Repository navigation
Bump version to 0.1.1 to propagate mcpName to the npm registry - #13
Merged
Merged
Conversation
- The MCP Registry verifies ownership by reading mcpName from the npm-published package.json at the version recorded in server.json. mcpName was added in PR #12 but npm @dominion525/familiar-mcp@0.1.0 was published before that PR, so the field is not visible on the registry and mcp-publisher publish fails with 400. - Bump mcp/package.json and mcp/package-lock.json via npm version --no-git-tag-version - Bump mcp/manifest.json and mcp/server.json (top-level and packages[0].version) in sync - No code changes; first end-to-end run of .github/workflows/release.yml will follow when the v0.1.1 tag is pushed Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.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
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.
Summary
Bump
@dominion525/familiar-mcpto0.1.1so that re-publishing surfaces themcpNamefield (added in #12) on the npm registry. The MCP Registry verifies ownership by readingmcpNamefrom the npm-publishedpackage.jsonat the version recorded inserver.json; npm0.1.0predates #12 and therefore lacks the field, causingmcp-publisher publishto 400.Changes
mcp/package.jsonandmcp/package-lock.jsonbumped to0.1.1vianpm version --no-git-tag-versionmcp/manifest.jsonandmcp/server.json(top-level +packages[0].version) bumped in syncRelease flow once merged
v0.1.1tag →.github/workflows/release.ymlruns for the first time end-to-end (npm publish via OIDC + GitHub Release +.mcpbasset upload)cd mcp && mcp-publisher publishthen succeeds