Skip to content

fix(release): ride out transient npm registry failures - #125

Merged
GeekCmore merged 1 commit into
mainfrom
fix/npm-retry
Oct 22, 2026
Merged

GeekCmore merged 1 commit into
mainfrom
fix/npm-retry

Conversation

@GeekCmore

Copy link
Copy Markdown
Collaborator

The npm registry had a degraded publish/whoami window during the 0.1.4-rc.2 rerun: npm whoami returned E503 after seven minutes, and the failure-only npx npm@12 stage list then hung. This makes the release controller survive the short outages that were turning successful publishes into red runs.

  • Retry npm whoami up to 10 times with 30 s pauses.
  • Bound the staged-queue listing with timeout 180.
  • Retry npm view on E503, EAI_AGAIN, ETIMEDOUT, ECONNRESET, and 503 Service Unavailable.

node --test script/tests/*.test.mjs and YAML parsing pass.

The npm registry can answer 503 for several minutes during a release. Retry npm whoami for five minutes, bound the staged-queue npx call, and retry npm view on the retryable network/5xx errors so the release controller does not fail before it can read or verify an artifact.
@GeekCmore
GeekCmore merged commit e934637 into main Oct 22, 2026
6 of 7 checks passed
@GeekCmore
GeekCmore deleted the fix/npm-retry branch October 22, 2026 02:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants