Squash migrations through v3.6 #8551

Closed
opened 2025-12-29 20:38:03 +01:00 by adam · 1 comment
Owner

Originally created by @jeremystretch on GitHub (Aug 31, 2023).

Originally assigned to: @jeremystretch on GitHub.

Proposed Changes

Squash all existing migrations up to the v3.6.0 release. (This is a repeat of what we did for the v3.0 release under #6471.)

Justification

Squashing migrations optimizes necessary changes to the database schema and reduces installation time.

Originally created by @jeremystretch on GitHub (Aug 31, 2023). Originally assigned to: @jeremystretch on GitHub. ### Proposed Changes Squash all existing migrations up to the v3.6.0 release. (This is a repeat of what we did for the v3.0 release under #6471.) ### Justification Squashing migrations optimizes necessary changes to the database schema and reduces installation time.
adam added the status: acceptedtype: housekeeping labels 2025-12-29 20:38:03 +01:00
adam closed this issue 2025-12-29 20:38:03 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jan 22, 2024):

Re-opening this as there's an issue with the way squashed migrations are split:

django.db.migrations.exceptions.InconsistentMigrationHistory: Migration circuits.0004_squashed is
applied before its dependency circuits.0003_squashed on database 'default'.
@jeremystretch commented on GitHub (Jan 22, 2024): Re-opening this as there's an issue with the way squashed migrations are split: ``` django.db.migrations.exceptions.InconsistentMigrationHistory: Migration circuits.0004_squashed is applied before its dependency circuits.0003_squashed on database 'default'. ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8551