fix: resolve alembic migration chain conflict (031 → 031/032/033) #338
No reviewers
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/basketball-api!338
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-migration-chain"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
basketball-api pod is in CrashLoopBackOff. Three migrations independently created with revision
031causeMultiple head revisionserror on startup.Changes
031_add_contract_overrides_to_players.py→032_...withdown_revision = "031"031_add_contract_email_type_enum_values.py→033_...withdown_revision = "032"Test Plan
alembic upgrade headapplies all three migrations in orderReview Checklist
Related Notes