Repository navigation
Conversation
Both workflows run on the same release event, so the registry job could validate server.json before PyPI served the new version and fail with a 404 (happened for v0.3.1 and v0.5.0). Poll PyPI for up to 10 minutes first.
This branch has not been 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.
The PyPI and MCP Registry workflows both start on the same
release: publishedevent. The registry checks that the PyPI version inserver.jsonexists, so it fails with a 404 whenever it runs before PyPI has finished publishing. This happened on v0.3.1 and v0.5.0, and both needed a manual re-run.This adds a step that polls
https://pypi.org/pypi/<pkg>/<version>/json(read fromserver.json) every 15s for up to 10 minutes before publishing.