[migrations] Merge dual alembic heads to a single head#5
Merged
Conversation
zou upgrade-db runs `alembic upgrade head`, which aborts when the migration tree has multiple heads. The fork carried two parallel heads (2b8f88aa610f reconcile-squash and d1e2f3a4b5c6 salary-scale-cascade), so every deploy-time upgrade-db was a silent no-op and schema changes (incl. the salary scale ON DELETE CASCADE) never applied. Adds an empty merge revision uniting both heads so upgrades resolve to a single target again. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
zou upgrade-db runs
alembic upgrade head, which aborts when the migration tree has multiple heads. The fork carried two parallel heads (2b8f88aa610f reconcile-squash and d1e2f3a4b5c6 salary-scale-cascade), so every deploy-time upgrade-db was a silent no-op and schema changes (incl. the salary scale ON DELETE CASCADE) never applied. Adds an empty merge revision uniting both heads so upgrades resolve to a single target again.Problem
Solution