[DOCS] Adds user section to breaking changes doc (#58073)
* [DOCS] Adds user section to breaking changes doc * [DOCS] Fixes heading level
This commit is contained in:
parent
9a10433525
commit
4d686e5f4f
|
@ -7,13 +7,18 @@
|
|||
This page discusses the breaking changes that you need to be aware of when migrating
|
||||
your application to Kibana 7.6.
|
||||
|
||||
* <<general-plugin-API-changes, General plugin API changes>>
|
||||
* <<move-to-new-platform-changes, Plugin API migrations to New Platform>>
|
||||
* <<user-facing-changes, Breaking changes for users>>
|
||||
* <<general-plugin-API-changes, Breaking changes for plugin developers>>
|
||||
|
||||
[float]
|
||||
[[user-facing-changes]]
|
||||
=== Breaking changes for users
|
||||
|
||||
There are no user-facing breaking changes in 7.6.
|
||||
|
||||
[float]
|
||||
[[general-plugin-API-changes]]
|
||||
=== General plugin API changes
|
||||
=== Breaking changes for plugin developers
|
||||
|
||||
[float]
|
||||
==== {kib} no longer crashes when a plugin version does not match the server
|
||||
|
@ -569,10 +574,6 @@ Make the `Request` instance available to all HTTP interceptors, which is now in
|
|||
You may now also under-specify the object returned from HTTP response interceptors
|
||||
to only overwrite specific properties.
|
||||
|
||||
[float]
|
||||
[[move-to-new-platform-changes]]
|
||||
=== Plugin API migrations to New Platform
|
||||
|
||||
[float]
|
||||
==== Expose whitelisted config values to client-side plugin
|
||||
{pull}50641[#50641]
|
||||
|
|
Loading…
Reference in a new issue