ci: publish MCP registry metadata#627
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
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.
Summary
Publish MCP registry metadata from the repo instead of relying on manual local
mcp-publisherruns.Adds a release/manual-dispatch workflow that validates the release tag against
package.jsonandserver.json, checks MCP metadata sync, authenticates with GitHub OIDC, and publishesserver.jsonto the official MCP Registry.Also hooks the package
versionlifecycle sonpm version/pnpm versionsyncsserver.jsonand stages it into the version commit.Touched files: 2. Scope stayed within release automation and MCP metadata sync.
Validation
Verified
server.jsonmetadata sync withnode scripts/sync-mcp-metadata.mjs --checkand parsed the new workflow YAML successfully with Ruby.pnpm install --frozen-lockfilecompleted, butpnpm formatcould not run in this local checkout becauseoxfmt's native Darwin ARM64 binding fails to load with a macOS code-signature Team ID error. No docs or skills were updated because this is release automation only.