Remove versionadded / versionchanged annotations for 6.0

docs/advanced_topics/customisation/page_editing_interface.md

@@ -238,10 +238,6 @@ so the form field for a model field can be overridden by adding it to the custom
 
 ## Customizing the generated copy page form
 
-```{versionadded} 6.0
-
-```
-
 ```{eval-rst}
 .. class:: wagtail.admin.forms.CopyForm
 ```

docs/extending/generic_views.md

@@ -99,10 +99,6 @@ If neither `panels` nor `edit_handler` is defined and the {meth}`~ModelViewSet.g
 
 ### Copy view
 
-```{versionadded} 6.0
-
-```
-
 The copy view is enabled by default and will be accessible by users with the 'add' permission on the model. To disable it, set {attr}`~.ModelViewSet.copy_view_enabled` to `False`.
 
 The view's form will be generated in the same way as create or edit forms. To use a custom form, override the `copy_view_class` and modify the `form_class` property on that class.

docs/reference/pages/model_reference.md

@@ -514,10 +514,6 @@ This is currently enforced via {attr}`~django.db.models.Options.unique_together`
 If your model defines a [`Meta` class](inv:django#ref/models/options) (either with a new definition or inheriting `TranslatableMixin.Meta` explicitly), be mindful when setting `unique_together` or {attr}`~django.db.models.Options.constraints`. Ensure that there is either a `unique_together` or a `UniqueConstraint` (not both) on `translation_key` and `locale`. There is a system check for this.
 ```
 
-```{versionchanged} 6.0
-The system check for `translation_key` and `locale` unique key constraint now allows a `UniqueConstraint` in `Meta.constraints` instead of `unique_together` in `Meta`.
-```
-
 ### Methods and properties
 
 ```{eval-rst}

docs/reference/streamfield/blocks.md

@@ -32,11 +32,6 @@ body = StreamField([
 })
 ```
 
-```{versionchanged} 6.0
-
-The `use_json_field` argument is no longer required.
-```
-
 ## Block options
 
 All block definitions accept the following optional keyword arguments:

docs/topics/snippets/customizing.md

@@ -95,10 +95,6 @@ Additionally, you can customize the base queryset for the listing view by overri
 
 ## Copy view
 
-```{versionadded} 6.0
-
-```
-
 The copy view is enabled by default and will be accessible by users with the 'add' permission on the model. To disable it, set {attr}`~.ModelViewSet.copy_view_enabled` to `False`. Refer to [the copy view customizations for `ModelViewSet`](modelviewset_copy) for more details.
 
 ## Inspect view

docs/topics/streamfield.md

@@ -580,10 +580,6 @@ hero_image = my_page.body.first_block_by_name('image')
 
 ## Search considerations
 
-```{versionadded} 6.0
-
-```
-
 Like any other field, content in a StreamField can be made searchable by adding the field to the model's search_fields definition - see {ref}`wagtailsearch_indexing_fields`. By default, all text content from the stream will be added to the search index. If you wish to exclude certain block types from being indexed, pass the keyword argument `search_index=False` as part of the block's definition. For example:
 
 ```python