fix(audit-action): retry, chunk and bound npm advisory requests - #17
Merged
cherviakovtaskworld merged 1 commit intoSep 9, 2026
Merged
Conversation
The bulk advisory client made a single attempt with a 10s budget for the whole prod closure in one body, so a transient registry 503 or a slow upload on a loaded runner turned into a red CI check. Extract the transport into registryClient.ts: retry 429/5xx/timeouts up to 4 times with exponential backoff (honouring Retry-After), split the payload into chunks of 400 packages sent with a concurrency of 3, and bound the whole run by a shared 120s deadline so a degraded registry cannot stall the CI step. Registry unavailability now surfaces as RegistryUnavailableError and as a new registry-unavailable output, so an infrastructure failure is distinguishable from an audit failure. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
VulnerabilitiesVulnerabilities were found in audit-action.
|
This-is-a-Book
approved these changes
Sep 9, 2026
cherviakovtaskworld
deleted the
cherviakovtaskworld/audit-registry-retries
branch
September 9, 2026 04:24
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
2 participants
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 bulk advisory client made a single attempt with a 10s budget for the whole
prod closure in one body, so a transient registry 503 or a slow upload on a
loaded runner turned into a red CI check.
Extract the transport into registryClient.ts: retry 429/5xx/timeouts up to 4
times with exponential backoff (honouring Retry-After), split the payload into
chunks of 400 packages sent with a concurrency of 3, and bound the whole run by
a shared 120s deadline so a degraded registry cannot stall the CI step. Registry
unavailability now surfaces as RegistryUnavailableError and as a new
registry-unavailable output, so an infrastructure failure is distinguishable
from an audit failure.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com