Removed versionadded/changed annotations for 3.2.

15 files changed, 3 insertions, 95 deletions

diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt
index 3c73783b24..006b955274 100644
--- a/docs/topics/auth/customizing.txt
+++ b/docs/topics/auth/customizing.txt
@@ -1172,10 +1172,3 @@ Finally, specify the custom model as the default user model for your project
 using the :setting:`AUTH_USER_MODEL` setting in your ``settings.py``::
 
     AUTH_USER_MODEL = 'customauth.MyUser'
-
-.. versionchanged:: 3.2
-
-    In older versions, ``ReadOnlyPasswordHashField`` is not
-    :attr:`~django.forms.Field.disabled` by default and
-    ``UserChangeForm.clean_password()`` is required to return the initial
-    value, whatever the user provides.
diff --git a/docs/topics/auth/passwords.txt b/docs/topics/auth/passwords.txt
index c6383ed9a3..3124e5c745 100644
--- a/docs/topics/auth/passwords.txt
+++ b/docs/topics/auth/passwords.txt
@@ -178,8 +178,6 @@ To use scrypt_ as your default storage algorithm, do the following:
 Increasing the salt entropy
 ---------------------------
 
-.. versionadded:: 3.2
-
 Most password hashes include a salt along with their password hash in order to
 protect against rainbow table attacks. The salt itself is a random value which
 increases the size and thus the cost of the rainbow table and is currently set
diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt
index 3bc35fd51d..f56bc00ce8 100644
--- a/docs/topics/cache.txt
+++ b/docs/topics/cache.txt
@@ -158,10 +158,6 @@ permanent storage -- they're all intended to be solutions for caching, not
 storage -- but we point this out here because memory-based caching is
 particularly temporary.
 
-.. versionchanged:: 3.2
-
-    The ``PyMemcacheCache`` backend was added.
-
 .. deprecated:: 3.2
 
     The ``MemcachedCache`` backend is deprecated as ``python-memcached`` has
diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt
index 1c4e99817f..b8d6c30a27 100644
--- a/docs/topics/db/models.txt
+++ b/docs/topics/db/models.txt
@@ -274,11 +274,6 @@ sees you've explicitly set :attr:`Field.primary_key`, it won't add the automatic
 Each model requires exactly one field to have :attr:`primary_key=True
 <Field.primary_key>` (either explicitly declared or automatically added).
 
-.. versionchanged:: 3.2
-
-    In older versions, auto-created primary key fields were always
-    :class:`AutoField`\s.
-
 .. _verbose-field-names:
 
 Verbose field names
diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt
index ac425e99f4..c24c06da68 100644
--- a/docs/topics/db/queries.txt
+++ b/docs/topics/db/queries.txt
@@ -670,8 +670,6 @@ The ``F()`` objects support bitwise operations by ``.bitand()``, ``.bitor()``,
 Expressions can reference transforms
 ------------------------------------
 
-.. versionadded:: 3.2
-
 Django supports using transforms in expressions.
 
 For example, to find all ``Entry`` objects published in the same year as they
diff --git a/docs/topics/db/sql.txt b/docs/topics/db/sql.txt
index 8d3216c60d..4713fb6d50 100644
--- a/docs/topics/db/sql.txt
+++ b/docs/topics/db/sql.txt
@@ -98,11 +98,6 @@ make it very powerful.
     both rows will match. To prevent this, perform the correct typecasting
     before using the value in a query.
 
-.. versionchanged:: 3.2
-
-    The default value of the ``params`` argument was changed from ``None`` to
-    an empty tuple.
-
 Mapping query fields to model fields
 ------------------------------------
 
diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt
index bffbf94ee6..313aa7d188 100644
--- a/docs/topics/db/transactions.txt
+++ b/docs/topics/db/transactions.txt
@@ -244,10 +244,6 @@ Django provides a single API to control database transactions.
     testing durable atomic blocks in a transaction for performance reasons. Use
     :class:`django.test.TransactionTestCase` for testing durability.
 
-.. versionchanged:: 3.2
-
-    The ``durable`` argument was added.
-
 Autocommit
 ==========
 
diff --git a/docs/topics/forms/formsets.txt b/docs/topics/forms/formsets.txt
index e15f11dea0..92810091ec 100644
--- a/docs/topics/forms/formsets.txt
+++ b/docs/topics/forms/formsets.txt
@@ -131,8 +131,6 @@ validation.  See :ref:`validate_max`.
 Limiting the maximum number of instantiated forms
 =================================================
 
-.. versionadded:: 3.2
-
 The ``absolute_max`` parameter to :func:`.formset_factory` allows limiting the
 number of forms that can be instantiated when supplying ``POST`` data. This
 protects against memory exhaustion attacks using forged ``POST`` requests::
@@ -268,11 +266,6 @@ the management data by rendering ``{{ my_formset.management_form }}``
     client-side code. These fields are not required and so are not shown in
     the example ``POST`` data.
 
-.. versionchanged:: 3.2
-
-    ``formset.is_valid()`` now returns ``False`` rather than raising an
-    exception when the management form is missing or has been tampered with.
-
 ``total_form_count`` and ``initial_form_count``
 -----------------------------------------------
 
@@ -297,8 +290,6 @@ forms with JavaScript.
 ``error_messages``
 ------------------
 
-.. versionadded:: 3.2
-
 The ``error_messages`` argument lets you override the default messages that the
 formset will raise. Pass in a dictionary with keys matching the error messages
 you want to override. For example, here is the default error message when the
@@ -682,8 +673,6 @@ use with ``can_delete``::
 ``can_delete_extra``
 --------------------
 
-.. versionadded:: 3.2
-
 .. attribute:: BaseFormSet.can_delete_extra
 
 Default: ``True``
diff --git a/docs/topics/http/decorators.txt b/docs/topics/http/decorators.txt
index cabdd4f01a..cb6fa9cdac 100644
--- a/docs/topics/http/decorators.txt
+++ b/docs/topics/http/decorators.txt
@@ -127,8 +127,6 @@ client-side caching.
 Common
 ======
 
-.. versionadded:: 3.2
-
 The decorators in :mod:`django.views.decorators.common` allow per-view
 customization of :class:`~django.middleware.common.CommonMiddleware` behavior.
 
diff --git a/docs/topics/i18n/timezones.txt b/docs/topics/i18n/timezones.txt
index 6eda217f56..4c6aa58ba2 100644
--- a/docs/topics/i18n/timezones.txt
+++ b/docs/topics/i18n/timezones.txt
@@ -35,10 +35,6 @@ Time zone support uses :mod:`zoneinfo`, which is part of the Python standard
 library from Python 3.9.  The ``backports.zoneinfo`` package is automatically
 installed alongside Django if you are using Python 3.8.
 
-.. versionchanged:: 3.2
-
-    Support for non-``pytz`` timezone implementations was added.
-
 .. versionchanged:: 4.0
 
     :mod:`zoneinfo` was made the default timezone implementation. You may
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index fe19f8abdb..d7daa69281 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -754,11 +754,6 @@ Django can serialize the following:
 - Any class reference (must be in module's top-level scope)
 - Anything with a custom ``deconstruct()`` method (:ref:`see below <custom-deconstruct-method>`)
 
-.. versionchanged:: 3.2
-
-    Serialization support for pure and concrete path objects from
-    :mod:`pathlib`, and :class:`os.PathLike` instances was added.
-
 Django cannot serialize:
 
 - Nested classes
diff --git a/docs/topics/serialization.txt b/docs/topics/serialization.txt
index 586d7ff13a..f3473e0dff 100644
--- a/docs/topics/serialization.txt
+++ b/docs/topics/serialization.txt
@@ -310,8 +310,6 @@ The JSON serializer uses ``DjangoJSONEncoder`` for encoding. A subclass of
 JSONL
 -----
 
-.. versionadded:: 3.2
-
 *JSONL* stands for *JSON Lines*. With this format, objects are separated by new
 lines, and each line contains a valid JSON object. JSONL serialized data looks
 like this::
diff --git a/docs/topics/signing.txt b/docs/topics/signing.txt
index c862995633..8791697b85 100644
--- a/docs/topics/signing.txt
+++ b/docs/topics/signing.txt
@@ -101,10 +101,6 @@ generate signatures. You can use a different secret by passing it to the
     and underscores. ``algorithm`` must be an algorithm supported by
     :py:mod:`hashlib`, it defaults to ``'sha256'``.
 
-.. versionchanged:: 3.2
-
-    The ``sign_object()`` and ``unsign_object()`` methods were added.
-
 Using the ``salt`` argument
 ---------------------------
 
@@ -139,10 +135,6 @@ different salt.
 Unlike your :setting:`SECRET_KEY`, your salt argument does not need to stay
 secret.
 
-.. versionchanged:: 3.2
-
-    The ``sign_object()`` and ``unsign_object()`` methods were added.
-
 Verifying timestamped values
 ----------------------------
 
@@ -180,15 +172,11 @@ created within a specified period of time::
 
     .. method:: sign_object(obj, serializer=JSONSerializer, compress=False)
 
-        .. versionadded:: 3.2
-
         Encode, optionally compress, append current timestamp, and sign complex
         data structure (e.g. list, tuple, or dictionary).
 
     .. method:: unsign_object(signed_obj, serializer=JSONSerializer, max_age=None)
 
-        .. versionadded:: 3.2
-
         Checks if ``signed_obj`` was signed less than ``max_age`` seconds ago,
         otherwise raises ``SignatureExpired``. The ``max_age`` parameter can
         accept an integer or a :py:class:`datetime.timedelta` object.
@@ -237,7 +225,3 @@ and tuples) if you pass in a tuple, you will get a list from
 
     Reverse of ``dumps()``, raises ``BadSignature`` if signature fails.
     Checks ``max_age`` (in seconds) if given.
