Removed versionadded/changed annotations for 6.0.

34 files changed, 0 insertions, 234 deletions

diff --git a/docs/howto/custom-shell.txt b/docs/howto/custom-shell.txt
index 28a75e06f6..894ff6d8d0 100644
--- a/docs/howto/custom-shell.txt
+++ b/docs/howto/custom-shell.txt
@@ -56,11 +56,6 @@ Running this customized ``shell`` command with ``verbosity=2`` would show:
       from django.urls import resolve, reverse
       from django.utils import timezone
 
-.. versionchanged:: 6.0
-
-    Automatic imports of common utilities, such as ``django.conf.settings``,
-    were added.
-
 If an overridden ``shell`` command includes paths that cannot be imported,
 these errors are shown when ``verbosity`` is set to ``1`` or higher. Duplicate
 imports are automatically handled.
diff --git a/docs/ref/contrib/admin/index.txt b/docs/ref/contrib/admin/index.txt
index 548bd5e405..e814e0aca0 100644
--- a/docs/ref/contrib/admin/index.txt
+++ b/docs/ref/contrib/admin/index.txt
@@ -3025,8 +3025,6 @@ Templates can override or extend base admin templates as described in
 
 .. attribute:: AdminSite.password_change_form
 
-    .. versionadded:: 6.0
-
     Subclass of :class:`~django.contrib.auth.forms.PasswordChangeForm` that
     will be used by the admin site password change view.
 
diff --git a/docs/ref/contrib/gis/forms-api.txt b/docs/ref/contrib/gis/forms-api.txt
index a605ac3fd8..c65fd78692 100644
--- a/docs/ref/contrib/gis/forms-api.txt
+++ b/docs/ref/contrib/gis/forms-api.txt
@@ -98,8 +98,6 @@ from other Django widget attributes.
 
 .. attribute:: BaseGeometryWidget.base_layer
 
-    .. versionadded:: 6.0
-
     A string that specifies the identifier for the default base map layer to be
     used by the corresponding JavaScript map widget. It is passed as part of
     the widget options when rendering, allowing the ``MapWidget`` to determine
@@ -157,8 +155,6 @@ Widget classes
 
     .. attribute:: base_layer
 
-        .. versionadded:: 6.0
-
         ``nasaWorldview``
 
     .. attribute:: template_name
@@ -205,8 +201,6 @@ Widget classes
 
     .. attribute:: base_layer
 
-        .. versionadded:: 6.0
-
         ``osm``
 
     .. attribute:: default_lat
@@ -238,18 +232,11 @@ Widget classes
 
     .. _FAQ answer: https://help.openstreetmap.org/questions/10920/how-to-embed-a-map-in-my-https-site
 
-    .. versionchanged:: 6.0
-
-        The ``OSMWidget`` no longer uses a custom template. Consequently, the
-        ``gis/openlayers-osm.html`` template was removed.
-
 .. _geometry-widgets-customization:
 
 Customizing the base layer used in OpenLayers-based widgets
 -----------------------------------------------------------
 
-.. versionadded:: 6.0
-
 To customize the base layer displayed in OpenLayers-based geometry widgets,
 define a new layer builder in a custom JavaScript file. For example:
 
diff --git a/docs/ref/contrib/gis/functions.txt b/docs/ref/contrib/gis/functions.txt
index 2c4d344867..b88ace5fab 100644
--- a/docs/ref/contrib/gis/functions.txt
+++ b/docs/ref/contrib/gis/functions.txt
@@ -323,8 +323,6 @@ reversed coordinates.
 ``Rotate``
 ----------
 
-.. versionadded:: 6.0
-
 .. class:: Rotate(expression, angle, origin=None, **extra)
 
 *Availability*: `PostGIS <https://postgis.net/docs/ST_Rotate.html>`__
@@ -609,10 +607,6 @@ result.
 
 __ https://en.wikipedia.org/wiki/Geohash
 
-.. versionchanged:: 6.0
-
-    MariaDB 12.0.1+ support was added.
-
 Miscellaneous
 =============
 
