fix: resolve alembic migration chain conflict (sponsors 031 → 036) #356
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
ldraney/basketball-api!356
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-sponsor-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
Sponsor blast PR added migration 031 conflicting with contract_config 031. CrashLoopBackOff on deploy. Same root cause as #338.
Changes
031_add_sponsors_table.py→036_add_sponsors_table.pyTest Plan
Review Checklist
Related Notes