django.git/tests/migrations, branch main

Refs #12529, #22325 -- Fixed ExecutorTests.test_custom_user isolation.

2026-03-14T18:11:27Z

Fixed #12529 -- Fixed migrate --run-syncdb crash for existing model with truncated db_table names.

2026-03-08T09:44:56Z

Refs #36652, #36936 -- Improved path manipulation in a migration test launching a subprocess.

2026-02-25T22:02:00Z

Added various missing test skips observed on MongoDB.

2026-02-10T21:06:49Z

Fixed #36893 -- Serialized elidable kwarg for RunSQL and RunPython operations.

2026-02-03T02:05:44Z

Fixed #36878 -- Unified data type for *_together options in ModelState.

2026-01-28T21:13:05Z

Ever since the beginning of Django's migration framework, there's been a bit of an inconsistency on how index_together and unique_together values have been stored on the ModelState[^1]. It's only really obvious, when looking at the current code for `from_model()`[^2] and the `rename_field()` state alteration code[^3]. The problem in the autodetector's detection of the `*_together` options as raised in the ticket, reinforces the inconsistency[^4]: the old value is being normalized to a set of tuples, whereas the new value is taken as-is. Why this hasn't been caught before, is likely to the fact, that we never really look at a `to_state` that comes from migration operations in the autodetector. Instead, in both usages in Django[^5], [^6] the `to_state` is a `ProjectState.from_apps()`. And that state is consistently using sets of tuples and not lists of lists. [^1]: https://github.com/django/django/commit/67dcea711e92025d0e8676b869b7ef15dbc6db73#diff-5dd147e9e978e645313dd99eab3a7bab1f1cb0a53e256843adb68aeed71e61dcR85-R87 [^2]: https://github.com/django/django/blob/b1ffa9a9d78b0c2c5ad6ed5a1d84e380d5cfd010/django/db/migrations/state.py#L842 [^3]: https://github.com/django/django/blob/b1ffa9a9d78b0c2c5ad6ed5a1d84e380d5cfd010/django/db/migrations/state.py#L340-L345 [^4]: https://github.com/django/django/blob/b1ffa9a9d78b0c2c5ad6ed5a1d84e380d5cfd010/django/db/migrations/autodetector.py#L1757-L1771 [^5]: https://github.com/django/django/blob/2351c1b12cc9cf82d642f769c774bc3ea0cc4006/django/core/management/commands/makemigrations.py#L215-L219 [^6]: https://github.com/django/django/blob/2351c1b12cc9cf82d642f769c774bc3ea0cc4006/django/core/management/commands/migrate.py#L329-L332

Applied Black's 2026 stable style.

2026-01-18T20:26:56Z

https://github.com/psf/black/releases/tag/26.1.0

Fixed #36791 -- Made MigrationAutodetector recreate through table when m2m target model changes.

2025-12-19T19:01:37Z

Co-Authored-By: Jacob Walls <38668450+jacobtylerwalls@users.noreply.github.com> Co-Authored-By: Clifford Gama

Refs #36652 -- Avoided missing imports in a temporary file generated in a migration test.

2025-12-15T20:24:57Z

Fixed #36765 -- Added support for stored GeneratedFields on Oracle 23ai/26ai (23.7+).

2025-12-13T15:38:04Z

Thanks Jacob Walls for the review.