Wait for npm to serve a release before registering it - #8
Merged
Merged
Conversation
The v0.2.1 registry job started 8s after npm publish and failed with "version '0.2.1' was not found (status: 404)". Poll npm for up to five minutes before publishing to the MCP Registry. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
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
1 participant
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
publish-registryjob that pollsnpm view @markmnl/fmsg-mcp@<version>every 10s, for up to 5 minutes, before authenticating and publishing to the MCP Registry.The v0.2.1 release (run 35694748594) failed because the registry job started 8s after
npm publishand gotversion '0.2.1' was not found (status: 404). Re-running the failed job succeeded.Testing
@markmnl/[email protected]and fails for a version that doesn't exist.🤖 Generated with Claude Code