Repository navigation
chore(mcp): align version fields with 0.3.1 - #101
Merged
Merged
Conversation
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.
What this changes
Aligns the MCP package's remaining version fields with
package.json(0.3.1) so the next manual publish reports the right version.Key files
packages/mcp/server.json— top-levelversionandpackages[0].version0.3.0 to 0.3.1packages/mcp/manifest.json—version0.3.0 to 0.3.1packages/mcp/src/index.ts—McpServer({ version })0.3.0 to 0.3.1Before / after
serverInfo.versionwas 0.3.0 in the shipped server; now 0.3.1.Verified with
pnpm --filter @mobile-reality/mdma-mcp build,test,smoke:pack, rootpnpm lintandpnpm typecheck, all green. Unreviewed fixes: none. No other stale version strings found.