Repository navigation
fix(release): bound each npm attempt during a registry outage - #126
Merged
Merged
Conversation
A degraded registry can hold whoami or view open for minutes, so the retry loops multiplied the wait instead of riding out a short outage. Bound each whoami to 30 seconds and each view to 30 seconds before retrying.
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.
The retry loop added for npm 503s assumed each
npm whoamiwould fail fast. During the 2026-10-22 degraded-publish window each call hung for about seven minutes, so ten retries could outlast the job. Bound eachwhoamiandnpm viewattempt to 30 seconds before retrying; a timeout is now treated as retryable.