planify: Plugin aus der npm-Registry statt git+https - #115
Open
trick77 wants to merge 1 commit into
Open
Conversation
The plugin preset wrote a git spec into opencode.json. opencode resolves that with bun on its next start, which needs a git binary and git-over-HTTPS on the target machine. Where that is missing, nothing is installed and nobody says so: the fetch-based skill and rules land, plan_render never appears, and the skill has nothing to operate on. Seen on a fresh remote machine. opencode-planify-german 0.3.2 is on npm, so the preset pins the registry spec like plugin-dcg and plugin-litellm-pricing do, and pin-sources looks the version up there instead of in the repo's tags. The fetched skill and rules move to the 0.3.2 commit: both now say what to do when plan_render is missing, instead of leaving the agent without an output path.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
A fresh remote machine ran
npx opencode-presets install opencode-planify-german, saw no error, and ended up without theplan_rendertool — skill loaded, nothing to operate on.The two fetch-based parts always land: this CLI downloads them itself, sha256-verified. The plugin part is different — the installer only appends a spec string to
plugininopencode.json, and opencode resolves it with bun on its next start. With a git spec that means agitbinary and git-over-HTTPS to github.com on the target machine. Where that is missing, nothing is installed and nothing complains.opencode-planify-germanis now published on npm (0.3.2, OIDC + provenance), so the preset can pin a registry spec likeplugin-dcgandplugin-litellm-pricingalready do.What changed
presets/plugin-opencode-planify-german.conf: body["opencode-planify-german@0.3.2"],@pins0.3.2, description says npm and names the restart opencode needs.presets/skill-…andpresets/instructions-…:@fetchmoved to the 0.3.2 commit with fresh sha256, cache paths…-0.3.2…. Upstream both files now say what to do whenplan_renderis missing — name the install command, do not fall back to hand-written HTML.src/pin-sources.ts:opencode-planify-germanlooks up on npm instead of GitHub tags. The repo publishes GitHub releases now too, but npm is the source the preset installs from.README.md: the plugin row still claimedpins tag v0.2.1.Verified
npm test178/178.npm run check-pinsreportsopencode-planify-german 0.3.2 / 0.3.2 okvia the npm lookup. Real install against a throwaway config: all four fetches verify, and the result isNote for upgrading an existing install
removeAtPathmatchesappendentries deep-equal against the current preset body, soremoverun from this version will not find the old git spec or the…-0.3.1…cache paths. Remove with the previous version first, or drop those three entries fromopencode.jsonby hand.