chore(release): tolerate npm replica lag — poll ~6 min, warn (not fail) on timeout so the GitHub release still lands - #635
Merged
Conversation
…l) on timeout so the GitHub release still lands v0.30.6: npm publish succeeded but the registry took ~5 minutes to serve the version; the 30s verify step aborted the job and the GitHub-release step never ran. Now: registry document polled directly (bypasses client cache) for up to 24×15s, continue-on-error so the idempotent release step always runs, and the step summary flags an unconfirmed propagation. AGENTS.md step 8 updated (do not re-run / do not publish locally on lag).
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.
v0.30.6: npm publish succeeded but the registry took ~5 minutes to serve
the version; the 30s verify step aborted the job and the GitHub-release step
never ran. Now: registry document polled directly (bypasses client cache)
for up to 24×15s, continue-on-error so the idempotent release step always
runs, and the step summary flags an unconfirmed propagation. AGENTS.md step 8
updated (do not re-run / do not publish locally on lag).