fix(mcp): tighten A2A and release verification - #145
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9f53fdda87
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if (process.argv.includes("--check")) { | ||
| const data = await checkMcpRegistryVersion({ name, version }); | ||
| process.stdout.write(`${data ? "true" : "false"}\n`); |
There was a problem hiding this comment.
When either MCP release workflow runs --check during a transient Registry 429 or 5xx response, this direct call throws immediately even though checkMcpRegistryVersion explicitly marks that error as retryable. Both the recovery and normal publish workflows therefore abort before authentication or publication on the first transient response; route check mode through retry logic before deciding whether the version is already published.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in 7e14f36. The preflight now reuses the existing retry loop for transient 429/5xx responses while returning unpublished immediately for an exact 404. Added a red/green regression covering 503 then 404; all three Registry helper tests pass.
1 participant
No description provided.