CI: npm audit fails main when the npm registry is down #263

New issue

Closed

opened 2026-10-22 02:48:25 +00:00 by littlefox · 1 comment

littlefox commented

2026-10-22 02:48:25 +00:00

Owner

Main run #432 (the merge of #261) went red in the e2e job's npm audit --audit-level=high step: 503 Service Unavailable from registry.npmjs.org's advisory endpoint ("audit endpoint returned an error"). The code and the other jobs were fine.

Fix, as for cargo-deny's advisory fetch (#143): a script that retries when the endpoint errors, fails on vulnerabilities as now, and after a few failed tries of the endpoint itself warns and passes (the next run audits again).

Main run #432 (the merge of #261) went red in the e2e job's `npm audit --audit-level=high` step: `503 Service Unavailable` from registry.npmjs.org's advisory endpoint ("audit endpoint returned an error"). The code and the other jobs were fine. Fix, as for cargo-deny's advisory fetch (#143): a script that retries when the endpoint errors, fails on vulnerabilities as now, and after a few failed tries of the endpoint itself warns and passes (the next run audits again).

littlefox added this to the 0.6: Performance milestone

2026-10-22 02:48:25 +00:00

littlefox added the

area/ci

kind/bug

labels

2026-10-22 02:48:25 +00:00

littlefox referenced this issue from a pull request that will close it,

2026-10-22 02:59:15 +00:00

CI: retry npm audit when the registry is down, then warn #264

littlefox referenced this issue from a commit

2026-10-22 02:59:17 +00:00