Fixed #27380 -- Added "raw" argument to m2m_changed signals.

1 files changed, 7 insertions, 2 deletions

diff --git a/docs/topics/db/fixtures.txt b/docs/topics/db/fixtures.txt
index 6066d34f8e..9e91e0d845 100644
--- a/docs/topics/db/fixtures.txt
+++ b/docs/topics/db/fixtures.txt
@@ -118,8 +118,9 @@ How fixtures are saved to the database
 
 When fixture files are processed, the data is saved to the database as is.
 Model defined :meth:`~django.db.models.Model.save` methods are not called, and
-any :data:`~django.db.models.signals.pre_save` or
-:data:`~django.db.models.signals.post_save` signals will be called with
+any :data:`~django.db.models.signals.pre_save`,
+:data:`~django.db.models.signals.post_save`, or
+:data:`~django.db.models.signals.m2m_changed` signals will be called with
 ``raw=True`` since the instance only contains attributes that are local to the
 model. You may, for example, want to disable handlers that access
 related fields that aren't present during fixture loading and would otherwise
@@ -163,6 +164,10 @@ You could also write a decorator to encapsulate this logic::
 Just be aware that this logic will disable the signals whenever fixtures are
 deserialized, not just during :djadmin:`loaddata`.
 
+.. versionchanged:: 6.1
+
+    The ``raw`` argument was added to ``m2m_changed`` signals.
+
 Compressed fixtures
 ===================