fix(release): close the 6.0.0 publication record - #92
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: 1fd71e46a5
ℹ️ 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".
| [[ "$(npm view "@godpowers/mcp@$version" version)" == "$version" ]] | ||
| verify_exact_version() { | ||
| package_spec="$1" | ||
| for attempt in {1..12}; do |
There was a problem hiding this comment.
When an npm version becomes visible between 110 and 120 seconds after publication, this loop still fails the workflow despite the newly documented 120-second retry allowance: the 12 checks occur initially and after only 11 ten-second sleeps, at approximately 0 through 110 seconds. Add a thirteenth check or otherwise use an elapsed-time deadline so propagation during the last advertised interval can be detected.
Useful? React with 👍 / 👎.
1 participant
Summary
Publication outcome
Both immutable 6.0.0 packages were published with npm provenance under release-6-0-0. Registry propagation delayed the first exact-version read, so the recovery path verified both versions and promoted MCP first and root second without republishing. Both latest tags now resolve to 6.0.0.
Validation