@@ -643,15 +637,9 @@ geometry. Returns ``True`` if its value is empty and ``False`` otherwise.
 Accepts a geographic field or expression and tests if the value is well formed.
 Returns ``True`` if its value is a valid geometry and ``False`` otherwise.
 
-.. versionchanged:: 6.0
-
-    MariaDB 12.0.1+ support was added.
-
 ``GeometryType``
 ----------------
 
-.. versionadded:: 6.0
-
 .. class:: GeometryType(expr)
 
 *Availability*: `PostGIS <https://postgis.net/docs/GeometryType.html>`__,
diff --git a/docs/ref/contrib/gis/geoquerysets.txt b/docs/ref/contrib/gis/geoquerysets.txt
index 70ac9d4d28..255aefdd84 100644
--- a/docs/ref/contrib/gis/geoquerysets.txt
+++ b/docs/ref/contrib/gis/geoquerysets.txt
@@ -205,10 +205,6 @@ MySQL       ``MBRCoveredBy(poly, geom)``
 SpatiaLite  ``CoveredBy(poly, geom)``
 ==========  =============================
 
-.. versionchanged:: 6.0
-
-    MariaDB 12.0.1+ support was added.
-
 .. fieldlookup:: covers
 
 ``covers``
@@ -395,17 +391,11 @@ MariaDB, MySQL, PostGIS, SpatiaLite  ``ST_IsValid(poly)``
 Oracle                               ``SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(poly, 0.05) = 'TRUE'``
 ===================================  ================================================================
 
-.. versionchanged:: 6.0
-
-    MariaDB 12.0.1+ support was added.
-
 .. fieldlookup:: geom_type
 
 ``geom_type``
 -------------
 
-.. versionadded:: 6.0
-
 *Availability*: `PostGIS <https://postgis.net/docs/GeometryType.html>`__,
 Oracle 23c+, MariaDB, MySQL, SpatiaLite
 
@@ -947,10 +937,6 @@ geometry column. This is analogous to a simplified version of the
 than performing a union because it rolls up geometries into a collection or
 multi object, not caring about dissolving boundaries.
 
-.. versionchanged:: 6.0
-
-    MariaDB 12.0.1+ support was added.
-
 ``Extent``
 ~~~~~~~~~~
 
diff --git a/docs/ref/contrib/gis/geos.txt b/docs/ref/contrib/gis/geos.txt
index c107e68262..31ab8f1008 100644
--- a/docs/ref/contrib/gis/geos.txt
+++ b/docs/ref/contrib/gis/geos.txt
@@ -318,8 +318,6 @@ Properties
 
 .. attribute:: GEOSGeometry.hasm
 
-    .. versionadded:: 6.0
-
     Returns a boolean indicating whether the geometry has the M dimension.
     Requires GEOS 3.12.
 
diff --git a/docs/ref/contrib/postgres/aggregates.txt b/docs/ref/contrib/postgres/aggregates.txt
index 6381f0f7eb..438613658a 100644
--- a/docs/ref/contrib/postgres/aggregates.txt
+++ b/docs/ref/contrib/postgres/aggregates.txt
@@ -209,11 +209,6 @@ General-purpose aggregation functions
         expression representing the string for separating values. For example,
         ``Value(",")``.
 
-        .. versionadded:: 6.0
-
-            Support for providing a ``Value`` or expression rather than a
-            string was added.
-
         .. deprecated:: 6.0
 
             Support for providing a string is deprecated.
diff --git a/docs/ref/contrib/postgres/operations.txt b/docs/ref/contrib/postgres/operations.txt
index e2b9af4f60..54885a0a33 100644
--- a/docs/ref/contrib/postgres/operations.txt
+++ b/docs/ref/contrib/postgres/operations.txt
@@ -52,8 +52,6 @@ them. In that case, connect to your Django database and run the query
 
     .. attribute:: hints
 
-        .. versionadded:: 6.0
-
         The optional ``hints`` argument will be passed as ``**hints`` to the
         :meth:`allow_migrate` method of database routers to assist them in
         :ref:`making routing decisions <topics-db-multi-db-hints>`.
@@ -67,8 +65,6 @@ them. In that case, connect to your Django database and run the query
 
     .. attribute:: hints
 
