Remove plugin version so updates are keyed on commits - #8
Merged
Conversation
A declared version makes `claude plugin update` compare version strings. The version has not moved since the plugin was created, so the updater reports the plugin is already current and skips real changes. Without the field it compares commits.
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.
claude plugin updatecompares the declared version string, so this plugin has been silently skipping updates. The version has read1.0.0since January while the repo moved on. On my machine right now the install sits at 3fb8382, two commits behind HEAD at 34d82a3, and one of those commits changedhooks/hooks.json. The nightly update printsalready at the latest version (1.0.0)and exits 0.Dropping the field makes the plugin commit-keyed, which is how every other plugin I install already works. The alternative is bumping the version on every change, a standing manual step that will be forgotten. Being two commits behind is what forgetting it looks like.
Nothing reads the manifest version. The
versioninpackage.jsonis separate and unaffected, and no workflow or doc references the manifest field. Tests pass locally.