[backport 3.3] upgrade: fix downgrading to 2.11.5 schema version#11975
Merged
sergepetrenko merged 2 commits intorelease/3.3from Oct 24, 2025
Merged
[backport 3.3] upgrade: fix downgrading to 2.11.5 schema version#11975sergepetrenko merged 2 commits intorelease/3.3from
sergepetrenko merged 2 commits intorelease/3.3from
Conversation
Some time ago we decided to introduce a new schema version to the 2.11 release series, 2.11.5. It doesn't carry any changes compared to the previous version, 2.11.1, and exists solely to mark the corresponding Tarantool version as supporting persistent names. This happened in commit 46cac24 ("upgrade: introduce 2.11.5 schema version"), however that commit was only pushed to the 2.11 branch, so the 3.x series still don't know anything about the 2.11.5 schema version and fail to downgrade to it. Let's fix this. Closes #11204 NO_DOC=bugfix (cherry picked from commit e3c2882)
Add the freshly released 2.11.8 version to the downgrade versions list. NO_CHANGELOG=post-release action NO_TEST=post-release action NO_DOC=post-release action (cherry picked from commit 0628d91)
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
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.
(This PR is a backport of #11951 to
release/3.3to a future3.3.4release.)Some time ago we decided to introduce a new schema version to the 2.11 release series, 2.11.5. It doesn't carry any changes compared to the previous version, 2.11.1, and exists solely to mark the corresponding Tarantool version as supporting persistent names.
This happened in commit 46cac24 ("upgrade: introduce 2.11.5 schema version"), however that commit was only pushed to the 2.11 branch, so the 3.x series still don't know anything about the 2.11.5 schema version and fail to downgrade to it. Let's fix this.
Closes #11204
NO_DOC=bugfix