-        .. versionadded:: 6.0
-
         The optional ``hints`` argument will be passed as ``**hints`` to the
         :meth:`allow_migrate` method of database routers to assist them in
         :ref:`making routing decisions <topics-db-multi-db-hints>`.
@@ -82,8 +78,6 @@ them. In that case, connect to your Django database and run the query
 
     .. attribute:: hints
 
-        .. versionadded:: 6.0
-
         The optional ``hints`` argument will be passed as ``**hints`` to the
         :meth:`allow_migrate` method of database routers to assist them in
         :ref:`making routing decisions <topics-db-multi-db-hints>`.
@@ -97,8 +91,6 @@ them. In that case, connect to your Django database and run the query
 
     .. attribute:: hints
 
-        .. versionadded:: 6.0
-
         The optional ``hints`` argument will be passed as ``**hints`` to the
         :meth:`allow_migrate` method of database routers to assist them in
         :ref:`making routing decisions <topics-db-multi-db-hints>`.
@@ -112,8 +104,6 @@ them. In that case, connect to your Django database and run the query
 
     .. attribute:: hints
 
-        .. versionadded:: 6.0
-
         The optional ``hints`` argument will be passed as ``**hints`` to the
         :meth:`allow_migrate` method of database routers to assist them in
         :ref:`making routing decisions <topics-db-multi-db-hints>`.
@@ -127,8 +117,6 @@ them. In that case, connect to your Django database and run the query
 
     .. attribute:: hints
 
-        .. versionadded:: 6.0
-
         The optional ``hints`` argument will be passed as ``**hints`` to the
         :meth:`allow_migrate` method of database routers to assist them in
         :ref:`making routing decisions <topics-db-multi-db-hints>`.
@@ -143,8 +131,6 @@ them. In that case, connect to your Django database and run the query
 
     .. attribute:: hints
 
-        .. versionadded:: 6.0
-
         The optional ``hints`` argument will be passed as ``**hints`` to the
         :meth:`allow_migrate` method of database routers to assist them in
         :ref:`making routing decisions <topics-db-multi-db-hints>`.
@@ -158,8 +144,6 @@ them. In that case, connect to your Django database and run the query
 
     .. attribute:: hints
 
-        .. versionadded:: 6.0
-
         The optional ``hints`` argument will be passed as ``**hints`` to the
         :meth:`allow_migrate` method of database routers to assist them in
         :ref:`making routing decisions <topics-db-multi-db-hints>`.
@@ -173,8 +157,6 @@ them. In that case, connect to your Django database and run the query
 
     .. attribute:: hints
 
-        .. versionadded:: 6.0
-
         The optional ``hints`` argument will be passed as ``**hints`` to the
         :meth:`allow_migrate` method of database routers to assist them in
         :ref:`making routing decisions <topics-db-multi-db-hints>`.
diff --git a/docs/ref/contrib/postgres/search.txt b/docs/ref/contrib/postgres/search.txt
index 15f4909e0f..8d693f3bf0 100644
--- a/docs/ref/contrib/postgres/search.txt
+++ b/docs/ref/contrib/postgres/search.txt
@@ -119,10 +119,6 @@ Examples:
 See :ref:`postgresql-fts-search-configuration` for an explanation of the
 ``config`` parameter.
 
-.. versionchanged:: 6.0
-
-    :class:`Lexeme` objects were added.
-
 ``SearchRank``
 ==============
 
@@ -284,8 +280,6 @@ floats to :class:`SearchRank` as ``weights`` in the same order above:
 ``Lexeme``
 ==========
 
-.. versionadded:: 6.0
-
 .. class:: Lexeme(value, output_field=None, *, invert=False, prefix=False, weight=None)
 
 ``Lexeme`` objects allow search operators to be safely used with strings from
diff --git a/docs/ref/csp.txt b/docs/ref/csp.txt
index 0498d90ab8..d86c08237f 100644
--- a/docs/ref/csp.txt
+++ b/docs/ref/csp.txt
@@ -2,8 +2,6 @@
 Content Security Policy
 =======================
 
-.. versionadded:: 6.0
-
 .. module:: django.middleware.csp
    :synopsis: Middleware for Content Security Policy headers
 
diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt
index 030d2f28dd..adbd2465a7 100644
--- a/docs/ref/django-admin.txt
+++ b/docs/ref/django-admin.txt
@@ -1079,11 +1079,6 @@ flag.
 See the guide on :ref:`customizing this behavior
 <customizing-shell-auto-imports>` to add or remove automatic imports.
 
-.. versionchanged:: 6.0
-
-    Automatic imports of common utilities, such as ``django.conf.settings``,
-    were added.
-
 .. django-admin-option:: --interface {ipython,bpython,python}, -i {ipython,bpython,python}
 
 Specifies the shell to use. By default, Django will use IPython_ or bpython_ if
@@ -1274,10 +1269,6 @@ If the optional destination is provided, Django will use that name instead. If
 the directory with the given name doesn't exist, it will be created. You can
 use '.' to denote the current working directory.
 
-.. versionchanged:: 6.0
-
-    Automatic creation of the destination directory was added.
-
 For example:
 
 .. console::
@@ -1400,10 +1391,6 @@ project directory, and create ``manage.py`` and the project package within it.
 If the directory with the given name doesn't exist, it will be created. Use '.'
 to denote the current working directory.
 
-.. versionchanged:: 6.0
-
-    Automatic creation of the destination directory was added.
-
 For example:
 
 .. console::
diff --git a/docs/ref/exceptions.txt b/docs/ref/exceptions.txt
index 4ffff03457..1f3e84a7f5 100644
--- a/docs/ref/exceptions.txt
+++ b/docs/ref/exceptions.txt
@@ -36,8 +36,6 @@ Django core exception classes are defined in ``django.core.exceptions``.
 ``ObjectNotUpdated``
 --------------------
 
-.. versionadded:: 6.0
-
 .. exception:: ObjectNotUpdated
 
     The base class for :exc:`Model.NotUpdated
diff --git a/docs/ref/middleware.txt b/docs/ref/middleware.txt
index e53c510393..e262193699 100644
--- a/docs/ref/middleware.txt
+++ b/docs/ref/middleware.txt
@@ -616,8 +616,6 @@ Content Security Policy middleware
 
 .. class:: ContentSecurityPolicyMiddleware
 
-.. versionadded:: 6.0
-
 Adds support for Content Security Policy (CSP), which helps mitigate risks such
 as Cross-Site Scripting (XSS) and data injection attacks by controlling the
 sources of content that can be loaded in the browser. See the
diff --git a/docs/ref/migration-operations.txt b/docs/ref/migration-operations.txt
index b12613b952..fe33fa166d 100644
--- a/docs/ref/migration-operations.txt
+++ b/docs/ref/migration-operations.txt
@@ -195,13 +195,6 @@ if the field is nullable or if it has a default value that can be used to
 populate the recreated column. If the field is not nullable and does not have a
 default value, the operation is irreversible.
 
-.. versionchanged:: 6.0
-
-    :class:`~django.db.backends.base.schema.BaseDatabaseSchemaEditor` and
-    PostgreSQL backends no longer use ``CASCADE`` to delete dependent related
-    database objects, such as views. Any dependent objects that are not managed
-    by Django may need to be removed manually before running ``RemoveField``.
-
 ``AlterField``
 --------------
 
diff --git a/docs/ref/models/class.txt b/docs/ref/models/class.txt
index c36eeaa34f..5e3fc8b88e 100644
--- a/docs/ref/models/class.txt
+++ b/docs/ref/models/class.txt
@@ -42,8 +42,6 @@ Attributes
 ``NotUpdated``
 --------------
 
-.. versionadded:: 6.0
-
 .. exception:: Model.NotUpdated
 
     This exception is raised when :ref:`a forced update
diff --git a/docs/ref/models/expressions.txt b/docs/ref/models/expressions.txt
index 81aa3a92b2..79c939fa38 100644
--- a/docs/ref/models/expressions.txt
+++ b/docs/ref/models/expressions.txt
@@ -236,12 +236,6 @@ MariaDB). For example:
     >>> reporter.stories_filed  # This triggers a refresh query on MySQL/MariaDB.
     14  # Assuming the database value was 13 when the object was saved.
 
-.. versionchanged:: 6.0
-
-    In previous versions of Django, ``F()`` objects were not refreshed from the
-    database on :meth:`~Model.save` which resulted in them being evaluated and
-    persisted every time the instance was saved.
-
 Using ``F()`` in filters
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -490,8 +484,6 @@ The ``Aggregate`` API is as follows:
 
     .. attribute:: allow_order_by
 
-        .. versionadded:: 6.0
-
         A class attribute determining whether or not this aggregate function
         allows passing a ``order_by`` keyword argument. If set to ``False``
         (default), ``TypeError`` is raised if ``order_by`` is passed as a value
@@ -529,10 +521,6 @@ grouping) contains no entries.
 The ``**extra`` kwargs are ``key=value`` pairs that can be interpolated
 into the ``template`` attribute.
 
-.. versionchanged:: 6.0
-
-    The ``order_by`` argument was added.
-
 Creating your own Aggregate Functions
 -------------------------------------
 
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index 4405d91daf..55cf3e7d34 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -1366,12 +1366,6 @@ materialized view.
 .. _PostgreSQL: https://www.postgresql.org/docs/current/ddl-generated-columns.html
 .. _SQLite: https://www.sqlite.org/gencol.html#limitations
 
-.. versionchanged:: 6.0
-
-    ``GeneratedField``\s are now automatically refreshed from the database on
-    backends that support it (SQLite, PostgreSQL, and Oracle) and marked as
-    deferred otherwise.
-
 :attr:`~Field.null` has no effect on ``GeneratedField`` since whether the
 column is nullable depends on the database and expression used.
 
diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt
index 8b9fb1aff4..5a9bf421d4 100644
--- a/docs/ref/models/instances.txt
+++ b/docs/ref/models/instances.txt
@@ -610,12 +610,6 @@ You can pass ``force_insert=(models.Model,)`` to force an ``INSERT`` statement
 for all parents. By default, ``force_insert=True`` only forces the insertion of
 a new row for the current model.
 
-.. versionchanged:: 6.0
-
-    When a forced update does not affect any rows a
-    :exc:`~django.db.models.Model.NotUpdated` exception is raised. On previous
-    versions a generic :exc:`django.db.DatabaseError` was raised.
-
 It should be very rare that you'll need to use these parameters. Django will
 almost always do the right thing and trying to override that will lead to
 errors that are difficult to track down. This feature is for advanced use
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 081a0d6a99..93bddf90b0 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -4019,8 +4019,6 @@ by the aggregate.
 ``AnyValue``
 ~~~~~~~~~~~~
 
-.. versionadded:: 6.0
-
 .. class:: AnyValue(expression, output_field=None, filter=None, default=None, **extra)
 
     Returns an arbitrary value from the non-null input values.
@@ -4225,8 +4223,6 @@ by the aggregate.
 ``StringAgg``
 ~~~~~~~~~~~~~
 
-.. versionadded:: 6.0
-
 .. class:: StringAgg(expression, delimiter, output_field=None, distinct=False, filter=None, order_by=None, default=None, **extra)
 
     Returns the input values concatenated into a string, separated by the
diff --git a/docs/ref/paginator.txt b/docs/ref/paginator.txt
index 549b9f4cd6..01def53295 100644
--- a/docs/ref/paginator.txt
+++ b/docs/ref/paginator.txt
@@ -170,8 +170,6 @@ Attributes
 ``AsyncPaginator`` class
 ========================
 
-.. versionadded:: 6.0
-
 .. class:: AsyncPaginator(object_list, per_page, orphans=0, allow_empty_first_page=True, error_messages=None)
 
     Asynchronous version of :class:`Paginator`.
@@ -259,8 +257,6 @@ Attributes
 ``AsyncPage`` class
 ===================
 
-.. versionadded:: 6.0
-
 .. class:: AsyncPage(object_list, number, paginator)
 
     Asynchronous version of :class:`Page`.
diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt
index 97c16717fe..95cdb217f0 100644
--- a/docs/ref/settings.txt
+++ b/docs/ref/settings.txt
@@ -56,10 +56,6 @@ Each item in the list should be an email address string. Example::
 
     ADMINS = ["john@example.com", '"Ng, Mary" <mary@example.com>']
 
-.. versionchanged:: 6.0
-
-    In older versions, required a list of (name, address) tuples.
-
 .. setting:: ALLOWED_HOSTS
 
 ``ALLOWED_HOSTS``
@@ -1284,11 +1280,6 @@ Default: ``'``:class:`django.db.models.BigAutoField`\ ``'``
 Default primary key field type to use for models that don't have a field with
 :attr:`primary_key=True <django.db.models.Field.primary_key>`.
 
-.. versionchanged:: 6.0
-
-    In older versions, the default value is
-    :class:`django.db.models.AutoField`.
-
 .. admonition:: Migrating auto-created through tables
 
     The value of ``DEFAULT_AUTO_FIELD`` will be respected when creating new
@@ -2242,10 +2233,6 @@ A list in the same format as :setting:`ADMINS` that specifies who should get
 broken link notifications when
 :class:`~django.middleware.common.BrokenLinkEmailsMiddleware` is enabled.
 
-.. versionchanged:: 6.0
-
-    In older versions, required a list of (name, address) tuples.
-
 .. setting:: MEDIA_ROOT
 
 ``MEDIA_ROOT``
@@ -2532,8 +2519,6 @@ have it to the value provided.
 ``SECURE_CSP``
 --------------
 
-.. versionadded:: 6.0
-
 Default: ``{}``
 
 This setting defines the directives used by the
@@ -2583,8 +2568,6 @@ This example illustrates the expected structure, using the constants defined in
 ``SECURE_CSP_REPORT_ONLY``
 --------------------------
 
-.. versionadded:: 6.0
-
 Default: ``{}``
 
 This setting is just like :setting:`SECURE_CSP`, but instead of enforcing the
@@ -2927,8 +2910,6 @@ backend definition in :setting:`STORAGES`.
 ``TASKS``
 ---------
 
