Opened 10 months ago
Last modified 12 days ago
#36141 closed Bug
After double squashing migrate command fails with InconsistentMigrationHistory — at Initial Version
| Reported by: | Jacob Walls | Owned by: | |
|---|---|---|---|
| Component: | Migrations | Version: | 6.0 |
| Severity: | Release blocker | Keywords: | |
| Cc: | Georgi Yanchev | Triage Stage: | Ready for checkin |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
[main/6.0]
Make four migrations, migrate, squash the first two, then squash the first three: then migrate (or makemigrations --check) fails.
manage.py makemigrations myapp --empty manage.py makemigrations myapp --empty manage.py makemigrations myapp --empty manage.py makemigrations myapp --empty manage.py migrate manage.py squashmigrations myapp 0001 0002 manage.py squashmigrations myapp 0001_initial_squashed 0003 manage.py migrate
django.db.migrations.exceptions.InconsistentMigrationHistory: Migration myapp.0004_auto_20250126_1339 is applied before its dependency new.0001_initial_squashed_0002_auto_20250126_1339_squashed_0003_auto_20250126_1339 on database 'default'.
Other migration commands can be subbed for that last call and still produce the same error, e.g. makemigrations --check, which is likely in a CI setting.
Note:
See TracTickets
for help on using tickets.