release: CLI v0.6.1 + extension v0.1.6 + plugin manifest catch-up#151
Merged
Conversation
Launch-readiness release carrying the fixes from the core and extension launch-readiness PRs. Bumps, this time following scripts/release.sh conventions (the v0.6.0 release bypassed it, which is how plugin.json drifted): package.json 0.6.0 -> 0.6.1 extension/package.json 0.1.5 -> 0.1.6 .claude-plugin/plugin.json 0.5.0 -> 0.6.1 (catch-up: skipped in v0.6.0) templates/plugin-README.md badge 0.5.0 -> 0.6.1 Plus release-process guards so the June-3 incidents cannot recur silently: - release-binary.yml: fail before building when tag / package.json / plugin.json versions disagree. - publish-extension.yml: same for extension/package.json. - release.sh postflight: verify the anthropics/claude-plugins-community SHA pin matches the plugin repo HEAD, with exact bump-PR instructions when it doesn't (the pin had silently pointed at April's v0.2.9 through three releases). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
4 tasks
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.
Summary
Launch-readiness release. Merge order matters: #149 → #150 → this PR → push tags (the tag must land on a main that already contains the fixes — and the new CI guard in this PR will fail the release if versions drift again).
axme-code)v0.6.1extension-v0.1.6v0.6.1sync).claude-plugin/plugin.jsonis a catch-up: the v0.6.0 release was prepared manually, bypassingscripts/release.sh, so the plugin manifest and README badge stayed at 0.5.0. Claude Code keys plugin update detection on that version — without this bump, plugin users would never see an update even after the marketplace pin is fixed.What ships in v0.6.1 / extension-v0.1.6
Everything from #149 (core) and #150 (extension): plugin audit pipeline revival, auto-update un-bricking, setup flag validation, config refuse-don't-clobber, setup.lock recovery, decision-ID dedup, Windows hook dedupe, POSIX node preflight, unified not-initialized messaging, real serverInfo version. Full notes in the CHANGELOG entry in this diff.
New release-process guards (also in this PR)
release-binary.yml: fails before building whentag != package.json != .claude-plugin/plugin.json. Would have caught both June-3 incidents (tag pushed before release PR merged; plugin.json drift).publish-extension.yml: same check forextension/package.json(would have caught the 0.1.4-manifest .vsix rejected by Open VSX).scripts/release.shpostflight: verifies the anthropics/claude-plugins-community SHA pin matches the plugin repo HEAD and prints exact bump-PR instructions when it doesn't. That pin silently pointed at April's v0.2.9 through three releases — the missing last mile no automation owned.After merge (your part — tags fire the workflows)
git checkout main && git pull origin main git tag v0.6.1 git push origin v0.6.1 git tag extension-v0.1.6 git push origin extension-v0.1.6Then I'll watch both workflows, verify all channels (GitHub Release, npm, plugin-repo sync, Open VSX), and open the marketplace-pin bump PR to anthropics/claude-plugins-community with the fresh sync SHA — the final step that actually unblocks
claude plugin install axme-code@claude-community(currently serving v0.2.9 from April).Verification
bash -n release.shclean; both workflow YAMLs parse; all JSON manifests parse[0.6.1]section present (release.sh preflight requirement)🤖 Generated with Claude Code