-.. versionadded:: 6.0
-
 Default::
 
     {
@@ -3296,7 +3277,6 @@ enabled if a proxy which sets this header is in use.
 ``URLIZE_ASSUME_HTTPS``
 -----------------------
 
-.. versionadded:: 6.0
 .. deprecated:: 6.0
 
 Default: ``False``
diff --git a/docs/ref/signals.txt b/docs/ref/signals.txt
index aecd7f9a44..c39adcb47f 100644
--- a/docs/ref/signals.txt
+++ b/docs/ref/signals.txt
@@ -720,8 +720,6 @@ Arguments sent with this signal:
 Tasks signals
 =============
 
-.. versionadded:: 6.0
-
 Signals sent by the :doc:`tasks </ref/tasks>` framework.
 
 ``task_enqueued``
diff --git a/docs/ref/tasks.txt b/docs/ref/tasks.txt
index 1850c91cab..051ecd3bdc 100644
--- a/docs/ref/tasks.txt
+++ b/docs/ref/tasks.txt
@@ -2,8 +2,6 @@
 Tasks
 =====
 
-.. versionadded:: 6.0
-
 .. module:: django.tasks
    :synopsis: Django's built-in background Task system.
 
diff --git a/docs/ref/templates/api.txt b/docs/ref/templates/api.txt
index bd04c87ef2..2d22f33795 100644
--- a/docs/ref/templates/api.txt
+++ b/docs/ref/templates/api.txt
@@ -809,8 +809,6 @@ tag for protection against :doc:`Cross Site Request Forgeries
 
 .. function:: csp(request)
 
-.. versionadded:: 6.0
-
 If this processor is enabled, every ``RequestContext`` will contain a variable
 ``csp_nonce``, providing a securely generated, request-specific nonce suitable
 for use under a Content Security Policy. See :ref:`CSP nonce usage <csp-nonce>`
diff --git a/docs/ref/templates/builtins.txt b/docs/ref/templates/builtins.txt
index 6f491e2e77..a530d4e1d0 100644
--- a/docs/ref/templates/builtins.txt
+++ b/docs/ref/templates/builtins.txt
@@ -458,10 +458,6 @@ Variable                    Description
                             the current one
 ==========================  ===============================================
 
-.. versionchanged:: 6.0
-
-    The variable ``forloop.length`` was added.
-
 ``for`` ... ``empty``
 ---------------------
 
@@ -992,8 +988,6 @@ output (as a string) inside a variable. This is useful if you want to use
 ``partial``
 -----------
 
-.. versionadded:: 6.0
-
 Renders a template fragment that was defined with :ttag:`partialdef`, inserting
 the matching partial at this location.
 
@@ -1023,8 +1017,6 @@ rendered three times:
 ``partialdef``
 --------------
 
-.. versionadded:: 6.0
-
 Defines a reusable template fragment that can be rendered multiple times within
 the same template or accessed directly via :ref:`template loading or inclusion
 <template-partials-direct-access>`.
@@ -1088,10 +1080,6 @@ links, and an empty result could prevent the page from reloading as expected.
     ``request`` object into the template context, or provide a ``QueryDict``
     instance to this tag.
 
-.. versionchanged:: 6.0
-
-    A ``?`` was prepended to the query string for empty results.
-
 Basic usage
 ~~~~~~~~~~~
 
@@ -1167,10 +1155,6 @@ If all keys are removed by setting them to ``None``, this outputs ``?``:
 Similarly, if all positional arguments are empty and keyword arguments do not
 contribute any new params, the output will also be ``?``.
 
-.. versionchanged:: 6.0
-
-    Support for multiple positional mapping arguments was added.
-
 Dynamic usage
 ~~~~~~~~~~~~~
 
diff --git a/docs/ref/templates/language.txt b/docs/ref/templates/language.txt
index d80c2f6bd7..38f1f91e90 100644
--- a/docs/ref/templates/language.txt
+++ b/docs/ref/templates/language.txt
@@ -481,8 +481,6 @@ wouldn't know which one of the blocks' content to use.
 Template partials
 =================
 
-.. versionadded:: 6.0
-
 Template partials define reusable template fragments within a template file.
 They are self-contained components that can be rendered multiple times within
 the same template, helping to avoid repetition and maintain consistent output.
diff --git a/docs/topics/checks.txt b/docs/topics/checks.txt
index e22415e6d6..3c8a2d920f 100644
--- a/docs/topics/checks.txt
+++ b/docs/topics/checks.txt
@@ -197,10 +197,6 @@ method::
             # ... your own checks ...
             return errors
 
-.. versionchanged:: 6.0
-
-    In older versions, constraints didn't implement a ``check()`` method.
-
 Writing tests
 -------------
 
diff --git a/docs/topics/db/aggregation.txt b/docs/topics/db/aggregation.txt
index 8d8fff0211..be6234f4e0 100644
--- a/docs/topics/db/aggregation.txt
+++ b/docs/topics/db/aggregation.txt
@@ -748,7 +748,3 @@ example above because they can detect the functional dependency. In general,
 ``AnyValue`` is useful when dealing with select list columns that involve
 non-aggregate functions or complex expressions not recognized by the database
 as functionally dependent on the columns in the grouping clause.
-
-.. versionchanged:: 6.0
-
-    The :class:`~django.db.models.AnyValue` aggregate was added.
diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt
index 4070ab9066..cbfa3c1949 100644
--- a/docs/topics/db/queries.txt
+++ b/docs/topics/db/queries.txt
@@ -1188,10 +1188,6 @@ directly, but you can still use dictionary unpacking to use it in a query:
 
     Negative JSON array indices are not supported.
 
-.. versionchanged:: 6.0
-
-    SQLite support for negative JSON array indices was added.
-
 .. versionchanged:: 6.1
 
     Oracle 21c+ support for negative JSON array indices was added.
diff --git a/docs/topics/email.txt b/docs/topics/email.txt
index 18b682768f..3aa5284379 100644
--- a/docs/topics/email.txt
+++ b/docs/topics/email.txt
@@ -516,11 +516,6 @@ email backend API :ref:`provides an alternative
       :class:`EmailAttachment`, or a tuple with attributes
       ``(filename, content, mimetype)``.
 
-      .. versionchanged:: 6.0
-
-          Support for :class:`~email.message.MIMEPart` objects in the
-          ``attachments`` list was added.
-
       .. deprecated:: 6.0
 
           Support for Python's legacy :class:`~email.mime.base.MIMEBase`
@@ -613,11 +608,6 @@ email backend API :ref:`provides an alternative
         you'll probably want to override this method to put the content you
         want into the Python EmailMessage object.
 
-        .. versionchanged:: 6.0
-
-            The ``policy`` keyword argument was added and the return type was
-            updated to an instance of :class:`~email.message.EmailMessage`.
-
     .. method:: recipients()
 
         Returns a list of all the recipients of the message, whether they're
@@ -685,11 +675,6 @@ email backend API :ref:`provides an alternative
           Python's :meth:`email.contentmanager.set_content` documentation
           describes the supported arguments for ``MIMEPart.set_content()``.
 
-          .. versionchanged:: 6.0
-
-              Support for :class:`~email.message.MIMEPart` attachments was
-              added.
-
           .. deprecated:: 6.0
 
               Support for :class:`email.mime.base.MIMEBase` attachments is
@@ -847,12 +832,6 @@ to "/contact/thanks/" when it's done::
             # to get proper validation errors.
             return HttpResponse("Make sure all fields are entered and valid.")
 
-
-.. versionchanged:: 6.0
-
-    Older versions raised ``django.core.mail.BadHeaderError`` for some
-    invalid headers. This has been replaced with :exc:`!ValueError`.
-
 .. _Header injection: http://www.nyphp.org/phundamentals/8_Preventing-Email-Header-Injection.html
 
 .. _topics-sending-multiple-emails:
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index f68f512cdd..285fb192cd 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -756,10 +756,6 @@ You can then transition the squashed migration to a normal migration by:
     future, you should remove references to it from Django’s migrations table
     with the :option:`migrate --prune` option.
 
-.. versionchanged:: 6.0
-
-    Support for squashing squashed migrations was added.
-
 .. _migration-serializing:
 
 Serializing values
@@ -807,10 +803,6 @@ Django can serialize the following:
 - Anything with a custom ``deconstruct()`` method
   (:ref:`see below <custom-deconstruct-method>`)
 
-.. versionchanged:: 6.0
-
-    Serialization support for :class:`zoneinfo.ZoneInfo` instances was added.
-
 Django cannot serialize:
 
 - Nested classes
diff --git a/docs/topics/security.txt b/docs/topics/security.txt
index ea3021c26d..3a3d79b8a8 100644
--- a/docs/topics/security.txt
+++ b/docs/topics/security.txt
@@ -303,8 +303,6 @@ Form Submissions
 Content Security Policy
 =======================
 
-.. versionadded:: 6.0
-
 Content Security Policy (CSP) is a browser security mechanism that helps
 protect web applications against attacks such as cross-site scripting (XSS) and
 other content injection attacks.
diff --git a/docs/topics/tasks.txt b/docs/topics/tasks.txt
index d3bc54f6b4..c21ad7e84e 100644
--- a/docs/topics/tasks.txt
+++ b/docs/topics/tasks.txt
@@ -2,10 +2,6 @@
 Django's Tasks framework
 ========================
 
-.. versionadded:: 6.0
-
-    For older Django versions, the :pypi:`django-tasks` backport is available.
-
 For a web application, there's often more than just turning HTTP requests into
 HTTP responses. For some functionality, it may be beneficial to run code
 outside the request-response cycle.
diff --git a/docs/topics/templates.txt b/docs/topics/templates.txt
index 4ddb59d7c4..1d9e392268 100644
--- a/docs/topics/templates.txt
+++ b/docs/topics/templates.txt
@@ -327,12 +327,6 @@ The ``django.template.loader`` module defines two functions to load templates.
     See :ref:`template-partials` for more information about defining and using
     template fragments.
 
-    .. versionchanged:: 6.0
-
-        Support for loading template partials when using the
-        :class:`~django.template.backends.django.DjangoTemplates` backend was
-        added.
-
 .. function:: select_template(template_name_list, using=None)
 
     ``select_template()`` is just like ``get_template()``, except it takes a