Make dependency-check resilient to transient registry errors#8818
Merged
Conversation
The dependency availability check occasionally fails when the registry returns a sporadic transient error, which blocks otherwise-healthy runs. Retry failed requests with exponential backoff and jitter (all bounds configurable via env), and raise request concurrency.
zurfyx
requested review from
acywatson,
etrepum,
fantactuka,
ivailop7 and
potatowagon
as code owners
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
meta-cla
Bot
added
the
CLA Signed
etrepum
approved these changes
Jul 8, 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
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.
Motivation
The internal-registry dependency-availability check occasionally fails when the registry returns a sporadic transient error, which blocks otherwise-healthy CI runs and can gate merges. The check should ride out a momentary hiccup rather than failing the whole run on a single bad response.
Changes
Retry-Afterwhen present.CHECK_MAX_ATTEMPTS,CHECK_RETRY_BASE_MS,CHECK_RETRY_MAX_MS,CHECK_CONCURRENCY.Test plan