diff --git a/docs/CHANGELOG.asciidoc b/docs/CHANGELOG.asciidoc index 271d5b9c0e05b..451d4645ff2b7 100644 --- a/docs/CHANGELOG.asciidoc +++ b/docs/CHANGELOG.asciidoc @@ -756,8 +756,6 @@ You should export the used index patterns separately. Breaking changes can prevent your application from optimal operation and performance. Before you upgrade to 7.13.0, review the breaking changes, then mitigate the impact to your application. -// tag::notable-breaking-changes[] - [discrete] [[breaking-97206]] .Remove Elastic Agent routes and related services @@ -794,8 +792,6 @@ The *Explore underlying data* context menu on dashboards is now disabled by defa To enable the *Explore underlying data* context menu, set `xpack.discoverEnhanced.actions.exploreDataInContextMenu.enabled` to `true` in kibana.yml. ==== -// end::notable-breaking-changes[] - [float] [[deprecations-7.13.0]] @@ -1326,8 +1322,6 @@ For information about the {kib} 7.12.0 release, review the following information Breaking changes can prevent your application from optimal operation and performance. Before you upgrade to 7.12.0, review the breaking changes, then mitigate the impact to your application. -// tag::notable-breaking-changes[] - [discrete] [[breaking-89632]] .Removes geo threshold alert type @@ -1371,8 +1365,6 @@ To display the cluster data in *Discover*, load documents directly from `_source . Go to `discover:searchFieldsFromSource`, then select *On*. ==== -// end::notable-breaking-changes[] - [float] [[known-issues-v7.12.0]] === Known issues @@ -1922,9 +1914,6 @@ Breaking changes can prevent your application from optimal operation and perform // The following section is re-used in the Installation and Upgrade Guide -// tag::notable-breaking-changes[] - - [discrete] [[ingestManager_renamed_fleet]] ==== Ingest Manager plugin renamed Fleet @@ -1962,8 +1951,6 @@ which drops support for glibc `2.12`-based operating systems. *via https://github.com/elastic/kibana/pull/83425[#83425]* -// end::notable-breaking-changes[] - [float] [[deprecation-v7.11.0]] === Deprecations @@ -2470,8 +2457,6 @@ Breaking changes can prevent your application from optimal operation and perform // The following section is re-used in the Installation and Upgrade Guide -// tag::notable-breaking-changes[] - [discrete] [[breaking_kibana_legacy_plugins]] @@ -2507,8 +2492,6 @@ more information about this property. *via https://github.com/elastic/kibana/pull/73805[#73805]* -// end::notable-breaking-changes[] - [discrete] [[general-plugin-API-changes-7-10]] ==== Breaking changes for plugin developers @@ -3842,8 +3825,6 @@ Breaking changes can prevent your application from optimal operation and perform // The following section is re-used in the Installation and Upgrade Guide -// tag::notable-breaking-changes[] - [float] [[breaking_kibana_keystore]] ===== `kibana.keystore` moved from the data folder to the config folder @@ -3855,8 +3836,6 @@ that path will continue to be used. *via https://github.com/elastic/kibana/pull/57856[#57856]* -// end::notable-breaking-changes[] - [float] [[general-plugin-API-changes-79]] ==== Breaking changes for plugin developers @@ -4942,9 +4921,6 @@ Breaking changes can prevent your application from optimal operation and perform // The following section is re-used in the Installation and Upgrade Guide - -// tag::notable-breaking-changes[] - [float] [[user-facing-changes-78]] ==== Breaking changes for users @@ -4982,10 +4958,6 @@ This fixes the Back button when navigating between dashboards using drilldowns. *via https://github.com/elastic/kibana/pull/62415[#62415]* ==== - -// end::notable-breaking-changes[] - - [float] [[general-plugin-API-changes-78]] ==== Breaking changes for plugin developers @@ -5804,11 +5776,6 @@ For information about the Kibana 7.7.0 release, review the following information Breaking changes can prevent your application from optimal operation and performance. Before you upgrade to 7.7.0, review the breaking changes, then mitigate the impact to your application. -// The following section is re-used in the Installation and Upgrade Guide -// tag::notable-breaking-changes[] - -// end::notable-breaking-changes[] - [float] ==== Breaking changes for users @@ -7242,11 +7209,6 @@ Breaking changes can prevent your application from optimal operation and perform * <> * <> -// The following section is re-used in the Installation and Upgrade Guide -//tag::notable-breaking-changes[] - -// end::notable-breaking-changes[] - [float] [[user-facing-changes]] ==== Breaking changes for users @@ -9633,15 +9595,11 @@ Breaking changes can prevent your application from optimal operation and perform //See also {kibana-ref-all}/7.5/release-highlights-7.5.0.html[release highlights] and <>. -//NOTE: The notable-breaking-changes tagged regions are re-used in the -//Installation and Upgrade Guide - //// The following section is re-used in the Installation and Upgrade Guide [[breaking_70_notable]] === Notable breaking changes //// -// tag::notable-breaking-changes[] [float] [[breaking_75_search_instead_of-msearch]] @@ -9669,7 +9627,6 @@ Any installs that previously enabled the Code app will now log a warning when Kibana starts up. It's safe to remove all configurations starting with `xpack.code.`. Starting in 8.0, these warnings will become errors that prevent Kibana from starting up. -// end::notable-breaking-changes[] [float] [[enhancement-7.5.0]] @@ -10037,15 +9994,11 @@ Breaking changes can prevent your application from optimal operation and perform //See also {kibana-ref-all}/7.4/release-highlights-7.4.0.html[release highlights] and <>. -//NOTE: The notable-breaking-changes tagged regions are re-used in the -//Installation and Upgrade Guide - //// The following section is re-used in the Installation and Upgrade Guide [[breaking_70_notable]] === Notable breaking changes //// -// tag::notable-breaking-changes[] [float] [[breaking_74_search_instead_of-msearch]] @@ -10061,9 +10014,6 @@ When the advanced setting `courier:batchSearches` is disabled, requests from *Discover*, *Visualize*, and *Dashboard* will now query {es} using the `_search` endpoint rather than the `_msearch` endpoint. - -// end::notable-breaking-changes[] - [float] [[enhancement-7.4.0]] === Enhancements @@ -10425,15 +10375,11 @@ Breaking changes can prevent your application from optimal operation and perform See also {kibana-ref-all}/7.3/release-highlights-7.3.0.html[release highlights] and <>. -//NOTE: The notable-breaking-changes tagged regions are re-used in the -//Installation and Upgrade Guide - //// The following section is re-used in the Installation and Upgrade Guide [[breaking_70_notable]] === Notable breaking changes //// -// tag::notable-breaking-changes[] [float] ==== Visibility of features after configuring a term join in Maps @@ -10454,8 +10400,6 @@ histograms might no longer work in 7.3. If you run into issues starting a advanced editor of the {transforms} wizard. The advanced editor will remove the unsupported attribute once the configuration gets applied. -// end::notable-breaking-changes[] - [float] [[breaking_73_dashboard_import_export]] ==== Dashboard import and export APIs @@ -10789,13 +10733,6 @@ Breaking changes can prevent your application from optimal operation and perform See also {kibana-ref-all}/7.2/release-highlights-7.2.0.html[release highlights] and <>. -//NOTE: The notable-breaking-changes tagged regions are re-used in the -//Installation and Upgrade Guide - -//tag::notable-breaking-changes[] - -// end::notable-breaking-changes[] - [float] [[breaking_72_index_pattern_changes]] @@ -10812,14 +10749,6 @@ time-based index patterns to a wildcard pattern to prepare for this change. on the root wildcard term. For example, a query on an index pattern such as `[logstash-]YYYY.MM.DD` will now query all indices that match `logstash-*`. - -//NOTE: The notable-breaking-changes tagged regions are re-used in the -//Installation and Upgrade Guide - -//tag::notable-breaking-changes[] - -// end::notable-breaking-changes[] - [float] [[enhancement-7.2.0]] === Enhancements @@ -11291,13 +11220,10 @@ Breaking changes can prevent your application from optimal operation and perform * <> //// -The following section is re-used in the Installation and Upgrade Guide [[breaking_70_notable]] === Notable breaking changes //// -// tag::notable-breaking-changes[] -// end::notable-breaking-changes[] [float] [[breaking_70_api_changes]]