Skip to content

chore(release): sync packaging version strings to 1.2.0 - #57

Merged
cuihtlauac merged 1 commit into
mainfrom
chore/sync-packaging-version-1.2.0
Oct 2, 2026
Merged

cuihtlauac merged 1 commit into
mainfrom
chore/sync-packaging-version-1.2.0

Conversation

@cuihtlauac

Copy link
Copy Markdown
Member

Follow-up to #55 + #53. #55 bumped Cargo.toml to 1.2.0 but was authored before the plugin/mcpb packaging (#53) introduced hardcoded version strings consumed by external tooling. This syncs them so the v1.2.0 tag is internally consistent (per the CLAUDE.md version-bump procedure):

  • server.json — version fields + the mcpb release-download identifier URL (…/v1.2.0/…-v1.2.0-…mcpb)
  • packaging/mcpb/manifest.json
  • .claude-plugin/plugin.json

No code change; JSON validated with jq. Should merge before tagging v1.2.0.

🤖 Generated with Claude Code

PR #55 bumped Cargo.toml to 1.2.0 but was authored before the plugin/mcpb
packaging landed (#53), which introduced version strings that are consumed
by external tooling before any binary runs. Sync them to match Cargo.toml
per the CLAUDE.md version-bump procedure, so the v1.2.0 tag is consistent:
- server.json (version fields + the mcpb release-download identifier URL)
- packaging/mcpb/manifest.json
- .claude-plugin/plugin.json

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@cuihtlauac
cuihtlauac merged commit 622dec5 into main Oct 2, 2026
16 checks passed
@cuihtlauac
cuihtlauac deleted the chore/sync-packaging-version-1.2.0 branch October 2, 2026 06:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant