Execute V15 User data migrations as pre-migrations #17140
Merged
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.
Prerequisites
Description
Similarly to #17130, we also need execute the V15 migrations affecting User data as pre-migrations.
As it happens, one of the V14 migrations (
MigrateTours
) must run before the V15 ones can run, so that one has been moved to pre-migrations as well. To achieve a smooth transition to V15 from both V14 and V13:MigrateTours
has been replaced with a no-op migration in the regular upgrade plan.MigrateTours
has slightly altered to exit fast, in case it has already run (which will be the case in a V14 to V15 upgrade).Testing this PR
Verify that both attended and unattended upgrades work from V14 to V15 and from V13 to V15.
Run these tests for both SQLite and SQL Server.