## Summary
Breaking change proposal: https://github.com/elastic/dev/issues/2556
This PR updates the upgrade note documentation to explain the 9.0.0
changes around Reporting access control
## Summary
It adds upgrade notes and create docs link for Endpoint management
deprecated apis in 9.0.
This pr is for main (9.0) and 8.x (8.18) and will follow up with this
one on 8.x branch: https://github.com/elastic/kibana/pull/206904 in
order to add these notes to the Upgrade Assistant for these deprecated
api's
The Api routes were already removed in this pr (only in main):
https://github.com/elastic/kibana/pull/199598
---------
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
## Summary
This deprecation was added to the 8.x branch in
https://github.com/elastic/kibana/pull/202775 but I think we also need a
record of this breaking chain on `main`
---------
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
## Summary
This PR aims at relocating some of the Kibana modules (plugins and
packages) into a new folder structure, according to the _Sustainable
Kibana Architecture_ initiative. We kindly ask you to:
* Review the moved files, as some of them contain relative paths that
have been updated.
* Review the updated files, as some of them contain references that have
been updated.
* Think of potential impact of the move, including tooling and
configuration files that can be pointing to the relocated modules. E.g.:
* customised eslint rules
* docs pointing to source code
* We kindly ask you to:
* Search for the `packages[\/\\]` and `plugins[\/\\]` patterns in the
source code (Babel and Eslint config files), and update them
appropriately.
* Manually review .buildkite/scripts/pipelines/pull_request/pipeline.ts
to ensure that any CI pipeline customizations continue to be correctly
applied after the changed path names
* Review all of the updated files, specially the `.ts` and `.js` files
listed in the sections below.
#### 1 package(s) are going to be relocated:
| Id | Target folder |
| -- | ------------- |
| `@kbn/doc-links` | `src/platform/packages/shared/kbn-doc-links` |
<details>
<summary>Updated references</summary>
```
./docs/upgrade-notes.asciidoc
./package.json
./packages/kbn-repo-packages/package-map.json
./packages/kbn-ts-projects/config-paths.json
./src/core/tsconfig.type_check.json
./src/platform/packages/shared/kbn-doc-links/jest.config.js
./src/plugins/ai_assistant_management/selection/tsconfig.type_check.json
./tsconfig.base.json
./tsconfig.base.type_check.json
./tsconfig.refs.json
./x-pack/plugins/alerting/tsconfig.type_check.json
./x-pack/plugins/search_connectors/tsconfig.type_check.json
./x-pack/plugins/search_inference_endpoints/tsconfig.type_check.json
./x-pack/plugins/search_playground/tsconfig.type_check.json
./x-pack/plugins/security_solution/tsconfig.type_check.json
./x-pack/plugins/serverless_search/tsconfig.type_check.json
./x-pack/plugins/threat_intelligence/tsconfig.type_check.json
./yarn.lock
```
</details>
<details>
<summary>Updated relative paths</summary>
```
src/platform/packages/shared/kbn-doc-links/jest.config.js:12
src/platform/packages/shared/kbn-doc-links/tsconfig.json:2
src/platform/packages/shared/kbn-doc-links/tsconfig.type_check.json:2
```
</details>
<details>
<summary>Script errors</summary>
```
```
</details>
This PR resets the release notes, upgrade notes, and what's new for 9.0.
It also cleans up a few references/files that were focusing on migration
to 8.0
Some more PRs will happen to prepare the rest of the docs for v9
Closes: https://github.com/elastic/platform-docs-team/issues/564
fix https://github.com/elastic/kibana/issues/197721.
The route deprecation field changed from a boolean to an object, where
the object contains information that is used in deprecation issues that
the Upgrade Assistant shows.
This PR makes the necessary changes in the deprecated Saved Objects HTTP
APIs.
This PR also includes a release notes entry for the API deprecations
that was missing.
### Checklist
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [x]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
### How to test this:
- Pull PR, run es against a trial license and start kibana as usual.
- Make a curl request to Kibana to get the config saved object:
```
curl --location 'localhost:5601/abc/api/saved_objects/config/9.0.0' \
--header 'Content-Type: application/json' \
--header 'Accept-Encoding: gzip, deflate, br' \
--header 'kbn-xsrf: kibana' \
--header 'Kbn-Version: 9.0.0' \
--header 'Authorization: Basic ZWxhc3RpYzpjaGFuZ2VtZQ=='
```
- Navigate to Upgrade Assistant and observe Kibana has at least 1
deprecation warning.
- View Kibana's warnings, you should see a warning entry for `The "GET
/api/saved_objects/{type}/{id}" route is deprecated`
- click on the deprecation and you should see more detail about the
deprecated API that's been used in the flyout:
- resolve the deprecation warning
- Kibana should continue to issue requests to the deprecated SO HTTP
APIs because these APIs have not been removed yet.
### Risk Matrix
| Risk | Probability | Severity | Mitigation/Notes |
|---------------------------|-------------|----------|-------------------------|
| End user concern from the deprecation warning that says the routes
have been deprecated | Low | Low | The APIs have been deprecated since
8.7 and recommends using public APIs instead. |
### For maintainers
- [x] This will appear in the **Release Notes** and follow the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
---------
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
This PR adds release notes for Kibana 8.16.0
It also adds new deprecations to the Upgrade notes file.
There are many entries so here's a list of the sections that have been
edited and are ready for review so far:
- [x] AGPL license
- [x] Alerting @lcawl
- [x] Dashboards and visualizations
- [x] Data ingestion and Fleet @kilfoyle
- [x] Discover
- [x] Elastic Observability solution @bmorelli25
- [x] Elastic Search solution @leemthompo
- [x] Elastic Security solution
- [x] Kibana platform
- [x] Kibana security
- [x] Machine Learning @szabosteve @leemthompo
- [x] Management
Closes: https://github.com/elastic/platform-docs-team/issues/502
---------
Co-authored-by: István Zoltán Szabó <istvan.szabo@elastic.co>
Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
Co-authored-by: Giorgos Bamparopoulos <gbamparop@gmail.com>
Co-authored-by: Brandon Morelli <bmorelli25@gmail.com>
Co-authored-by: lcawl <lcawley@elastic.co>
## Summary
This PR fixes the following broken links that occur when we change
"current" to 8.16 in https://github.com/elastic/docs/pull/3104:
```
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/8.10/release-notes-8.7.0.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/8.11/release-notes-8.7.0.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/8.12/release-notes-8.7.0.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/8.13/release-notes-8.7.0.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/8.14/release-notes-8.7.0.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/8.15/release-notes-8.7.0.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/8.16/breaking-changes-summary.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/8.16/release-notes-8.7.0.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/8.7/release-notes-8.7.0.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/8.8/release-notes-8.7.0.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/8.9/release-notes-8.7.0.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/8.x/breaking-changes-summary.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/8.x/release-notes-8.7.0.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/current/breaking-changes-summary.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/current/release-notes-8.7.0.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/master/breaking-changes-summary.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
INFO:build_docs: /tmp/docsbuild/target_repo/html/en/kibana/master/release-notes-8.7.0.html contains broken links to:
INFO:build_docs: - en/kibana/current/add-aggregation-based-visualization-panels.html
```
NOTE: The backport PRs for 8.8 and 8.7 will need to be edited to use
version-specific URLs since the content in those branches are re-used in
https://www.elastic.co/guide/en/elastic-stack/8.7/kibana-breaking-changes.html,
for example.
## Summary
As part of the Search Session deprecation, we need this listed in the
8.15.x release notes.
---------
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
Co-authored-by: Florent Le Borgne <florent.leborgne@elastic.co>
## Summary
This PR:
- adds a page that is a compiled list of all breaking changes and
deprecations introduced since the last major version. I slightly edited
some bits to align the wording and add version information to each item,
and took a bit of freedom (not too much!) to ignore items that shouldn't
be identified as deprecations or breaking changes, or to move them to
the appropriate section in this page.
- adds a link to the new page from the Upgrade Kibana page.
<img width="1483" alt="image"
src="https://github.com/user-attachments/assets/16109072-d5c6-4eb4-8a52-ef209a07072a">
<img width="810" alt="image"
src="https://github.com/user-attachments/assets/939e9212-b750-4a6f-bd8f-f8df04e46d76">
I'm wondering if we should leave this uncategorized or at least identify
which items are specific to a solution. It also doesn't make much sense
that we have Obs here while we don't have Security. Let's think about a
consistent way to do it.
Note: In this PR, the page is initially added under the Release notes
section. I'll need to make sure that this does not interfere with the
release notes automation.
Note 2: If we move forward with this proposal, we'll need update the
release notes internal docs to add the relevant information to this page
with each minor release, or find a way to automate.
Closes: https://github.com/elastic/kibana-team/issues/1075
---------
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
Co-authored-by: Luke Elmers <lukeelmers@gmail.com>
