[codex] Fix Flyway migration version conflict#268
Merged
Conversation
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
1 participant
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.
What changed
V9__change_field_social_login_token_longtext.sqltoV11__change_field_social_login_token_longtext.sql.Why
The deploy branch already contains
V9__create_account_deletion_feedback.sqlandV10__deduplicate_social_users_add_unique_constraint.sql. After PR #267 was merged, the application jar contained two Flyway migrations with version9, causing startup to fail with:Impact
Flyway can validate and run migrations again. The
social_login_tokencolumn widening still runs, now as version11, after the existing deploy migrations.Validation
./gradlew compileJavapasses.