Add VERSIONS-SKIP to handle projects stuck on bad latest versions #4355
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.
what
VERSIONS-SKIP
VERSIONS-SKIP
why
Some projects' latest versions are defective in some way. Usually, those projects release a later version that fixes the issue, and we can proceed normally, but occasionally the projects languish in this broken state. In that case, we try and fail to auto-update the project twice a day, leaving broken PRs open indefinitely.
With this new feature, we can mark those versions as bad and prevent auto-update from re-opening PRs for them.
references
These PRs have been open for over a year due to this issue: