Repository navigation
fix: make npm publish gate survive registry CDN lag - #13
Merged
Merged
Conversation
v0.0.19's npm publish succeeded, but verifyRegistry required dist-tags.latest within 120s via npm view and failed while the CDN still served 0.0.18 — the same pattern as v0.0.17. - Treat exact version packument visibility as ready (latest may lag) - Poll cache-busted registry JSON for up to 10 minutes with backoff - Skip republish when the version is already on npm (idempotent re-run)
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.
Problem
publish npm for v0.0.19 failed even though
npm publishsucceeded (+ [email protected]). Post-publishverifyRegistrypollednpm viewfor 120s requiringdist-tags.latest === version, while the CDN kept servinglatest=0.0.18/ version details missing. Same pattern as v0.0.17. The package did land on npm ~2 minutes later.Fix
dist-tags.latest; smoke already pins@version)Note
A follow-up workflow change (
workflow_dispatch+ overlay gate scripts from default branch + 45m job timeout) could not be pushed with the current OAuth token (missingworkflowscope). Scripts-only fix is enough for future tags that include this commit.Test
npm run test:scripts -- scripts/release-npm-lib.test.mjs— 9 passed.