Repository navigation
chore: release 0.5.1 - #4
Merged
Merged
Conversation
The manifests have claimed 0.5.0 since the v0.5.0 feature commit, but that version was never tagged and never released — the newest release is still v0.4.0, from August. Meanwhile `/plugin marketplace add` clones the default branch, so every install during that window already reports 0.5.0, some of them carrying the pre-fix secret scanner. Release the fixed tree as 0.5.1 rather than 0.5.0 for exactly that reason: a number main has already served cannot distinguish the old copy from the new one, and `claude plugin update` would see no change to act on. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
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.
Version bump only —
0.5.0→0.5.1in the two manifests.Why 0.5.1 and not 0.5.0
The manifests have claimed
0.5.0since the v0.5.0 feature commit, but thatversion was never tagged and never released. The newest release is still
v0.4.0, from August.
/plugin marketplace addclones the default branch, not a tag, so every installduring that window already reports
0.5.0— some of them carrying the pre-fixsecret scanner. Reusing the number would mean the version string cannot
distinguish the old copy from the new one, and
claude plugin updatewould seeno change to act on: the fixes would silently fail to reach anyone who already
installed.
What ships
Everything since v0.4.0 — the whole v0.5.0 feature set plus today's four fixes:
feat: v0.5.0— history mining, CI guard, personal store, read telemetryfix: add required owner to marketplace.json(fix: add requiredownerto marketplace.json so the plugin installs #1) — v0.4.0 was neverinstallable from the marketplace
fix: secret scan missed every prefixed secret name(fix: secret scan missed every prefixed secret name (db_password, STRIPE_SECRET) #2)fix: linter was dead in a personal-store-only project(fix: linter was dead in a personal-store-only project #3)Checks
claude plugin validate .and./plugin— both pass, no warningsclaude plugin tag --dry-run— manifests agree on 0.5.1tests/test_manifests.pyenforces that the threedeclared versions match)
Tag will follow the repo's existing
v0.5.1convention, not thelore--v0.5.1schemeclaude plugin tagwould create.