[25.1] Fix database migration error from 25.0 > 25.1#21737
Merged
mvdbeek merged 1 commit intogalaxyproject:release_25.1from Feb 4, 2026
Merged
[25.1] Fix database migration error from 25.0 > 25.1#21737mvdbeek merged 1 commit intogalaxyproject:release_25.1from
mvdbeek merged 1 commit intogalaxyproject:release_25.1from
Conversation
This is needed because the migration adding these fields was added to 25.1, fixing a bug in 24.2. So if a new galaxy db was created at or after 24.2, these fields were added from the model, so there was no path to migrate to 25.1, as the fields that were added in the migration would have already been added by galaxy on initial startup.
jdavcs
changed the title
nsoranzo
approved these changes
Feb 3, 2026
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.
Fix #21699.
This is needed because the migration adding these fields was added to 25.1, fixing a bug in 24.2. So if a new galaxy db was created under versions 24.2 or 25.0, these fields were added from the model during startup. Thus, in that case, there was no path to safely migrate to 25.1, as the fields that were being added in the migration were already in the database - hense, the migration error.
How to test the changes?
(Select all options that apply)
License