Removed versionadded/changed annotations for 5.2.

docs/ref/models/constraints.txt

@@ -293,13 +293,6 @@ If :attr:`.UniqueConstraint.fields` is set without a
 code when there are multiple fields, and to the :attr:`.Field.unique` error
 code when there is a single field.
 
-.. versionchanged:: 5.2
-
-    In older versions, the provided
-    :attr:`.UniqueConstraint.violation_error_code` was not used when
-    :attr:`.UniqueConstraint.fields` was set without a
-    :attr:`.UniqueConstraint.condition`.
-
 ``violation_error_message``
 ---------------------------
 
@@ -317,10 +310,3 @@ If :attr:`.UniqueConstraint.fields` is set without a
 :attr:`Meta.unique_together <django.db.models.Options.unique_together>` error
 message when there are multiple fields, and to the :attr:`.Field.unique` error
 message when there is a single field.
-
-.. versionchanged:: 5.2
-
-    In older versions, the provided
-    :attr:`.UniqueConstraint.violation_error_message` was not used when
-    :attr:`.UniqueConstraint.fields` was set without a
-    :attr:`.UniqueConstraint.condition`.

docs/ref/models/database-functions.txt

@@ -844,8 +844,6 @@ JSON Functions
 ``JSONArray``
 -------------
 
-.. versionadded:: 5.2
-
 .. class:: JSONArray(*expressions)
 
 Accepts a list of field names or expressions and returns a JSON array

docs/ref/models/expressions.txt

@@ -1095,8 +1095,6 @@ calling the appropriate methods on the wrapped expression.
 
     .. attribute:: set_returning
 
-        .. versionadded:: 5.2
-
         Tells Django that this expression contains a set-returning function,
         enforcing subquery evaluation. It's used, for example, to allow some
         Postgres set-returning functions (e.g. ``JSONB_PATH_QUERY``,
@@ -1105,8 +1103,6 @@ calling the appropriate methods on the wrapped expression.
 
     .. attribute:: allows_composite_expressions
 
-        .. versionadded:: 5.2
-
         Tells Django that this expression allows composite expressions, for
         example, to support :ref:`composite primary keys
         <cpk-and-database-functions>`. Defaults to ``False``.

docs/ref/models/fields.txt

@@ -564,10 +564,6 @@ alongside the old one.
 The primary key field is set to ``None`` when
 :meth:`deleting <django.db.models.Model.delete>` an object.
 
-.. versionchanged:: 5.2
-
-    The ``CompositePrimaryKey`` field was added.
-
 ``unique``
 ----------
 
@@ -716,8 +712,6 @@ isn't defined.
 ``CompositePrimaryKey``
 -----------------------
 
-.. versionadded:: 5.2
-
 .. class:: CompositePrimaryKey(*field_names, **options)
 
 A virtual field used for defining a composite primary key.
@@ -758,10 +752,6 @@ The default form widget for this field is a :class:`~django.forms.TextInput`.
         ``max_length`` for some backends. Refer to the :doc:`database backend
         notes </ref/databases>` for details.
 
-    .. versionchanged:: 5.2
-
-       Support for unlimited ``VARCHAR`` columns was added on SQLite.
-
 .. attribute:: CharField.db_collation
 
     Optional. The database collation name of the field.

docs/ref/models/instances.txt

@@ -465,11 +465,6 @@ field or fields compose the primary key for the model. You can read and set
 this value, just as you would for any other attribute, and it will update the
 correct fields in the model.
 
-.. versionchanged:: 5.2
-
-    Support for the primary key to be composed of multiple fields was added via
-    ``CompositePrimaryKey``.
-
 Explicitly specifying auto-primary-key values
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -983,8 +978,6 @@ Other attributes
 
 .. method:: Model._is_pk_set()
 
-.. versionadded:: 5.2
-
 The ``_is_pk_set()`` method returns whether the model instance's ``pk`` is set.
 It abstracts the model's primary key definition, ensuring consistent behavior
 regardless of the specific ``pk`` configuration.

docs/ref/models/meta.txt

@@ -123,8 +123,6 @@ Retrieving all field instances of a model
 Retrieving fields composing the primary key of a model
 ------------------------------------------------------
 
-.. versionadded:: 5.2
-
 .. attribute:: Options.pk_fields
 
     Returns a list of the fields composing the primary key of a model.

docs/ref/models/querysets.txt

@@ -750,11 +750,6 @@ You can also refer to fields on related models with reverse relations through
     ``"true"``, ``"false"``, and ``"null"`` strings for
     :class:`~django.db.models.JSONField` key transforms.
 
-.. versionchanged:: 5.2
-
-    The ``SELECT`` clause generated when using ``values()`` was updated to
-    respect the order of the specified ``*fields`` and ``**expressions``.
-
 ``values_list()``
 ~~~~~~~~~~~~~~~~~
 
@@ -845,11 +840,6 @@ not having any author:
     ``"true"``, ``"false"``, and ``"null"`` strings for
     :class:`~django.db.models.JSONField` key transforms.
 
-.. versionchanged:: 5.2
-
-    The ``SELECT`` clause generated when using ``values_list()`` was updated to
-    respect the order of the specified ``*fields``.
-
 ``dates()``
 ~~~~~~~~~~~
 
@@ -3125,11 +3115,6 @@ adverse effects on your database. For example, the ``ANALYZE`` flag supported
 by MariaDB, MySQL 8.0.18+, and PostgreSQL could result in changes to data if
 there are triggers or if a function is called, even for a ``SELECT`` query.
 
-.. versionchanged:: 5.2
-
-    Support for the ``memory`` and ``serialize`` options on PostgreSQL 17+ was
-    added.
-
 .. _field-lookups:
 
 ``Field`` lookups