Skip to content

fix(api): renumber the summary migrations after 0051_seed_resource_types - #230

Merged
anantjain341 merged 1 commit into
CivicDataLab:devfrom
anantjain341:fix/merge-migrations
Oct 6, 2026
Merged

anantjain341 merged 1 commit into
CivicDataLab:devfrom
anantjain341:fix/merge-migrations

Conversation

@anantjain341

Copy link
Copy Markdown

Dev deploys fail since #227: both #223 and #227 added a migration 0051 after 0050, so the container stops at start-up with "Conflicting migrations detected".

#227's migrations never ran on dev or prod, so this renumbers them to follow 0051_seed_resource_types:

  • 0051_alter_usecase_summary → 0052_alter_usecase_summary
  • 0052_alter_collaborative_summary → 0053_alter_collaborative_summary

No other changes. Checked locally from dev's state: migrations apply cleanly.

CivicDataLab#223 and CivicDataLab#227 both added a migration 0051 after 0050, so the container stops
at start-up with "Conflicting migrations detected" and dev deploys fail.
CivicDataLab#227's migrations never ran on dev or prod, so they move after
0051_seed_resource_types:

- 0051_alter_usecase_summary -> 0052_alter_usecase_summary
- 0052_alter_collaborative_summary -> 0053_alter_collaborative_summary

Same operations, new numbers only.
@anantjain341
anantjain341 merged commit f77545e into CivicDataLab:dev Oct 6, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant