Repository navigation
Fix/mcp registry publish npm propagation - #487
Merged
gaurav-singh-9227 merged 3 commits intoOct 16, 2026
Merged
gaurav-singh-9227 merged 3 commits into
gaurav-singh-9227 merged 3 commits into
Conversation
The MCP Registry validates that the npm version already exists before it accepts the server entry. The release workflow dispatches this one right after `npm publish`, but npm's read API lags publish by up to a minute, so the registry check raced it and 404'd. That race failed the last three tag-triggered releases: v2.2.0 registry 404 at 15:21:34, npm served it at 15:21:57 (23s early) v2.2.1 registry 404 at 14:29:12, npm served it at 14:29:30 (18s early) v2.2.2 registry 404 at 14:23:26, npm served it at 14:24:04 (38s early) In every case the npm publish itself succeeded; only the registry step failed, which is why manually re-running it later always went green. Poll registry.npmjs.org for the exact version (up to 5 minutes) before logging in, and retry the publish up to 3 times so a brief blip does not cost a whole release cycle. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
Give both retry loops more room so a slow npm propagation or a longer registry blip does not cost a whole release cycle: - npm propagation wait: 5 -> 15 minutes - publish retry backoff: 30s -> 5 minutes between attempts Both loops exit as soon as they succeed, so the normal path is unchanged (runs still finish in ~90s); the wider caps only apply when something is actually slow, and an exhausted loop still fails the job rather than publishing a version npm is not serving. Add timeout-minutes: 45 so the job is explicitly bounded instead of inheriting GitHub's 6-hour default. Worst case is ~31 min. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
gaurav-singh-9227
approved these changes
Oct 16, 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.
No description provided.