chore(plugin): bump to 1.29.0 and require a version bump on every plugin change - #40
Merged
Merged
Conversation
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.
PR #39 loosened the Fable mention rule on 2026-09-10 but left the plugin version at 1.28.0. The installer copies a plugin into its cache only when the marketplace version is higher than the installed one. So
/pluginreported "already at the latest version" and every machine kept running the old hook. This PR ships the change and stops the same miss from happening again.CLAUDE.mdthat says every change underplugins/gborges-standard/bumps the version in both manifests, and why.plugins/gborges-standard/without raising the version, or leaves the two manifests unequal. Rehearsed locally againstorigin/main: base 1.28.0, PR 1.29.0, pass.