chore: bump server.json to 1.0.1 (mcpb package scaffold)#125
Merged
Conversation
Align the committed MCP Registry manifest with the 1.0.1 release. Adds a packages[] mcpb entry pinned to the mcpb-v1.0.1 release asset, with a placeholder file_sha256 filled once the bundle is built at tag time. CI (build-mcpb.yml) still overwrites file_sha256 with the real hash on the mcpb-v1.0.1 tag; this commit makes the manual mcp-publisher publish fallback target 1.0.1 instead of the immutable, already-live 1.0.0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Jim Vinson <jim@vinson.org>
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.
What
Bumps the committed
server.jsonMCP Registry manifest from1.0.0to1.0.1and adds apackages[]mcpbentry pinned to themcpb-v1.0.1release asset. Thefile_sha256is aPLACEHOLDER_FILL_TUESDAYuntil the bundle is built at tag time.Why
The 1.0.1 repo prep (PR #124) left the committed
server.jsonat1.0.0with nopackagesarray. CI (build-mcpb.yml) overwrites it dynamically on themcpb-v1.0.1tag, but the manualmcp-publisher publishfallback would target the immutable, already-live1.0.0and fail. This makes the committed manifest match the release and gives the fallback a correct target.Compatibility
CI's pin step does a jq right-hand-wins merge onto
packages[0], so it silently replaces the placeholder hash with the realshasum -a 256at tag time. No conflict with the CI path.Follow-up (Tuesday 2026-07-07)
Replace
PLACEHOLDER_FILL_TUESDAYwith the real hash of the publishedmcpb-v1.0.1asset in a small commit after the bundle builds.Health
pnpm install --frozen-lockfileclean,pnpm -r buildgreen,pnpm -r test700 passed (baseline),mcpb validategreen.🤖 Generated with Claude Code