Repository navigation
Publish: a version already in the MCP Registry is not a failure - #6
Merged
Merged
Conversation
Re-running Publish for a registered version (a release published after a manual run, as with v0.1.14) failed at the last step with 400 "cannot publish duplicate version", though nothing was wrong. That reply now passes with a notice; any other registry error still fails the run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013F6VMUcDtZmJX3ZibLuzXg
This was referenced Oct 11, 2026
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.
Summary
The "Publish to the MCP Registry" step in
publish.ymlfailed whenever the version was already registered. That happened with thev0.1.14release (run 38128314315): 0.1.14 had already been registered by a manual run, so the registry answered400 … "invalid version: cannot publish duplicate version"and the run went red, though nothing was wrong.Now that reply passes, with a
::notice::saying the version is already registered. Any othermcp-publishererror still fails the run, and its output is still printed.Related issue
None.
Type of change
Checklist
dotnet buildpasses (CI)dotnet testpasses (CI)Notes for reviewers
PR CI doesn't run
publish.yml, so I tested the step by hand. I took itsrun:block from the parsed YAML and ran it underbash -e, as Actions does, against a stand-inmcp-publisher:The real check comes with the next release, or with a manual Publish run for an existing version.
🤖 Generated with Claude Code
https://claude.ai/code/session_013F6VMUcDtZmJX3ZibLuzXg
Generated by Claude Code