Repository navigation
fix(ci): defer upgrades blocked by release age - #3379
Merged
Merged
Conversation
Keep the seven-day holdback when a required minimum version is too young to resolve. Confirm that the unrestricted dependency set resolves before deferring, so invalid requirements still fail the job.
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
1 participant
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 scheduled upgrade run failed because the release group requires
GitPython>=3.2, while the seven-day cutoff excludes its first available release.Keep the minimum version and age filter. If the filtered release dependencies cannot resolve, check the unrestricted set in runner temporary storage with source builds disabled. Defer the upgrade when that check succeeds; unresolvable requirements still fail the job.