id summary reporter owner description type status component version severity resolution keywords cc stage has_patch needs_docs needs_tests needs_better_patch easy ui_ux 33734 InconsistentMigrationHistory triggers on squashed migrations when not all replaced migrations are applied GwynBleidD nobody "#27004 fixed a bug with triggering `InconsistentMigrationHistory` in some cases but not all of them. For example in migration tree: {{{ 0001_sq_0002 / \ App A: 0001 ---> 0002 | App B: 0001 }}} When only A.0001 and B.0002 are applied I think [https://github.com/django/django/blob/main/django/db/migrations/loader.py#L320-L326 fix] applied in #27004 should check if any of migrations replaced are already applied, not if all of them. When any of them is applied, we are already on a separate path of applying migration and squash migration will only be marked as applied, so it should be fine to change it from all to any." Bug closed Migrations 3.2 Normal needsinfo migrations squash inconsistentmigrationhistory Unreviewed 0 0 0 0 0 0