Removed versionadded/changed annotations for 4.1.

10 files changed, 0 insertions, 106 deletions

diff --git a/docs/ref/contrib/admin/index.txt b/docs/ref/contrib/admin/index.txt
index 28a874b602..5a2b33ecca 100644
--- a/docs/ref/contrib/admin/index.txt
+++ b/docs/ref/contrib/admin/index.txt
@@ -1186,22 +1186,6 @@ subclass::
     :meth:`ModelAdmin.get_search_results` to provide additional or alternate
     search behavior.
 
-    .. versionchanged:: 4.1
-
-        Searches using multiple search terms are now applied in a single call
-        to ``filter()``, rather than in sequential ``filter()`` calls.
-
-        For multi-valued relationships, this means that rows from the related
-        model must match all terms rather than any term. For example, if
-        ``search_fields`` is set to ``['child__name', 'child__age']``, and a
-        user searches for ``'Jamal 17'``, parent rows will be returned only if
-        there is a relationship to some 17-year-old child named Jamal, rather
-        than also returning parents who merely have a younger or older child
-        named Jamal in addition to some other 17-year-old.
-
-        See the :ref:`spanning-multi-valued-relationships` topic for more
-        discussion of this difference.
-
 .. attribute:: ModelAdmin.search_help_text
 
     Set ``search_help_text`` to specify a descriptive text for the search box
@@ -1418,22 +1402,6 @@ templates used by the :class:`ModelAdmin` views:
     field, for example ``... OR UPPER("polls_choice"."votes"::text) = UPPER('4')``
     on PostgreSQL.
 
-    .. versionchanged:: 4.1
-
-        Searches using multiple search terms are now applied in a single call
-        to ``filter()``, rather than in sequential ``filter()`` calls.
-
-        For multi-valued relationships, this means that rows from the related
-        model must match all terms rather than any term. For example, if
-        ``search_fields`` is set to ``['child__name', 'child__age']``, and a
-        user searches for ``'Jamal 17'``, parent rows will be returned only if
-        there is a relationship to some 17-year-old child named Jamal, rather
-        than also returning parents who merely have a younger or older child
-        named Jamal in addition to some other 17-year-old.
-
-        See the :ref:`spanning-multi-valued-relationships` topic for more
-        discussion of this difference.
-
 .. _Solr: https://solr.apache.org
 .. _Haystack: https://haystacksearch.org
 
@@ -1999,10 +1967,6 @@ Other methods
     Django view for the page that shows the modification history for a given
     model instance.
 
-    .. versionchanged:: 4.1
-
-        Pagination was added.
-
 Unlike the hook-type ``ModelAdmin`` methods detailed in the previous section,
 these five methods are in reality designed to be invoked as Django views from
 the admin application URL dispatching handler to render the pages that deal
@@ -2725,11 +2689,6 @@ linked to the document in ``{% block dark-mode-vars %}``.
 
 .. _prefers-color-scheme: https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme
 
-.. versionchanged:: 4.1
-
-    The dark mode variables were moved to a separate stylesheet and template
-    block.
-
 ``AdminSite`` objects
 =====================
 
@@ -2900,10 +2859,6 @@ Templates can override or extend base admin templates as described in
     You can override this method to change the default order on the admin index
     page.
 
-    .. versionchanged:: 4.1
-
-        The ``app_label`` argument was added.
-
 .. method:: AdminSite.has_permission(request)
 
     Returns ``True`` if the user for the given ``HttpRequest`` has permission
diff --git a/docs/ref/contrib/admin/javascript.txt b/docs/ref/contrib/admin/javascript.txt
index ce48d5ac53..9f3a5ca4f6 100644
--- a/docs/ref/contrib/admin/javascript.txt
+++ b/docs/ref/contrib/admin/javascript.txt
@@ -12,12 +12,6 @@ in the admin change form. The ``formset:added`` and ``formset:removed`` events
 allow this. ``event.detail.formsetName`` is the formset the row belongs to.
 For the ``formset:added`` event, ``event.target`` is the newly added row.
 
-.. versionchanged:: 4.1
-
-    In older versions, the event was a ``jQuery`` event with ``$row`` and
-    ``formsetName`` parameters. It is now a JavaScript ``CustomEvent`` with
-    parameters set in ``event.detail``.
-
 In your custom ``change_form.html`` template, extend the
 ``admin_change_form_document_ready`` block and add the event listener code:
 
diff --git a/docs/ref/contrib/auth.txt b/docs/ref/contrib/auth.txt
index abcf3905c9..241a0219bd 100644
--- a/docs/ref/contrib/auth.txt
+++ b/docs/ref/contrib/auth.txt
@@ -666,10 +666,6 @@ The following backends are available in :mod:`django.contrib.auth.backends`:
         if it wasn't provided to :func:`~django.contrib.auth.authenticate`
         (which passes it on to the backend).
 
-        .. versionchanged:: 4.1
-
-            The ``created`` argument was added.
-
     .. method:: user_can_authenticate()
 
         Returns whether the user is allowed to authenticate. This method
diff --git a/docs/ref/contrib/gis/geos.txt b/docs/ref/contrib/gis/geos.txt
index 8f32883cc1..764dd80e5d 100644
--- a/docs/ref/contrib/gis/geos.txt
+++ b/docs/ref/contrib/gis/geos.txt
@@ -659,8 +659,6 @@ Other Properties & Methods
 
 .. method:: GEOSGeometry.make_valid()
 
-    .. versionadded:: 4.1
-
     Returns a valid :class:`GEOSGeometry` equivalent, trying not to lose any of
     the input vertices. If the geometry is already valid, it is returned
     untouched. This is similar to the
@@ -680,10 +678,6 @@ Other Properties & Methods
         >>> print(g)
         MULTIPOINT (2 2, 1 1, 0 0)
 
-    .. versionchanged:: 4.1
-
-        The ``clone`` argument was added.
-
 ``Point``
 ---------
 
diff --git a/docs/ref/contrib/postgres/aggregates.txt b/docs/ref/contrib/postgres/aggregates.txt
index 55ec952fa2..79cfa8432b 100644
--- a/docs/ref/contrib/postgres/aggregates.txt
+++ b/docs/ref/contrib/postgres/aggregates.txt
@@ -78,8 +78,6 @@ General-purpose aggregation functions
 ``BitXor``
 ----------
 
-.. versionadded:: 4.1
-
 .. class:: BitXor(expression, filter=None, default=None, **extra)
 
     Returns an ``int`` of the bitwise ``XOR`` of all non-null input values, or
diff --git a/docs/ref/contrib/postgres/constraints.txt b/docs/ref/contrib/postgres/constraints.txt
index b8a744f2b4..5c50ddd3a5 100644
--- a/docs/ref/contrib/postgres/constraints.txt
+++ b/docs/ref/contrib/postgres/constraints.txt
@@ -30,11 +30,6 @@ PostgreSQL supports additional data integrity constraints available from the
     Exclusion constraints are checked during the :ref:`model validation
     <validating-objects>`.
 
-    .. versionchanged:: 4.1
-
-        In older versions, exclusion constraints were not checked during model
-        validation.
-
 ``name``
 --------
 
@@ -71,10 +66,6 @@ For example::
 
 creates an exclusion constraint on ``circle`` using ``circle_ops``.
 
-.. versionchanged:: 4.1
-
-    Support for the ``OpClass()`` expression was added.
-
 .. _operator class: https://www.postgresql.org/docs/current/indexes-opclass.html
 
 ``index_type``
@@ -142,11 +133,6 @@ used for queries that select only included fields
 ``include`` is supported for GiST indexes. PostgreSQL 14+ also supports
 ``include`` for SP-GiST indexes.
 
-.. versionchanged:: 4.1
-
-    Support for covering exclusion constraints using SP-GiST indexes on
-    PostgreSQL 14+ was added.
-
 ``opclasses``
 -------------
 
@@ -176,8 +162,6 @@ creates an exclusion constraint on ``circle`` using ``circle_ops``.
 ``violation_error_message``
 ---------------------------
 
-.. versionadded:: 4.1
-
 The error message used when ``ValidationError`` is raised during
 :ref:`model validation <validating-objects>`. Defaults to
 :attr:`.BaseConstraint.violation_error_message`.
diff --git a/docs/ref/contrib/postgres/fields.txt b/docs/ref/contrib/postgres/fields.txt
index 34ad06a09a..f63bde45bb 100644
--- a/docs/ref/contrib/postgres/fields.txt
+++ b/docs/ref/contrib/postgres/fields.txt
@@ -586,8 +586,6 @@ the ``default_bounds`` argument.
 
     .. attribute:: DecimalRangeField.default_bounds
 
-        .. versionadded:: 4.1
-
         Optional. The value of ``bounds`` for list and tuple inputs. The
         default is lower bound included, upper bound excluded, that is ``[)``
         (see the PostgreSQL documentation for details about
@@ -606,8 +604,6 @@ the ``default_bounds`` argument.
 
     .. attribute:: DateTimeRangeField.default_bounds
 
-        .. versionadded:: 4.1
-
         Optional. The value of ``bounds`` for list and tuple inputs. The
         default is lower bound included, upper bound excluded, that is ``[)``
         (see the PostgreSQL documentation for details about
diff --git a/docs/ref/contrib/postgres/indexes.txt b/docs/ref/contrib/postgres/indexes.txt
index 4eb38e71d5..d428975c1a 100644
--- a/docs/ref/contrib/postgres/indexes.txt
+++ b/docs/ref/contrib/postgres/indexes.txt
@@ -133,10 +133,6 @@ available from the ``django.contrib.postgres.indexes`` module.
     Provide an integer value from 10 to 100 to the fillfactor_ parameter to
     tune how packed the index pages will be. PostgreSQL's default is 90.
 
-    .. versionchanged:: 4.1
-
-        Support for covering SP-GiST indexes on PostgreSQL 14+ was added.
-
     .. _fillfactor: https://www.postgresql.org/docs/current/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS
 
 ``OpClass()`` expressions
@@ -178,8 +174,4 @@ available from the ``django.contrib.postgres.indexes`` module.
 
     creates an exclusion constraint on ``circle`` using ``circle_ops``.
 
-    .. versionchanged:: 4.1
-
-        Support for exclusion constraints was added.
-
     .. _operator class: https://www.postgresql.org/docs/current/indexes-opclass.html
diff --git a/docs/ref/contrib/sitemaps.txt b/docs/ref/contrib/sitemaps.txt
index 7dc3dced51..8cd9a22304 100644
--- a/docs/ref/contrib/sitemaps.txt
+++ b/docs/ref/contrib/sitemaps.txt
@@ -296,8 +296,6 @@ Note:
 
     .. method:: Sitemap.get_latest_lastmod()
 
-        .. versionadded:: 4.1
-
         **Optional.** A method that returns the latest value returned by
         :attr:`~Sitemap.lastmod`. This function is used to add the ``lastmod``
         attribute to :ref:`Sitemap index context
@@ -465,10 +463,6 @@ with a caching decorator -- you must name your sitemap view and pass
              {'sitemaps': sitemaps}, name='sitemaps'),
     ]
 
-.. versionchanged:: 4.1
-
-    Use of the ``Last-Modified`` header was added.
-
 Template customization
 ======================
 
@@ -516,11 +510,6 @@ attributes:
 - ``lastmod``: Populated by the :meth:`~Sitemap.get_latest_lastmod`
   method for each sitemap.
 
-.. versionchanged:: 4.1
-
-    The context was changed to a list of objects with ``location`` and optional
-    ``lastmod`` attributes.
-
 Sitemap
 -------
 
diff --git a/docs/ref/contrib/staticfiles.txt b/docs/ref/contrib/staticfiles.txt
index a72e2ae286..c4295b0d68 100644
--- a/docs/ref/contrib/staticfiles.txt
+++ b/docs/ref/contrib/staticfiles.txt
@@ -330,10 +330,6 @@ argument. For example::
             manifest_storage = StaticFilesStorage(location=settings.BASE_DIR)
             super().__init__(*args, manifest_storage=manifest_storage, **kwargs)
 
-.. versionchanged:: 4.1
-
-    Support for finding paths in CSS source map comments was added.
-
 .. versionchanged:: 4.2
 
     Support for finding paths to JavaScript modules in ``import`` and