fix(release): keep the .mcpb template's client pin in sync - #135
Open
dougborg wants to merge 1 commit into
Open
Conversation
The MCP release for mcp-v0.2.0 failed to build its bundle: RuntimeError: Bundle pyproject.template.toml is out of sync with the package's. release-pr-prepare.yml bumps the client floor in statuspro_mcp_server/pyproject.toml, but the .mcpb bundle carries its own copy of the dependency list in mcpb/pyproject.template.toml, and scripts/build_mcpb.py hard-fails when the two disagree. The release PR moved one and not the other. Update both in the same step, and stage both in the commit. Also corrects the drift already on main (template still said >=0.1.0 while the package says >=0.3.0) so mcp-v0.2.0 can be published. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QRhJ5dF3N3z7X63aRaDBcQ
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.
Problem
Publishing
mcp-v0.2.0failed in run 30273452529:release-pr-prepare.ymlkeepsstatuspro_mcp_server/pyproject.toml's client floor truthful — it correctly bumped it to>=0.3.0on the release PR. But the.mcpbbundle carries a second copy of the dependency list instatuspro_mcp_server/mcpb/pyproject.template.toml, andscripts/build_mcpb.pyhard-fails when the two disagree. Only one of the two moved.The drift guard did its job — this is a gap in the release glue, not a bad check.
Fix
main(template>=0.1.0vs package>=0.3.0), which is what currently blocksmcp-v0.2.0from publishing.Sibling repos
stocktrim-openapi-clienthas the samemcpb/pyproject.template.tomllayout and will hit this identically once its release PR runs.frontappandkatanahave no bundle template and are unaffected.Context
Found while recovering the stuck draft releases from #134.
client-v0.3.0published successfully (PyPI 0.3.0, release un-drafted with wheel, sdist and both attestations attached);mcp-v0.2.0is the remaining one.🤖 Generated with Claude Code
https://claude.ai/code/session_01QRhJ5dF3N3z7X63aRaDBcQ