Publish to the registry only on a 404, not on any non-200 - #80
Merged
Merged
Conversation
The publish job checks whether server.json's version is already on the official MCP registry. The registry answered that check with a transient 500, the job read anything but 200 as "not published", and it tried to publish 1.0.1 again -- failing the run with "duplicate version" though the listing was fine. - 404 means publish; 200 means skip - A 5xx is retried four times with backoff - If it persists, the run skips publishing with a warning rather than failing; the next deploy checks again Closes #79 --- Pages affected: - [MCP Harbor](https://ai.mcpharbor.dev/) -- the registry this job lists on the official MCP registry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Closes #79.
The deploy for #78 went red on
publish-mcp-registrywithinvalid version: cannot publish duplicate version. The listing was fine.The plan step asks the official registry whether
server.json's version already exists. That request got a transient HTTP 500 — it answers 200 now, three times running — and the step treated any non-200 as "not published yet", so the job tried to publish 1.0.1 a second time.Skipping is safe: nothing about the listing changes, and the next deploy checks again. A deploy should never go red because a third party had a bad few seconds.
Pages affected:
🤖 Generated with Claude Code