Repository navigation
chore(release): 0.13.2 - #231
Merged
Merged
Conversation
Pins the MCP registry listing to the version the tag will publish. The registry has no workspace stamping, so this is the one manifest that carries a real number (INV-9). 0.13.2 exists only because 0.13.1 published partially: core, elements, react, vue and svelte reached npm, then @aspicio/mcp was rejected for a missing repository field (#230). npm never accepts a version twice, so the runbook's answer is the next patch for all six, keeping them on one number. Its contents are 0.13.1's plus that fix. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
🚀 Preview deployed for |
|
🛠️ API preview deployed for |
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
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
The MCP registry listing advertises 0.13.1, a version
@aspicio/mcpwill never have, and the tag that publishes 0.13.2 cannot be cut until the listing agrees.server.jsonis the one manifest carrying a real version number — the registry has no workspace stamping, so the publish workflow cannot fill it in the way it does for the npm packages (INV-9).Solution
Bump both
versionfields to 0.13.2, ahead of the tag. Merge after #230.Why 0.13.2 exists. The v0.13.1 run (39879582677) published
core,elements,react,vue, andsvelte, then npm rejectedmcpfor a missingrepositoryfield (fixed in #230). npm never accepts a version twice, so the runbook's partial-publish answer applies: the next patch, for all six, so they stay on one number.A patch, not a minor: its content is 0.13.1's (dependency and toolchain movement, no API change — see #228) plus a manifest fix.
Other Changes
None — this PR is the version bump alone.
Related:
🤖 Generated with Claude Code