fix(toolset): scaffold the view bridge at this runtime's own version - #154
Merged
Merged
Conversation
The scaffold wrote "@developmentseed/mcp-view": "^0.1.0" into every new UI, and had done since 0.1.x — eight minor releases ago. The npm bridge is released from this repo in step with the wheel, so the installed version names the bridge to scaffold against, and the literal that went stale is gone. Only the release triple is used, so a local build whose version carries a suffix still names a published range. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ciaransweet
pushed a commit
that referenced
this pull request
Sep 21, 2026
🤖 I have created a release *beep* *boop* --- ## [0.10.2](mcp-toolsets-runtime-v0.10.1...mcp-toolsets-runtime-v0.10.2) (2026-09-21) ### Bug Fixes * **toolset:** scaffold the view bridge at this runtime's own version ([#154](#154)) ([d42171b](d42171b)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: ds-release-bot[bot] <116609932+ds-release-bot[bot]@users.noreply.github.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
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.
mcp-toolset new --with-uiwrote"@developmentseed/mcp-view": "^0.1.0"into every scaffolded UI, and had done since 0.1.x. A caret range on0.1.0resolves within0.1.x, so a toolset scaffolded today started eight minor releases behind the runtime that serves it — without the content sizing from #149, and on the pre-2.0ext-apps.Change
The bridge is published from this repo in the same version as the wheel, so the scaffold reads its own installed version rather than carrying a literal:
Only the release triple is used, so a local build whose version carries a
.devNor+localsuffix still names a range npm has published.Why not release-please
The other three version-carrying files are rewritten by release-please, but its generic updater needs an
x-release-please-versioncomment on the line, and this line lives inside a JSON template — the comment would land in every scaffoldedpackage.json. Reading the installed version needs no release wiring and cannot drift.Tests
mcp_view_rangereturns^0.10.1for0.10.1and^0.11.0for0.11.0.dev3+g1a2b3c.package.jsoncarries that range, so a literal cannot come back.Found while bumping mcp-toolsets#44, whose own view was still on
^0.2.0.🤖 Generated with Claude Code