Repository navigation
ci: wait for the npm version before publishing to the MCP registry - #7
Merged
Merged
Conversation
The 0.1.1 registry publish failed with 400 "version '0.1.1' was not found" because it ran seconds after semantic-release published, while npm still answered 404 (npm timestamped 0.1.1 ~75s after semantic-release reported it published). Poll npm for up to 10 minutes first. Co-Authored-By: Claude Opus 5.5 <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.
Problem
The first automated registry publish (run 44277350182) failed:
The
mcp-registryjob runs right after semantic-release, but npm made 0.1.1 visible only ~75s after semantic-release reported it published. Re-running the job a minute later succeeded, so this race would hit every release.Change
publish-mcp-registry.ymlpollsnpm view <pkg>@<version>every 15s (up to 10 min) beforemcp-publisher publish. The package name comes fromserver.json.Verification
YAML parses; the check returns immediately for a published version (
0.1.1) and keeps waiting for a missing one.ci:only, so merging doesn't cut a release.🤖 Generated with Claude Code