Repository navigation
ci(cli): wait up to five minutes for npm before publishing to the MCP Registry - #290
Merged
Merged
Conversation
… Registry The registry reads the npm package of cli/server.json to check its mcpName, so it rejects the server until npm lists the new version. With 1.1.0 that took about two and a half minutes: the step got in on the fifth of six attempts. Ten attempts, 30 seconds apart, leave room for a slower npm. RELEASING.md also says that the trusted publisher has to allow npm publish, since one that only allows npm stage publish answers the workflow with a 403.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Merged
3 of 4 tasks
This branch was successfully deployed
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.
Summary
The release of 1.1.0 published to the MCP Registry on the fifth of six attempts, about two and a half minutes after npm: the registry rejects the server until npm lists the version (404). The step now tries ten times, 30 seconds apart, about five minutes.
docs/RELEASING.mdsays five minutes, and adds to the failure modes that the trusted publisher has to allownpm publish; one that only allowsnpm stage publishrejects the workflow with a 403.Test plan
cli-v*tag