Removed versionadded/changed annotations for 4.1.

2 files changed, 0 insertions, 51 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: