Uh oh!
There was an error while loading. Please reload this page.
[stable27] allow to upgrade from 26.0.x to 27.1.x directly - #39952
Merged
Conversation
Signed-off-by: Simon L <szaimen@e.mail.de> Signed-off-by: Simon L. <szaimen@e.mail.de>
AndyScherzinger
approved these changes
Aug 18, 2023
AndyScherzinger
left a comment
Member
There was a problem hiding this comment.
Not an expert, so +1 for the threshold-only
skjnldsv
previously requested changes
Aug 18, 2023
nickvergessen
approved these changes
Aug 24, 2023
nickvergessen
left a comment
Member
There was a problem hiding this comment.
This should definitely be in.
The updater will always return the latest 27.* to the newest 26
We don't want to make another loop, that is one of the reasons we did a minor.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Do this to prevent upgrade issues if custom update solutions are in place that are not written to handle the case needing to upgrade from 26.0.x to 27.0.x and then to 27.1.x
As discussed with @skjnldsv and @AndyScherzinger