Skip to content

fix: wait for the package registry to serve the release before publishing to the MCP Registry - #1976

Merged
n24q02m merged 1 commit into
mainfrom
fix/wait-for-package-registry
Nov 17, 2026
Merged

n24q02m merged 1 commit into
mainfrom
fix/wait-for-package-registry

Conversation

@n24q02m

@n24q02m n24q02m commented Nov 17, 2026

Copy link
Copy Markdown
Owner

Description

The MCP Registry checks every non-OCI package listed in server.json against its package registry when a server version is published, and rejects the publish with 400 ("version ... was not found (status: 404)") while that registry does not serve the version yet. The publish-mcp-registry job 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.json lists, so it covers both.

Changes

  • Add a "Wait for the package registry to serve the release" step before "Install MCP Publisher". For each non-OCI package in server.json it 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 answers 200.
  • The step fails with an explicit error if the version never appears, or if server.json lists a package type it cannot check, instead of letting the publish fail later with a less clear message.
  • Raise the job's timeout-minutes from 10 to 20 so the wait fits inside it.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Testing

  • Existing tests pass
  • Added new tests for the changes
  • Tested manually

Ran the step's script locally from this checkout, against this repository's server.json:

  • with VERSION set to the version currently published (n24q02m-wet), the URL answers 200 and the step exits 0;
  • with a version that does not exist, the URL keeps answering 404 and the step exits 1 with the still answers 404 error (loop shortened for the run).

actionlint on cd.yml reports the same findings before and after the change; none are in the new step. CI on this PR covers the rest.

@github-actions

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@n24q02m
n24q02m merged commit ed83d73 into main Nov 17, 2026
14 checks passed
@n24q02m
n24q02m deleted the fix/wait-for-package-registry branch November 17, 2026 05:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant