Remove old versionadded / versionchanged notes

docs/advanced_topics/reference_index.md

@@ -14,10 +14,6 @@ By default, the index will store references between objects managed within the W
 -   models registered as Snippets
 -   models registered with ModelAdmin
 
-```{versionchanged} 5.0
-When introduced in Wagtail 4.1, the Reference Index recorded references in all application models by default. Wagtail 5.0 reduced the scope of the default models to those specifically linked with Wagtail.
-```
-
 The reference index does not require any further configuration. However there are circumstances where it may be necessary to add or remove models from the index.
 
 (registering_a_model_for_indexing)=

docs/advanced_topics/streamfield_validation.md

@@ -2,10 +2,6 @@
 
 # StreamField validation
 
-```{versionadded} 5.0
-Support for custom validation logic on StreamField blocks was improved and simplified.
-```
-
 All StreamField blocks implement a `clean` method which accepts a block value and returns a cleaned version of that value, or raises a `ValidationError` if the value fails validation. Built-in validation rules, such as checking that a URLBlock value is a correctly-formatted URL, are implemented through this method. Additionally, for blocks that act as containers for other blocks, such as StructBlock, the `clean` method recursively calls the `clean` methods of its child blocks and handles raising validation errors back to the caller as required.
 
 The `clean` method can be overridden on block subclasses to implement custom validation logic. For example, a StructBlock that requires either one of its child blocks to be filled in could be implemented as follows:

docs/reference/contrib/searchpromotions.md

@@ -112,7 +112,3 @@ def search(request):
 ```
 
 On high traffic websites, the stored queries and daily hits logs may get large and you may want to clean out old records. This command cleans out all search query logs that are more than one week old (or a number of days configurable through the [`WAGTAILSEARCH_HITS_MAX_AGE`](wagtailsearch_hits_max_age) setting).
-
-```{versionadded} 5.0
-This management command was renamed from `search_garbage_collect`.
-```

docs/reference/management_commands.md

@@ -154,10 +154,6 @@ Displays a summary of the contents of the references index. This shows the numbe
 ./manage.py search_garbage_collect
 ```
 
-```{versionchanged} 5.0
-This management command has been renamed to [`searchpromotions_garbage_collect`](searchpromotions_garbage_collect). See the [upgrade consideration](wagtailsearch_query_migration) for more details.
-```
-
 (wagtail_update_image_renditions)=
 
 ## wagtail_update_image_renditions

docs/reference/streamfield/blocks.md

@@ -18,10 +18,6 @@ This document details the block types provided by Wagtail for use in [StreamFiel
    :param collapsed: When true, all blocks are initially collapsed.
 ```
 
-```{versionchanged} 5.0
-The `use_json_field` argument must be set to `True`, except in migrations created prior to Wagtail 5.0.
-```
-
 ```python
 body = StreamField([
     ('heading', blocks.CharBlock(form_classname="title")),

docs/topics/search/indexing.md

@@ -106,10 +106,6 @@ These are used for performing full-text searches on your models, usually for tex
 
 -   **es_extra** (`dict`) - This field is to allow the developer to set or override any setting on the field in the Elasticsearch mapping. Use this if you want to make use of any Elasticsearch features that are not yet supported in Wagtail.
 
-```{versionchanged} 5.0
-The `partial_match` option has been deprecated. To index a field for partial matching, use `AutocompleteField` instead.
-```
-
 (wagtailsearch_index_autocompletefield)=
 
 ### `index.AutocompleteField`

docs/topics/search/searching.md

@@ -32,10 +32,6 @@ The `search()` method will convert your `QuerySet` into an instance of one of Wa
 
 The standard behaviour of the `search` method is to only return matches for complete words; for example, a search for "hel" will not return results containing the word "hello". The exception to this is the fallback database search backend, used when the database does not have full-text search extensions available, and no alternative backend has been specified. This performs basic substring matching, and will return results containing the search term ignoring all word boundaries.
 
-```{versionchanged} 5.0
-The Elasticsearch backend now defaults to matching on complete words. Previously, this backend performed partial matching by default, and it was necessary to pass the keyword argument `partial_match=False` to disable this. To perform searches with partial matching behaviour, you should instead use the `autocomplete` method (see below) in conjunction with `AutocompleteField`. Any occurrences of `partial_match=False` in your code can now be removed.
-```
-
 ### Autocomplete searches
 
 Wagtail provides a separate method which performs partial matching on specific autocomplete fields. This is primarily useful for suggesting pages to the user in real-time as they type their query - it is not recommended for ordinary searches, as the autocompletion will tend to add unwanted results beyond the specific term being searched for.

docs/topics/snippets/customising.md

@@ -133,10 +133,6 @@ For some common views, Wagtail also allows you to override the template used by
 
 ## Menu item
 
-```{versionadded} 5.0
-The ability to have a separate menu item was added.
-```
-
 By default, registering a snippet model will add a "Snippets" menu item to the sidebar menu. You can configure a snippet model to have its own top-level menu item in the sidebar menu by setting {attr}`~wagtail.snippets.views.snippets.SnippetViewSet.add_to_admin_menu` to `True`. Alternatively, if you want to add the menu item inside the Settings menu, you can set {attr}`~wagtail.snippets.views.snippets.SnippetViewSet.add_to_settings_menu` to `True`. The menu item will use the icon specified on the `SnippetViewSet` and it will link to the index view for the snippet model.
 
 Unless specified, the menu item will be named after the model's verbose name. You can customise the menu item's label, name, and order by setting the {attr}`~wagtail.snippets.views.snippets.SnippetViewSet.menu_label`, {attr}`~wagtail.snippets.views.snippets.SnippetViewSet.menu_name`, and {attr}`~wagtail.snippets.views.snippets.SnippetViewSet.menu_order` attributes respectively. If you would like to customise the `MenuItem` instance completely, you could override the {meth}`~wagtail.snippets.views.snippets.SnippetViewSet.get_menu_item` method.

docs/topics/streamfield.md

@@ -45,10 +45,6 @@ You can find the complete list of available block types in the [](streamfield_bl
    StreamField is not a direct replacement for other field types such as RichTextField. If you need to migrate an existing field to StreamField, refer to [](streamfield_migrating_richtext).
 ```
 
-```{versionchanged} 5.0
-The `use_json_field=True` argument is required. `use_json_field=False` is only permitted within migrations created before Wagtail 5.0. This is a temporary measure to ensure that all existing StreamFields are upgraded to the database's native JSONField support; it will be removed in a future release.
-```
-
 (streamfield_template_rendering)=
 
 ## Template rendering