upgrade: fix downgrading to 2.11.5 schema version#11951
Merged
sergepetrenko merged 2 commits intotarantool:masterfrom Oct 23, 2025
Merged
upgrade: fix downgrading to 2.11.5 schema version#11951sergepetrenko merged 2 commits intotarantool:masterfrom
sergepetrenko merged 2 commits intotarantool:masterfrom
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 tarantool#11204 NO_DOC=bugfix
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
Serpentian
approved these changes
Oct 21, 2025
Contributor
Serpentian
left a comment
There was a problem hiding this comment.
Thank you for forward-porting the commit)
lenkis
approved these changes
Oct 22, 2025
Collaborator
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin release/3.2
git worktree add -d .worktree/backport/release/3.2/11951 origin/release/3.2
cd .worktree/backport/release/3.2/11951
git switch --create backport/release/3.2/11951
git cherry-pick -x e3c2882972d43718d2b22cf962efb92639b5465c 0628d91cd76be45cfe0623d955237ca4c7125e0c |
Collaborator
|
Successfully created backport PR for |
Collaborator
|
Successfully created backport PR for |
Collaborator
|
Successfully created backport PR for |
Collaborator
Backport summary
|
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
5 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.
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