Repository navigation
fix(migrations): resolve welcome recovery version collision - #50
Merged
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
2 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.
Problem
Production migration deployment stopped because two migration files shared version
20260726140000. Supabase had already recorded the two-person matching migration at that version, so the welcome claim recovery migration could not be added to migration history.Fix
Rename the welcome claim recovery migration to the unique, ordered version
20260726145000. SQL content is unchanged.Verification
pnpm agent:migrations:check -- --allpnpm --filter @tomeet/data test— 42 tests passed20260726145000and20260726150000pending