Fixed #32676 -- Prevented migrations from rendering related field attributes when not passed during initialization.

Thanks Simon Charette for the implementation idea.

1 files changed, 12 insertions, 4 deletions

diff --git a/docs/releases/4.0.txt b/docs/releases/4.0.txt
index 831bb9b854..eecbc9e4d8 100644
--- a/docs/releases/4.0.txt
+++ b/docs/releases/4.0.txt
@@ -387,6 +387,18 @@ custom middleware::
 
 .. _Content-Security-Policy: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy
 
+Migrations autodetector changes
+-------------------------------
+
+The migrations autodetector now uses model states instead of model classes.
+Also, migration operations for ``ForeignKey`` and ``ManyToManyField`` fields no
+longer specify attributes which were not passed to the fields during
+initialization.
+
+As a side-effect, running ``makemigrations`` might generate no-op
+``AlterField`` operations for ``ManyToManyField`` and ``ForeignKey`` fields in
+some cases.
+
 Miscellaneous
 -------------
 
@@ -422,10 +434,6 @@ Miscellaneous
 * Tests that fail to load, for example due to syntax errors, now always match
   when using :option:`test --tag`.
 
-* The migrations autodetector now uses model states instead of model classes.
-  As a side-effect ``makemigrations`` might generate no-op ``AlterField``
-  operations for ``ForeignKey`` fields in some cases.
-
 * The undocumented ``django.contrib.admin.utils.lookup_needs_distinct()``
   function is renamed to ``lookup_spawns_duplicates()``.