fix(053): remove duplicate MCP registry publish workflow#518
Merged
Conversation
…g release.yml job release.yml already has an 'mcp-registry' job that publishes server.json on every tag via keyless GitHub OIDC (continue-on-error) — it has shipped 44 versions to registry.modelcontextprotocol.io. The publish-mcp-registry.yml added in #517 was a redundant duplicate that would have thrown 'cannot publish duplicate version' on every release. Removes it and corrects docs/mcp-registry-publishing.md to reference the existing automation instead of claiming publishing was manual.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
2 participants
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.
Reverts the redundant workflow added in #517.
Root cause:
release.ymlalready has anmcp-registryjob that publishesserver.jsonon every tag via keyless GitHub OIDC (continue-on-error: true). It has published 44 versions to registry.modelcontextprotocol.io (0.21.2 → 0.33.1). The earlier assumption that publishing was a blocked manual step was wrong.What this PR does:
.github/workflows/publish-mcp-registry.yml(ci(053): auto-publish server.json to MCP Registry on release (OIDC) #517) — a near-exact duplicate that would fail withcannot publish duplicate versionon every release.docs/mcp-registry-publishing.mdto document the existingrelease.ymlautomation rather than a new workflow, and clarifies that manual login is only for deprecate/validate/one-off actions.Net effect of this whole thread: the only durable change is #516's
server.jsondescription refresh (local-first + security scanning), which will go live automatically on the next release whenrelease.ymlpublishes the new version. No duplicate workflow remains.