fix: resolve alembic migration chain conflict (sponsors 031 → 036) #356

Merged
forgejo_admin merged 1 commit from fix-sponsor-migration-chain into main 2026-04-06 16:15:29 +00:00
Contributor

Summary

Sponsor blast PR added migration 031 conflicting with contract_config 031. CrashLoopBackOff on deploy. Same root cause as #338.

Changes

  • Rename 031_add_sponsors_table.py036_add_sponsors_table.py
  • Chain: revision 036, down_revision 035

Test Plan

  • No duplicate 031 files
  • Pod starts without multiple heads error

Review Checklist

  • File rename + 4 line revision ID changes
## Summary Sponsor blast PR added migration 031 conflicting with contract_config 031. CrashLoopBackOff on deploy. Same root cause as #338. ## Changes - Rename `031_add_sponsors_table.py` → `036_add_sponsors_table.py` - Chain: revision 036, down_revision 035 ## Test Plan - [x] No duplicate 031 files - [ ] Pod starts without multiple heads error ## Review Checklist - [x] File rename + 4 line revision ID changes ## Related Notes - Fixes #344
fix: resolve alembic migration chain conflict (sponsors 031 → 036)
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
0db749b959
Sponsor blast PR added migration 031 which conflicts with contract_config 031.
Rename to 036, chain after 035 (player overrides).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
forgejo_admin deleted branch fix-sponsor-migration-chain 2026-04-06 16:15:29 +00:00
Sign in to join this conversation.
No description provided.