ci: increase wait-for-npm-ready timeout for publish scan delay - #5286
Merged
Conversation
npm now scans published packages before they go live, adding a delay of up to 15+ minutes between publish and availability. Raise the retry interval to 120s and cap at 12 attempts (~22 min). Closes #5266
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
WilcoFiers
approved these changes
Aug 5, 2026
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.
Summary
npm now scans published packages before they go live, adding a delay of up to 15+ minutes between calling
publishand the package becoming available. Ourwait-for-npm-ready.shretry loop was tuned for near-instant availability (10s × 30 = ~5 min), so it can now time out before the package appears.This raises the retry interval to 120s and caps attempts at 12 (~22 min worst case).
Notes
deploy.yml(validate-next-deploy,validate-deploy) rely on the 360-min default job timeout, so notimeout-minuteschanges were needed.Closes #5266