Defer major upgrades while the current version line is still maintained - #226
Open
LarsLaskowski wants to merge 1 commit into
Open
Defer major upgrades while the current version line is still maintained#226LarsLaskowski wants to merge 1 commit into
LarsLaskowski wants to merge 1 commit into
Conversation
The major upgrade policy read the start of the new major line from the candidate list, which is pre-filtered to tags published after the running tag, so a line that began long ago looked young enough to pass the waiting period. The first release is now taken as the lowest known version of that line, a line whose lowest known version is not its initial release counts as truncated, and the upgrade additionally waits until the current major line went dormant before that initial release. Missing publication timestamps no longer skip the age checks but defer the upgrade instead.
|
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.
Summary
The major upgrade policy read the start of the new major line from the
candidate list, which is pre-filtered to tags published after the running
tag, so a line that began long ago looked young enough to pass the waiting
period. The first release is now taken as the lowest known version of that
line, a line whose lowest known version is not its initial release counts as
truncated, and the upgrade additionally waits until the current major line
went dormant before that initial release. Missing publication timestamps no
longer skip the age checks but defer the upgrade instead.