feat: enable upgrading release from 4.4.X to 4.5.Y #8696
Merged
Conversation
This file contains 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
thalesmg
force-pushed
the
relup-upgrade-44-to-45
branch
3 times, most recently
from
1d2d365
to
3bcf972
Compare
When upgrading from 4.4.X, the `install_upgrade` script from 4.4.X is used, which forbids such transition.
thalesmg
force-pushed
the
relup-upgrade-44-to-45
branch
2 times, most recently
from
2e00079
to
403e787
Compare
thalesmg
force-pushed
the
relup-upgrade-44-to-45
branch
from
403e787
to
fc9e802
Compare
ieQu1
approved these changes
Aug 15, 2022
qzhuyan
approved these changes
Aug 15, 2022
zmstone
approved these changes
Aug 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When upgrading from 4.4.X, the
install_upgradescript from 4.4.Xis used, which forbids such transition.
The problem is that the
install_upgrade.escriptfor the older versions are already released. So, a new 4.4.FIX release containing this fix would need to be cut to allow upgrading 4.4.X -> 4.4.FIX -> 4.5.0.