-
-.. versionchanged:: 3.2
-
-    The ``sign_object()`` and ``unsign_object()`` methods were added.
diff --git a/docs/topics/testing/advanced.txt b/docs/topics/testing/advanced.txt
index c0251d8368..a78f1b93fc 100644
--- a/docs/topics/testing/advanced.txt
+++ b/docs/topics/testing/advanced.txt
@@ -600,10 +600,6 @@ and tear down the test suite.
     custom arguments by calling ``parser.add_argument()`` inside the method, so
     that the :djadmin:`test` command will be able to use those arguments.
 
-    .. versionadded:: 3.2
-
-        The ``enable_faulthandler`` and ``timing`` arguments were added.
-
     .. versionadded:: 4.0
 
         The ``logger`` and ``shuffle`` arguments were added.
@@ -783,11 +779,6 @@ utility methods in the ``django.test.utils`` module.
     :ref:`serialized_rollback <test-case-serialized-rollback>` feature. If
     it's not provided, it defaults to ``aliases``.
 
-    .. versionchanged:: 3.2
-
-        The ``time_keeper`` kwarg was added, and all kwargs were made
-        keyword-only.
-
     .. versionchanged:: 4.0
 
         The ``serialized_aliases`` kwarg was added.
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index 846d428980..a99ee77cb0 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -868,18 +868,12 @@ It also provides an additional method:
     (for instance, MySQL with the MyISAM engine), ``setUpTestData()`` will be
     called before each test, negating the speed benefits.
 
-    .. versionchanged:: 3.2
-
-        Objects assigned to class attributes in ``setUpTestData()`` must
-        support creating deep copies with :py:func:`copy.deepcopy` in order to
-        isolate them from alterations performed by each test methods. In
-        previous versions of Django these objects were reused and changes made
-        to them were persisted between test methods.
+    Objects assigned to class attributes in ``setUpTestData()`` must support
+    creating deep copies with :py:func:`copy.deepcopy` in order to isolate them
+    from alterations performed by each test methods.
 
 .. classmethod:: TestCase.captureOnCommitCallbacks(using=DEFAULT_DB_ALIAS, execute=False)
 
-    .. versionadded:: 3.2
-
     Returns a context manager that captures :func:`transaction.on_commit()
     <django.db.transaction.on_commit>` callbacks for the given database
     connection. It returns a list that contains, on exit of the context, the
@@ -1706,14 +1700,6 @@ your test suite.
 
     Output in case of error can be customized with the ``msg`` argument.
 
-    .. versionchanged:: 3.2
-
-        The default value of ``transform`` argument was changed to ``None``.
-
-    .. versionadded:: 3.2
-
-        Support for direct comparison between querysets was added.
-
     .. deprecated:: 3.2
 
         If ``transform`` is not provided and ``values`` is a list of strings,