Repository navigation
fix: wait for the package registry to serve the release before publishing to the MCP Registry - #1976
Merged
Merged
Conversation
…hing to the MCP Registry
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
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.
Description
The MCP Registry checks every non-OCI package listed in
server.jsonagainst its package registry when a server version is published, and rejects the publish with400("version ... was not found (status: 404)") while that registry does not serve the version yet. Thepublish-mcp-registryjob runs right after the package is published, so a registry that is a few seconds slow to serve the new version fails the job and leaves the release half done until someone re-runs it.This repository has not failed this way yet, but the same race has failed MCP Registry publishes for servers released to npm, and PyPI can also take a moment to serve a new version. The step checks whichever registry
server.jsonlists, so it covers both.Changes
server.jsonit polls the URL the MCP Registry checks (pypi.org/pypi/<name>/<version>/json) every 15 seconds, up to 40 times (10 minutes), and continues as soon as it answers200.server.jsonlists a package type it cannot check, instead of letting the publish fail later with a less clear message.timeout-minutesfrom 10 to 20 so the wait fits inside it.Type of Change
Testing
Ran the step's script locally from this checkout, against this repository's
server.json:VERSIONset to the version currently published (n24q02m-wet), the URL answers200and the step exits 0;404and the step exits 1 with thestill answers 404error (loop shortened for the run).actionlintoncd.ymlreports the same findings before and after the change; none are in the new step. CI on this PR covers the rest.