mirror of
https://github.com/elastic/kibana.git
synced 2025-06-27 18:51:07 -04:00
84935 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
123c9989c7
|
[9.0] [Unzyme] src/core/packages/i18n (#223159) (#223439)
# Backport This will backport the following commits from `main` to `9.0`: - [[Unzyme] `src/core/packages/i18n` (#223159)](https://github.com/elastic/kibana/pull/223159) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2025-06-11T10:19:29Z","message":"[Unzyme] `src/core/packages/i18n` (#223159)","sha":"70a2da8304022a9246add36552a17ac3295f0069","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","technical debt","release_note:skip","backport:version","v9.1.0","v8.19.0","v9.0.3"],"title":"[Unzyme] `src/core/packages/i18n`","number":223159,"url":"https://github.com/elastic/kibana/pull/223159","mergeCommit":{"message":"[Unzyme] `src/core/packages/i18n` (#223159)","sha":"70a2da8304022a9246add36552a17ac3295f0069"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223159","number":223159,"mergeCommit":{"message":"[Unzyme] `src/core/packages/i18n` (#223159)","sha":"70a2da8304022a9246add36552a17ac3295f0069"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/223387","number":223387,"state":"MERGED","mergeCommit":{"sha":"2a17cc9b99dd0c73572ae962175983f4e8c3f316","message":"[8.19] [Unzyme] `src/core/packages/i18n` (#223159) (#223387)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [[Unzyme] `src/core/packages/i18n`\n(#223159)](https://github.com/elastic/kibana/pull/223159)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>"}},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co> |
||
|
Kibana Machine
|
1dff88f868
|
[9.0] Update lz-string dependencies to ^1.5.0 (main) (#219591) (#223438)
# Backport This will backport the following commits from `main` to `9.0`: - [Update lz-string dependencies to ^1.5.0 (main) (#219591)](https://github.com/elastic/kibana/pull/219591) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-11T16:17:26Z","message":"Update lz-string dependencies to ^1.5.0 (main) (#219591)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| @​types/lz-string | devDependencies | minor | [`^1.3.34` ->\n`^1.5.0`](https://renovatebot.com/diffs/npm/@types%2flz-string/1.3.34/1.5.0)\n|\n| [lz-string](http://pieroxy.net/blog/pages/lz-string/index.html)\n([source](https://redirect.github.com/pieroxy/lz-string)) | dependencies\n| patch | [`^1.4.4` ->\n`^1.5.0`](https://renovatebot.com/diffs/npm/lz-string/1.5.0/1.5.0) |\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about these\nupdates again.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>\nCo-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>","sha":"e407e9fee34a9459c7062807405bf816b6e8c107","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:SharedUX","backport:all-open","v9.1.0"],"title":"Update lz-string dependencies to ^1.5.0 (main)","number":219591,"url":"https://github.com/elastic/kibana/pull/219591","mergeCommit":{"message":"Update lz-string dependencies to ^1.5.0 (main) (#219591)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| @​types/lz-string | devDependencies | minor | [`^1.3.34` ->\n`^1.5.0`](https://renovatebot.com/diffs/npm/@types%2flz-string/1.3.34/1.5.0)\n|\n| [lz-string](http://pieroxy.net/blog/pages/lz-string/index.html)\n([source](https://redirect.github.com/pieroxy/lz-string)) | dependencies\n| patch | [`^1.4.4` ->\n`^1.5.0`](https://renovatebot.com/diffs/npm/lz-string/1.5.0/1.5.0) |\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about these\nupdates again.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>\nCo-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>","sha":"e407e9fee34a9459c7062807405bf816b6e8c107"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/219591","number":219591,"mergeCommit":{"message":"Update lz-string dependencies to ^1.5.0 (main) (#219591)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| @​types/lz-string | devDependencies | minor | [`^1.3.34` ->\n`^1.5.0`](https://renovatebot.com/diffs/npm/@types%2flz-string/1.3.34/1.5.0)\n|\n| [lz-string](http://pieroxy.net/blog/pages/lz-string/index.html)\n([source](https://redirect.github.com/pieroxy/lz-string)) | dependencies\n| patch | [`^1.4.4` ->\n`^1.5.0`](https://renovatebot.com/diffs/npm/lz-string/1.5.0/1.5.0) |\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about these\nupdates again.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>\nCo-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>","sha":"e407e9fee34a9459c7062807405bf816b6e8c107"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co> Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com> |
||
Viduni Wickramarachchi
|
70c508143c
|
[9.0] [Obs AI Assistant] Add Elastic Managed LLM tour callout (#220782) (#223283)
# Backport This will backport the following commits from `main` to `9.0`: - [[Obs AI Assistant] Add Elastic Managed LLM tour callout (#220782)](https://github.com/elastic/kibana/pull/220782) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Viduni Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2025-06-10T16:44:53Z","message":"[Obs AI Assistant] Add Elastic Managed LLM tour callout (#220782)\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/253\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/252\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/250\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/251\n\n## Summary\n\n1. Added Elastic Managed LLM connector via a tour callout when the\nconnector is present. This will be included in the AI Assistant flyout,\nAI Assistant page and contextual insights.\n2. Added a callout in the conversation when the Elastic Managed LLM is\nbeing used\n3. Added `Manage Connectors` to contextual insights action menu\n4. Added `AI Connector` updates to settings.\n\n## How to enable the Elastic LLM Connector for testing\n\n1. Run command - `VAULT_ADDR={...} vault login -method oidc`\n2. Run command - `node scripts/eis.js` (This will output the config for\nthe connector which needs to be pasted to `kibana.dev.yml`)\n3. Run Elasticsearch - `yarn es snapshot --license trial -E\nxpack.inference.elastic.url=http://localhost:8443/`\n4. Start Kibana as usual\n5. Run `yarn run ts-node --transpile-only\nx-pack/solutions/observability/packages/kbn-genai-cli/recipes/hello_world.ts`\nto test whether it works correctly.\n6. The connector should be visible in the connectors list in Kibana and\nin the AI Assistant\n\n## Screenshots\n\n### Flyout\n\n<img width=\"544\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e9f454e1-dcfe-4cf5-9929-77282764a8ce\"\n/>\n\n### Page\n\n<img width=\"1684\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/aac7c329-9918-4626-9fe9-5682902000fe\"\n/>\n\n### Contextual insights in APM\n\n<img width=\"1098\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/9eca3d33-b7ea-4128-a7de-d1b4776d8a8e\"\n/>\n\n### Callout within the conversation\n\n<img width=\"674\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/5c0b3933-b253-474e-92a5-d8793ebff819\"\n/>\n\n<img width=\"904\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2ca1ffef-0fcb-4d4f-addf-20c4927b7db0\"\n/>\n\n### Updates to AI connector title, description and buttons in Settings\n\n<img width=\"959\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/838d651d-319b-4637-a522-dc80d01bb11e\"\n/>\n\n### `Manage Connectors` link to contextual insights\n\n\n\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cf4d23a6d42208a131c91d1481377c5950cf0b05","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:feature","Team:Obs AI Assistant","ci:project-deploy-observability","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[Obs AI Assistant] Add Elastic Managed LLM tour callout","number":220782,"url":"https://github.com/elastic/kibana/pull/220782","mergeCommit":{"message":"[Obs AI Assistant] Add Elastic Managed LLM tour callout (#220782)\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/253\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/252\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/250\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/251\n\n## Summary\n\n1. Added Elastic Managed LLM connector via a tour callout when the\nconnector is present. This will be included in the AI Assistant flyout,\nAI Assistant page and contextual insights.\n2. Added a callout in the conversation when the Elastic Managed LLM is\nbeing used\n3. Added `Manage Connectors` to contextual insights action menu\n4. Added `AI Connector` updates to settings.\n\n## How to enable the Elastic LLM Connector for testing\n\n1. Run command - `VAULT_ADDR={...} vault login -method oidc`\n2. Run command - `node scripts/eis.js` (This will output the config for\nthe connector which needs to be pasted to `kibana.dev.yml`)\n3. Run Elasticsearch - `yarn es snapshot --license trial -E\nxpack.inference.elastic.url=http://localhost:8443/`\n4. Start Kibana as usual\n5. Run `yarn run ts-node --transpile-only\nx-pack/solutions/observability/packages/kbn-genai-cli/recipes/hello_world.ts`\nto test whether it works correctly.\n6. The connector should be visible in the connectors list in Kibana and\nin the AI Assistant\n\n## Screenshots\n\n### Flyout\n\n<img width=\"544\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e9f454e1-dcfe-4cf5-9929-77282764a8ce\"\n/>\n\n### Page\n\n<img width=\"1684\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/aac7c329-9918-4626-9fe9-5682902000fe\"\n/>\n\n### Contextual insights in APM\n\n<img width=\"1098\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/9eca3d33-b7ea-4128-a7de-d1b4776d8a8e\"\n/>\n\n### Callout within the conversation\n\n<img width=\"674\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/5c0b3933-b253-474e-92a5-d8793ebff819\"\n/>\n\n<img width=\"904\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2ca1ffef-0fcb-4d4f-addf-20c4927b7db0\"\n/>\n\n### Updates to AI connector title, description and buttons in Settings\n\n<img width=\"959\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/838d651d-319b-4637-a522-dc80d01bb11e\"\n/>\n\n### `Manage Connectors` link to contextual insights\n\n\n\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cf4d23a6d42208a131c91d1481377c5950cf0b05"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/220782","number":220782,"mergeCommit":{"message":"[Obs AI Assistant] Add Elastic Managed LLM tour callout (#220782)\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/253\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/252\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/250\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/251\n\n## Summary\n\n1. Added Elastic Managed LLM connector via a tour callout when the\nconnector is present. This will be included in the AI Assistant flyout,\nAI Assistant page and contextual insights.\n2. Added a callout in the conversation when the Elastic Managed LLM is\nbeing used\n3. Added `Manage Connectors` to contextual insights action menu\n4. Added `AI Connector` updates to settings.\n\n## How to enable the Elastic LLM Connector for testing\n\n1. Run command - `VAULT_ADDR={...} vault login -method oidc`\n2. Run command - `node scripts/eis.js` (This will output the config for\nthe connector which needs to be pasted to `kibana.dev.yml`)\n3. Run Elasticsearch - `yarn es snapshot --license trial -E\nxpack.inference.elastic.url=http://localhost:8443/`\n4. Start Kibana as usual\n5. Run `yarn run ts-node --transpile-only\nx-pack/solutions/observability/packages/kbn-genai-cli/recipes/hello_world.ts`\nto test whether it works correctly.\n6. The connector should be visible in the connectors list in Kibana and\nin the AI Assistant\n\n## Screenshots\n\n### Flyout\n\n<img width=\"544\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e9f454e1-dcfe-4cf5-9929-77282764a8ce\"\n/>\n\n### Page\n\n<img width=\"1684\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/aac7c329-9918-4626-9fe9-5682902000fe\"\n/>\n\n### Contextual insights in APM\n\n<img width=\"1098\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/9eca3d33-b7ea-4128-a7de-d1b4776d8a8e\"\n/>\n\n### Callout within the conversation\n\n<img width=\"674\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/5c0b3933-b253-474e-92a5-d8793ebff819\"\n/>\n\n<img width=\"904\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2ca1ffef-0fcb-4d4f-addf-20c4927b7db0\"\n/>\n\n### Updates to AI connector title, description and buttons in Settings\n\n<img width=\"959\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/838d651d-319b-4637-a522-dc80d01bb11e\"\n/>\n\n### `Manage Connectors` link to contextual insights\n\n\n\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cf4d23a6d42208a131c91d1481377c5950cf0b05"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
964a3cba85
|
[9.0] Update dependency msw to ~2.9.0 (main) (#223181) (#223427)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency msw to ~2.9.0 (main) (#223181)](https://github.com/elastic/kibana/pull/223181) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-11T15:20:55Z","message":"Update dependency msw to ~2.9.0 (main) (#223181)","sha":"50b3dc3cc4b9229ff3e7c5fdb15fef6c647b48b8","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Cloud Security","backport:all-open","v9.1.0"],"title":"Update dependency msw to ~2.9.0 (main)","number":223181,"url":"https://github.com/elastic/kibana/pull/223181","mergeCommit":{"message":"Update dependency msw to ~2.9.0 (main) (#223181)","sha":"50b3dc3cc4b9229ff3e7c5fdb15fef6c647b48b8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223181","number":223181,"mergeCommit":{"message":"Update dependency msw to ~2.9.0 (main) (#223181)","sha":"50b3dc3cc4b9229ff3e7c5fdb15fef6c647b48b8"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
242204dbe0
|
[9.0] [Synthetics] Avoid re-render when Run test finishes (#222503) (#223384)
# Backport This will backport the following commits from `main` to `9.0`: - [[Synthetics] Avoid re-render when Run test finishes (#222503)](https://github.com/elastic/kibana/pull/222503) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Francesco Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-06-11T09:58:29Z","message":"[Synthetics] Avoid re-render when Run test finishes (#222503)\n\nThis PR closes #217482 \n\nAfter manually running a test a re-render was causing loss of unsaved\nchanges.\n\nBefore:\n\n\n |
||
Dzmitry Lemechko
|
8484341e78
|
[9.0] [chore] update appex-qa dependencies (#222734) (#223073)
# Backport This will backport the following commits from `main` to `9.0`: - [[chore] update appex-qa dependencies (#222734)](https://github.com/elastic/kibana/pull/222734) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-06-06T17:23:08Z","message":"[chore] update appex-qa dependencies (#222734)\n\n## Summary\n\nUpdating the following dependenices:\n\n- supertest + superagent\n- lighthouse\n- Adding `qs` dependency only because it is now required by `superagent`\nas a sub-dependency\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"8e95c0dfea754da3db0350c1064aee921688fca4","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","v9.1.0","v8.19.0","v9.0.1"],"title":"[chore] update appex-qa dependencies","number":222734,"url":"https://github.com/elastic/kibana/pull/222734","mergeCommit":{"message":"[chore] update appex-qa dependencies (#222734)\n\n## Summary\n\nUpdating the following dependenices:\n\n- supertest + superagent\n- lighthouse\n- Adding `qs` dependency only because it is now required by `superagent`\nas a sub-dependency\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"8e95c0dfea754da3db0350c1064aee921688fca4"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222734","number":222734,"mergeCommit":{"message":"[chore] update appex-qa dependencies (#222734)\n\n## Summary\n\nUpdating the following dependenices:\n\n- supertest + superagent\n- lighthouse\n- Adding `qs` dependency only because it is now required by `superagent`\nas a sub-dependency\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"8e95c0dfea754da3db0350c1064aee921688fca4"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
cc26905fb1
|
[9.0] [Lens] Limit user messages to the lens container (#202717) (#223354)
# Backport This will backport the following commits from `main` to `9.0`: - [[Lens] Limit user messages to the lens container (#202717)](https://github.com/elastic/kibana/pull/202717) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Vettorello","email":"marco.vettorello@elastic.co"},"sourceCommit":{"committedDate":"2025-06-11T07:08:36Z","message":"[Lens] Limit user messages to the lens container (#202717)\n\n## Summary\n\nThis PR fixes the wrong position of the Lens user messages caused by the\nabsolute positioning of their container within a `static` positioned\nparent.\n\n>An element with `position: absolute` is positioned relative to its\nnearest positioned ancestor. A \"positioned\" ancestor has a position\nvalue other than static (the default).\nIf no such ancestor exists, the element will be positioned relative to\nthe initial containing block, which is usually the <html> element.\n\nThe `LensEmbeddableComponent` root div was with a `position:static` by\ndefault, causing the absolute positioned badge/user message icon to be\npositioned in the nearest positioned ancestor.\n\nFix https://github.com/elastic/kibana/issues/189344\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6eec63d5f186d827ef7d6952ee5c78c7ea78c6ae","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:Visualizations","release_note:skip","Feature:Lens","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Lens] Limit user messages to the lens container","number":202717,"url":"https://github.com/elastic/kibana/pull/202717","mergeCommit":{"message":"[Lens] Limit user messages to the lens container (#202717)\n\n## Summary\n\nThis PR fixes the wrong position of the Lens user messages caused by the\nabsolute positioning of their container within a `static` positioned\nparent.\n\n>An element with `position: absolute` is positioned relative to its\nnearest positioned ancestor. A \"positioned\" ancestor has a position\nvalue other than static (the default).\nIf no such ancestor exists, the element will be positioned relative to\nthe initial containing block, which is usually the <html> element.\n\nThe `LensEmbeddableComponent` root div was with a `position:static` by\ndefault, causing the absolute positioned badge/user message icon to be\npositioned in the nearest positioned ancestor.\n\nFix https://github.com/elastic/kibana/issues/189344\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6eec63d5f186d827ef7d6952ee5c78c7ea78c6ae"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202717","number":202717,"mergeCommit":{"message":"[Lens] Limit user messages to the lens container (#202717)\n\n## Summary\n\nThis PR fixes the wrong position of the Lens user messages caused by the\nabsolute positioning of their container within a `static` positioned\nparent.\n\n>An element with `position: absolute` is positioned relative to its\nnearest positioned ancestor. A \"positioned\" ancestor has a position\nvalue other than static (the default).\nIf no such ancestor exists, the element will be positioned relative to\nthe initial containing block, which is usually the <html> element.\n\nThe `LensEmbeddableComponent` root div was with a `position:static` by\ndefault, causing the absolute positioned badge/user message icon to be\npositioned in the nearest positioned ancestor.\n\nFix https://github.com/elastic/kibana/issues/189344\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6eec63d5f186d827ef7d6952ee5c78c7ea78c6ae"}}]}] BACKPORT--> Co-authored-by: Marco Vettorello <marco.vettorello@elastic.co> |
||
Stratoula Kalafateli
|
5de5dc9958
|
[9.0] [Lens] Do not break when the table has no data (#217937) (#223349)
# Backport This will backport the following commits from `main` to `9.0`: - [[Lens] Do not break when the table has no data (#217937)](https://github.com/elastic/kibana/pull/217937) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T12:03:09Z","message":"[Lens] Do not break when the table has no data (#217937)\n\n## Summary\n\nWhen the datatable comes with empty results the visualization fails with\nbad way\n\n<img width=\"396\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/b4e266d7-edbd-452b-9192-84c957fe98db\"\n/>\n\n\nWith the fix\n<img width=\"756\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d061d29e-9246-432a-944b-308b88d161e7\"\n/>\n\n\n\nHow to replicate:\n\n- Create a field ES|QL control with 2 values (extension and geo.dest).\nYou can do it with multiple ways. I created with typing `FROM\nkibana_sample_data_logs | STATS count = COUNT(*) BY` and then `Create\ncontrol`.\n- Use the variable in another panel with query: `FROM\nkibana_sample_data_logs | WHERE ??field == \"css\" | KEEP extension` (The\ncontrol value should be in the extension). This will work\n- Select the second field (geo.dest). This will return an empty query\nand will break the table viz.\n\n### Checklist\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"fa2d3912f408326980241df394c51bd87074e21c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Lens","Feature:ES|QL","backport:version","v9.1.0","v8.19.0"],"title":"[Lens] Do not break when the table has no data","number":217937,"url":"https://github.com/elastic/kibana/pull/217937","mergeCommit":{"message":"[Lens] Do not break when the table has no data (#217937)\n\n## Summary\n\nWhen the datatable comes with empty results the visualization fails with\nbad way\n\n<img width=\"396\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/b4e266d7-edbd-452b-9192-84c957fe98db\"\n/>\n\n\nWith the fix\n<img width=\"756\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d061d29e-9246-432a-944b-308b88d161e7\"\n/>\n\n\n\nHow to replicate:\n\n- Create a field ES|QL control with 2 values (extension and geo.dest).\nYou can do it with multiple ways. I created with typing `FROM\nkibana_sample_data_logs | STATS count = COUNT(*) BY` and then `Create\ncontrol`.\n- Use the variable in another panel with query: `FROM\nkibana_sample_data_logs | WHERE ??field == \"css\" | KEEP extension` (The\ncontrol value should be in the extension). This will work\n- Select the second field (geo.dest). This will return an empty query\nand will break the table viz.\n\n### Checklist\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"fa2d3912f408326980241df394c51bd87074e21c"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217937","number":217937,"mergeCommit":{"message":"[Lens] Do not break when the table has no data (#217937)\n\n## Summary\n\nWhen the datatable comes with empty results the visualization fails with\nbad way\n\n<img width=\"396\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/b4e266d7-edbd-452b-9192-84c957fe98db\"\n/>\n\n\nWith the fix\n<img width=\"756\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d061d29e-9246-432a-944b-308b88d161e7\"\n/>\n\n\n\nHow to replicate:\n\n- Create a field ES|QL control with 2 values (extension and geo.dest).\nYou can do it with multiple ways. I created with typing `FROM\nkibana_sample_data_logs | STATS count = COUNT(*) BY` and then `Create\ncontrol`.\n- Use the variable in another panel with query: `FROM\nkibana_sample_data_logs | WHERE ??field == \"css\" | KEEP extension` (The\ncontrol value should be in the extension). This will work\n- Select the second field (geo.dest). This will return an empty query\nand will break the table viz.\n\n### Checklist\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"fa2d3912f408326980241df394c51bd87074e21c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218254","number":218254,"state":"MERGED","mergeCommit":{"sha":"d35ae396a663a340f859f5fb29ef98fff52fb8ca","message":"[8.x] [Lens] Do not break when the table has no data (#217937) (#218254)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Lens] Do not break when the table has no data\n(#217937)](https://github.com/elastic/kibana/pull/217937)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>"}}]}] BACKPORT--> |
||
Davis McPhee
|
1d69508df2
|
[9.0] Revert "[ES|QL] Fix CSV report time range when exporting from Discover (#216792)" (#223249) (#223344)
# Backport This will backport the following commits from `main` to `9.0`: - [Revert "[ES|QL] Fix CSV report time range when exporting from Discover (#216792)" (#223249)](https://github.com/elastic/kibana/pull/223249) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-06-11T02:57:09Z","message":"Revert \"[ES|QL] Fix CSV report time range when exporting from Discover (#216792)\" (#223249)\n\n## Summary\n\nThis reverts commit 6a0c173b1ad6152ee75bc2e74dfd71e74fa6b54a.\n\nFixes #223171.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"9b18d391b119477624e6fcaec5059e0c641f341b","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:DataDiscovery","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"Revert \"[ES|QL] Fix CSV report time range when exporting from Discover (#216792)\"","number":223249,"url":"https://github.com/elastic/kibana/pull/223249","mergeCommit":{"message":"Revert \"[ES|QL] Fix CSV report time range when exporting from Discover (#216792)\" (#223249)\n\n## Summary\n\nThis reverts commit 6a0c173b1ad6152ee75bc2e74dfd71e74fa6b54a.\n\nFixes #223171.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"9b18d391b119477624e6fcaec5059e0c641f341b"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223249","number":223249,"mergeCommit":{"message":"Revert \"[ES|QL] Fix CSV report time range when exporting from Discover (#216792)\" (#223249)\n\n## Summary\n\nThis reverts commit 6a0c173b1ad6152ee75bc2e74dfd71e74fa6b54a.\n\nFixes #223171.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"9b18d391b119477624e6fcaec5059e0c641f341b"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/223343","number":223343,"state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
2e8b54878b
|
[9.0] Update dependency @types/moment-duration-format to ^2.2.6 (main) (#202973) (#223339)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency @types/moment-duration-format to ^2.2.6 (main) (#202973)](https://github.com/elastic/kibana/pull/202973) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-11T01:25:06Z","message":"Update dependency @types/moment-duration-format to ^2.2.6 (main) (#202973)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n|\n[@types/moment-duration-format](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/moment-duration-format)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/moment-duration-format))\n| devDependencies | patch | [`^2.2.3` ->\n`^2.2.6`](https://renovatebot.com/diffs/npm/@types%2fmoment-duration-format/2.2.3/2.2.6)\n|\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [x] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"7b8c157fd91a9f9758ad50871e5cc6c0f39f4765","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Monitoring","Team:Kibana Management","release_note:skip","backport:all-open","v9.1.0"],"title":"Update dependency @types/moment-duration-format to ^2.2.6 (main)","number":202973,"url":"https://github.com/elastic/kibana/pull/202973","mergeCommit":{"message":"Update dependency @types/moment-duration-format to ^2.2.6 (main) (#202973)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n|\n[@types/moment-duration-format](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/moment-duration-format)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/moment-duration-format))\n| devDependencies | patch | [`^2.2.3` ->\n`^2.2.6`](https://renovatebot.com/diffs/npm/@types%2fmoment-duration-format/2.2.3/2.2.6)\n|\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [x] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"7b8c157fd91a9f9758ad50871e5cc6c0f39f4765"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202973","number":202973,"mergeCommit":{"message":"Update dependency @types/moment-duration-format to ^2.2.6 (main) (#202973)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n|\n[@types/moment-duration-format](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/moment-duration-format)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/moment-duration-format))\n| devDependencies | patch | [`^2.2.3` ->\n`^2.2.6`](https://renovatebot.com/diffs/npm/@types%2fmoment-duration-format/2.2.3/2.2.6)\n|\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [x] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"7b8c157fd91a9f9758ad50871e5cc6c0f39f4765"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Matthew Kime <matt@mattki.me> |
||
|
Kibana Machine
|
dd164022b7
|
[9.0] Update dependency blurhash to ^2.0.5 (main) (#219584) (#223332)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency blurhash to ^2.0.5 (main) (#219584)](https://github.com/elastic/kibana/pull/219584) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-10T23:39:46Z","message":"Update dependency blurhash to ^2.0.5 (main) (#219584)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [blurhash](https://blurha.sh/)\n([source](https://redirect.github.com/woltapp/blurhash/tree/HEAD/TypeScript))\n| dependencies | patch | [`^2.0.1` ->\n`^2.0.5`](https://renovatebot.com/diffs/npm/blurhash/2.0.1/2.0.5) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>woltapp/blurhash (blurhash)</summary>\n\n###\n[`v2.0.4`]( |
||
|
Kibana Machine
|
fc42880a39
|
[9.0] Update dependency @types/deep-freeze-strict to ^1.1.2 (main) (#219582) (#223325)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency @types/deep-freeze-strict to ^1.1.2 (main) (#219582)](https://github.com/elastic/kibana/pull/219582) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-10T23:20:00Z","message":"Update dependency @types/deep-freeze-strict to ^1.1.2 (main) (#219582)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n|\n[@types/deep-freeze-strict](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/deep-freeze-strict)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/deep-freeze-strict))\n| devDependencies | patch | [`^1.1.0` ->\n`^1.1.2`](https://renovatebot.com/diffs/npm/@types%2fdeep-freeze-strict/1.1.0/1.1.2)\n|\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"0711625608d76f193f72dbfe73849ae8949bfd18","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:SharedUX","backport:all-open","v9.1.0"],"title":"Update dependency @types/deep-freeze-strict to ^1.1.2 (main)","number":219582,"url":"https://github.com/elastic/kibana/pull/219582","mergeCommit":{"message":"Update dependency @types/deep-freeze-strict to ^1.1.2 (main) (#219582)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n|\n[@types/deep-freeze-strict](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/deep-freeze-strict)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/deep-freeze-strict))\n| devDependencies | patch | [`^1.1.0` ->\n`^1.1.2`](https://renovatebot.com/diffs/npm/@types%2fdeep-freeze-strict/1.1.0/1.1.2)\n|\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"0711625608d76f193f72dbfe73849ae8949bfd18"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/219582","number":219582,"mergeCommit":{"message":"Update dependency @types/deep-freeze-strict to ^1.1.2 (main) (#219582)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n|\n[@types/deep-freeze-strict](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/deep-freeze-strict)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/deep-freeze-strict))\n| devDependencies | patch | [`^1.1.0` ->\n`^1.1.2`](https://renovatebot.com/diffs/npm/@types%2fdeep-freeze-strict/1.1.0/1.1.2)\n|\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"0711625608d76f193f72dbfe73849ae8949bfd18"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
d5d94ac66f
|
[9.0] Update TTFMP documentation for meta fields. (#221807) (#223317)
# Backport This will backport the following commits from `main` to `9.0`: - [Update TTFMP documentation for meta fields. (#221807)](https://github.com/elastic/kibana/pull/221807) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Abdul Wahab Zahid","email":"awahab07@yahoo.com"},"sourceCommit":{"committedDate":"2025-06-10T22:14:05Z","message":"Update TTFMP documentation for meta fields. (#221807)\n\nEnhances the performance metrics documentation by explaining how\nto use the `meta.description` field for contextualizing render time\nevents and how to track subsequent page or section loads using\n`onPageRefreshStart`.\n\n\n- Added a section describing the default meaning of render time and how\nto provide a custom `description` in the `meta` field of `onPageReady`\nfor more precise event context.\n- Documented the use of `onPageRefreshStart` to distinguish between\ninitial loads and subsequent refreshes, clarifying that\n`meta.isInitialLoad` is set to `false` for refreshes and `true` by\ndefault.\n- Included code examples and sample indexed event structures for both\nfeatures.","sha":"ca05a06f00e013a18198cb46ce051d64f0d3f4b1","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","v8.18.0","v9.1.0","v8.19.0"],"title":"Update TTFMP documentation for meta fields.","number":221807,"url":"https://github.com/elastic/kibana/pull/221807","mergeCommit":{"message":"Update TTFMP documentation for meta fields. (#221807)\n\nEnhances the performance metrics documentation by explaining how\nto use the `meta.description` field for contextualizing render time\nevents and how to track subsequent page or section loads using\n`onPageRefreshStart`.\n\n\n- Added a section describing the default meaning of render time and how\nto provide a custom `description` in the `meta` field of `onPageReady`\nfor more precise event context.\n- Documented the use of `onPageRefreshStart` to distinguish between\ninitial loads and subsequent refreshes, clarifying that\n`meta.isInitialLoad` is set to `false` for refreshes and `true` by\ndefault.\n- Included code examples and sample indexed event structures for both\nfeatures.","sha":"ca05a06f00e013a18198cb46ce051d64f0d3f4b1"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.19"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/221807","number":221807,"mergeCommit":{"message":"Update TTFMP documentation for meta fields. (#221807)\n\nEnhances the performance metrics documentation by explaining how\nto use the `meta.description` field for contextualizing render time\nevents and how to track subsequent page or section loads using\n`onPageRefreshStart`.\n\n\n- Added a section describing the default meaning of render time and how\nto provide a custom `description` in the `meta` field of `onPageReady`\nfor more precise event context.\n- Documented the use of `onPageRefreshStart` to distinguish between\ninitial loads and subsequent refreshes, clarifying that\n`meta.isInitialLoad` is set to `false` for refreshes and `true` by\ndefault.\n- Included code examples and sample indexed event structures for both\nfeatures.","sha":"ca05a06f00e013a18198cb46ce051d64f0d3f4b1"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Abdul Wahab Zahid <awahab07@yahoo.com> |
||
|
Kibana Machine
|
f9577fbf33
|
[9.0] Update papaparse (main) (manual) (#220930) (#223268)
# Backport This will backport the following commits from `main` to `9.0`: - [Update papaparse (main) (manual) (#220930)](https://github.com/elastic/kibana/pull/220930) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marshall Main","email":"55718608+marshallmain@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-10T16:46:29Z","message":"Update papaparse (main) (manual) (#220930)\n\n## Summary\n\nManual version of https://github.com/elastic/kibana/pull/206182 due to\nbreaking type changes in papaparse\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"ea71069d09d1b802bf29e4d113ff75d022f30789","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","backport:version","v9.1.0","v8.19.0","v8.17.7","v8.18.2","v9.0.2"],"title":"Update papaparse (main) (manual)","number":220930,"url":"https://github.com/elastic/kibana/pull/220930","mergeCommit":{"message":"Update papaparse (main) (manual) (#220930)\n\n## Summary\n\nManual version of https://github.com/elastic/kibana/pull/206182 due to\nbreaking type changes in papaparse\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"ea71069d09d1b802bf29e4d113ff75d022f30789"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.17","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/220930","number":220930,"mergeCommit":{"message":"Update papaparse (main) (manual) (#220930)\n\n## Summary\n\nManual version of https://github.com/elastic/kibana/pull/206182 due to\nbreaking type changes in papaparse\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"ea71069d09d1b802bf29e4d113ff75d022f30789"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Marshall Main <55718608+marshallmain@users.noreply.github.com> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
30c79c64b0
|
[9.0] [APM] Prevent table updates during data loading only when 'Progressive Loading' is enabled (#223093) (#223231)
# Backport This will backport the following commits from `main` to `9.0`: - [[APM] Prevent table updates during data loading only when 'Progressive Loading' is enabled (#223093)](https://github.com/elastic/kibana/pull/223093) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Milosz Marcinkowski","email":"38698566+miloszmarcinkowski@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-10T12:51:08Z","message":"[APM] Prevent table updates during data loading only when 'Progressive Loading' is enabled (#223093)\n\n### Summary\n\nFollow up to [#220514](https://github.com/elastic/kibana/pull/220514).\nApply the `isLoading` check only when Progressive Loading is enabled.\nWithout this, users are prevented from applying sorting filters to the\ntable during data loading.\n\n<img width=\"1728\" alt=\"Screenshot 2025-06-09 at 11 55 19\"\nsrc=\"https://github.com/user-attachments/assets/bf4afd49-0025-46b3-8c44-0d021a665073\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"2becef46f0a74f6107bb34f0421cd28e1e9535f1","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM] Prevent table updates during data loading only when 'Progressive Loading' is enabled","number":223093,"url":"https://github.com/elastic/kibana/pull/223093","mergeCommit":{"message":"[APM] Prevent table updates during data loading only when 'Progressive Loading' is enabled (#223093)\n\n### Summary\n\nFollow up to [#220514](https://github.com/elastic/kibana/pull/220514).\nApply the `isLoading` check only when Progressive Loading is enabled.\nWithout this, users are prevented from applying sorting filters to the\ntable during data loading.\n\n<img width=\"1728\" alt=\"Screenshot 2025-06-09 at 11 55 19\"\nsrc=\"https://github.com/user-attachments/assets/bf4afd49-0025-46b3-8c44-0d021a665073\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"2becef46f0a74f6107bb34f0421cd28e1e9535f1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223093","number":223093,"mergeCommit":{"message":"[APM] Prevent table updates during data loading only when 'Progressive Loading' is enabled (#223093)\n\n### Summary\n\nFollow up to [#220514](https://github.com/elastic/kibana/pull/220514).\nApply the `isLoading` check only when Progressive Loading is enabled.\nWithout this, users are prevented from applying sorting filters to the\ntable during data loading.\n\n<img width=\"1728\" alt=\"Screenshot 2025-06-09 at 11 55 19\"\nsrc=\"https://github.com/user-attachments/assets/bf4afd49-0025-46b3-8c44-0d021a665073\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"2becef46f0a74f6107bb34f0421cd28e1e9535f1"}}]}] BACKPORT--> Co-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com> |
||
|
Kibana Machine
|
b27957565a
|
[9.0] [ILM][Index Management] Replace deprecated EuiFilterSelectItem (#223001) (#223220)
# Backport This will backport the following commits from `main` to `9.0`: - [[ILM][Index Management] Replace deprecated EuiFilterSelectItem (#223001)](https://github.com/elastic/kibana/pull/223001) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Damian Polewski","email":"125268832+damian-polewski@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-10T11:52:50Z","message":"[ILM][Index Management] Replace deprecated EuiFilterSelectItem (#223001)\n\nCloses #220512\n\nThis PR replaces deprecated `EuiFilterSelectItem` component with\n`EuiSelectable` in ILM and Index Management plugins.","sha":"245fb8e0f15317f29904de0bb4301a0b03253e35","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Index Management","Feature:ILM","Team:Kibana Management","release_note:skip","backport:version","v9.1.0","v8.19.0","v9.0.3"],"title":"[ILM][Index Management] Replace deprecated EuiFilterSelectItem","number":223001,"url":"https://github.com/elastic/kibana/pull/223001","mergeCommit":{"message":"[ILM][Index Management] Replace deprecated EuiFilterSelectItem (#223001)\n\nCloses #220512\n\nThis PR replaces deprecated `EuiFilterSelectItem` component with\n`EuiSelectable` in ILM and Index Management plugins.","sha":"245fb8e0f15317f29904de0bb4301a0b03253e35"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223001","number":223001,"mergeCommit":{"message":"[ILM][Index Management] Replace deprecated EuiFilterSelectItem (#223001)\n\nCloses #220512\n\nThis PR replaces deprecated `EuiFilterSelectItem` component with\n`EuiSelectable` in ILM and Index Management plugins.","sha":"245fb8e0f15317f29904de0bb4301a0b03253e35"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Damian Polewski <125268832+damian-polewski@users.noreply.github.com> |
||
Shahzad
|
4c30099330
|
[9.0] [Observability] Add alert details action button !! (#213195) (#223000)
# Backport This will backport the following commits from `main` to `9.0`: - [[Observability] Add alert details action button !! (#213195)](https://github.com/elastic/kibana/pull/213195) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-03-06T07:02:37Z","message":"[Observability] Add alert details action button !! (#213195)\n\n## Summary\n\nAdd alert details action button !!\n\nif you have opened up the flyout, reason action button gets hidden.\n\nAlso fixed dark theme issues for the chart !!\n\n<img width=\"1728\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e9ba3330-2378-418a-91b7-52b67fdc4c09\"\n/>","sha":"8f7f5ff73bb214c1cf4c87f470a3720d41752938","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v9.0.3"],"title":"[Observability] Add alert details action button !!","number":213195,"url":"https://github.com/elastic/kibana/pull/213195","mergeCommit":{"message":"[Observability] Add alert details action button !! (#213195)\n\n## Summary\n\nAdd alert details action button !!\n\nif you have opened up the flyout, reason action button gets hidden.\n\nAlso fixed dark theme issues for the chart !!\n\n<img width=\"1728\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e9ba3330-2378-418a-91b7-52b67fdc4c09\"\n/>","sha":"8f7f5ff73bb214c1cf4c87f470a3720d41752938"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213195","number":213195,"mergeCommit":{"message":"[Observability] Add alert details action button !! (#213195)\n\n## Summary\n\nAdd alert details action button !!\n\nif you have opened up the flyout, reason action button gets hidden.\n\nAlso fixed dark theme issues for the chart !!\n\n<img width=\"1728\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e9ba3330-2378-418a-91b7-52b67fdc4c09\"\n/>","sha":"8f7f5ff73bb214c1cf4c87f470a3720d41752938"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"url":"https://github.com/elastic/kibana/pull/221616","number":221616,"branch":"8.19","state":"MERGED","mergeCommit":{"sha":"755f6c64f827f84f1065a8096d7635908747afed","message":"[8.19] [Observability] Add alert details action button !! (#213195) (#221616)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [[Observability] Add alert details action button !!\n(#213195)](https://github.com/elastic/kibana/pull/213195)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>"}}]}] BACKPORT--> |
||
Andreana Malama
|
2d02151b33
|
[9.0] [Lens] Fix the button text for going back to the aggregation based visualization (#222823) (#223214)
# Backport This will backport the following commits from `main` to `9.0`: - [[Lens] Fix the button text for going back to the aggregation based visualization (#222823)](https://github.com/elastic/kibana/pull/222823) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Andreana Malama","email":"72010092+andrimal@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-10T10:47:12Z","message":"[Lens] Fix the button text for going back to the aggregation based visualization (#222823)\n\n## Summary\n\nFix #203977 \n\nWhen the user clicked 'Edit visualization in Lens' from an aggregation\nvisualization, the button to return to the aggregation based\nvisualization editor showed the wrong app to return to (Dashboard). This\nPR fixes the button text to return to the aggregation based\nvisualization.\n\nBefore: \n\n\nAfter: \n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"95f74bec29f56fe638962b1fcd36b17c95c415f1","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[Lens] Fix the button text for going back to the aggregation based visualization","number":222823,"url":"https://github.com/elastic/kibana/pull/222823","mergeCommit":{"message":"[Lens] Fix the button text for going back to the aggregation based visualization (#222823)\n\n## Summary\n\nFix #203977 \n\nWhen the user clicked 'Edit visualization in Lens' from an aggregation\nvisualization, the button to return to the aggregation based\nvisualization editor showed the wrong app to return to (Dashboard). This\nPR fixes the button text to return to the aggregation based\nvisualization.\n\nBefore: \n\n\nAfter: \n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"95f74bec29f56fe638962b1fcd36b17c95c415f1"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222823","number":222823,"mergeCommit":{"message":"[Lens] Fix the button text for going back to the aggregation based visualization (#222823)\n\n## Summary\n\nFix #203977 \n\nWhen the user clicked 'Edit visualization in Lens' from an aggregation\nvisualization, the button to return to the aggregation based\nvisualization editor showed the wrong app to return to (Dashboard). This\nPR fixes the button text to return to the aggregation based\nvisualization.\n\nBefore: \n\n\nAfter: \n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"95f74bec29f56fe638962b1fcd36b17c95c415f1"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
0af79efd1d
|
[9.0] [Security Solution] Enforce sending the request to API even if offline, for air-gapped environment. (#220510) (#223205)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Enforce sending the request to API even if offline, for air-gapped environment. (#220510)](https://github.com/elastic/kibana/pull/220510) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jacek Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2025-06-10T10:14:45Z","message":"[Security Solution] Enforce sending the request to API even if offline, for air-gapped environment. (#220510)\n\n**Resolves: #181808**\n\n## Summary\n\nI am fixing the issue of the Rules and Alerts tabs in Security, as well\nas the Fleet tab in Management, that gets stalled in air-gapped\nenvironment. I am doing so by enforcing the request to be sent to the\nAPI even when offline.\n\n### Historical context:\nDuring investigation of the original issue #181808 I proved that Kibana\ndoesn't try to reach to EPR in the air-gapped environment (that is, with\nthe `xpack.fleet.isAirGapped: true` flag, and WIFI being turned ON). I\ncommented this\n[here](https://github.com/elastic/kibana/issues/181808#issuecomment-2829911511)\nand we closed the issue. However, @111andre111 reached out to us saying\nthat this wasn't enough, as the real issue remains, that is, Kibana\ndoesn't behave properly when:\n- `xpack.fleet.isAirGapped` flag is set to `true`\n- there is no Internet connection (WIFI off or cable physically\ndisconnected)\n\nThat's why we reopened the ticket and I restarted the investigation. \nMy first observation was that when I turn off the WIFI, I cannot see\nrequests to the API being sent in the Network tab in Dev Tools, most\nimportantly to the `_bootstrap` endpoint at the first entrance to the\nSolution app, and other endpoints later. I searched that the browser\ndiscovers being offline and suppresses such calls. When WIFI is back ON,\nthen the browser sends these requests. That was exactly what I saw in\nthe Network tab.\nI searched and found an option to force browser to always send the\nrequest, regardless of what it thinks about connectivity. Such option,\n`networkMode: 'always'`, can be added to TanStackQuery client.\n\nI started working on adding this option to occurences of `useQuery` and\n`useMutation`, and immediately sounded success, as the behavior was\ncorrect. However, @xcrzx rigthfully pointed out, that it would be much\nbetter to only add it to one place, that is the configuration of the\nQueryClient. I did it, and to my surprise, the problem returned.\nI noticed that adding this option to the QueryClient in Fleet solved the\nproblem in the Fleet tab immediately, but adding this option to the\n`SecuritySolutionQueryClient` does nothing, like it was completely\nignored.\nI searched different options and spent two more days debugging the\nproblem, but then, when paired up again with Dmitrii, he found that the\n`SecuritySolutionQueryClient` is overshadowed by some other QueryClient\npresent in the stack of components much below, the `CasesContext`. That\ndiscovery enabled me to add this new setting to the other QueryClient,\nand this fixes the issue. However, we think that it will be worth\ninvestigating why we need this second context, as the situation when one\nQueryClient overshadows another one, smells badly and may be a source of\nother issues as well (I will reach out to the team responsible for the\nCasesContext and ask if we can unify this somehow).\n\n## BEFORE\n\n\nhttps://github.com/user-attachments/assets/662dab73-b1bd-4d6b-9d15-c35efab679c6\n\n## AFTER\n\n\nhttps://github.com/user-attachments/assets/b905bde0-150d-478d-9734-9003fb5bcf66\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7ad35a4a33c3bd4d4f4e33acff20f4ebaa3242ce","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Fleet","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","ci:build-all-platforms","ci:build-os-packages","Feature:Prebuilt Detection Rules","ci:build-cloud-image","backport:version","v9.1.0","v8.19.0"],"title":"[Security Solution] Enforce sending the request to API even if offline, for air-gapped environment.","number":220510,"url":"https://github.com/elastic/kibana/pull/220510","mergeCommit":{"message":"[Security Solution] Enforce sending the request to API even if offline, for air-gapped environment. (#220510)\n\n**Resolves: #181808**\n\n## Summary\n\nI am fixing the issue of the Rules and Alerts tabs in Security, as well\nas the Fleet tab in Management, that gets stalled in air-gapped\nenvironment. I am doing so by enforcing the request to be sent to the\nAPI even when offline.\n\n### Historical context:\nDuring investigation of the original issue #181808 I proved that Kibana\ndoesn't try to reach to EPR in the air-gapped environment (that is, with\nthe `xpack.fleet.isAirGapped: true` flag, and WIFI being turned ON). I\ncommented this\n[here](https://github.com/elastic/kibana/issues/181808#issuecomment-2829911511)\nand we closed the issue. However, @111andre111 reached out to us saying\nthat this wasn't enough, as the real issue remains, that is, Kibana\ndoesn't behave properly when:\n- `xpack.fleet.isAirGapped` flag is set to `true`\n- there is no Internet connection (WIFI off or cable physically\ndisconnected)\n\nThat's why we reopened the ticket and I restarted the investigation. \nMy first observation was that when I turn off the WIFI, I cannot see\nrequests to the API being sent in the Network tab in Dev Tools, most\nimportantly to the `_bootstrap` endpoint at the first entrance to the\nSolution app, and other endpoints later. I searched that the browser\ndiscovers being offline and suppresses such calls. When WIFI is back ON,\nthen the browser sends these requests. That was exactly what I saw in\nthe Network tab.\nI searched and found an option to force browser to always send the\nrequest, regardless of what it thinks about connectivity. Such option,\n`networkMode: 'always'`, can be added to TanStackQuery client.\n\nI started working on adding this option to occurences of `useQuery` and\n`useMutation`, and immediately sounded success, as the behavior was\ncorrect. However, @xcrzx rigthfully pointed out, that it would be much\nbetter to only add it to one place, that is the configuration of the\nQueryClient. I did it, and to my surprise, the problem returned.\nI noticed that adding this option to the QueryClient in Fleet solved the\nproblem in the Fleet tab immediately, but adding this option to the\n`SecuritySolutionQueryClient` does nothing, like it was completely\nignored.\nI searched different options and spent two more days debugging the\nproblem, but then, when paired up again with Dmitrii, he found that the\n`SecuritySolutionQueryClient` is overshadowed by some other QueryClient\npresent in the stack of components much below, the `CasesContext`. That\ndiscovery enabled me to add this new setting to the other QueryClient,\nand this fixes the issue. However, we think that it will be worth\ninvestigating why we need this second context, as the situation when one\nQueryClient overshadows another one, smells badly and may be a source of\nother issues as well (I will reach out to the team responsible for the\nCasesContext and ask if we can unify this somehow).\n\n## BEFORE\n\n\nhttps://github.com/user-attachments/assets/662dab73-b1bd-4d6b-9d15-c35efab679c6\n\n## AFTER\n\n\nhttps://github.com/user-attachments/assets/b905bde0-150d-478d-9734-9003fb5bcf66\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7ad35a4a33c3bd4d4f4e33acff20f4ebaa3242ce"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.19"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/220510","number":220510,"mergeCommit":{"message":"[Security Solution] Enforce sending the request to API even if offline, for air-gapped environment. (#220510)\n\n**Resolves: #181808**\n\n## Summary\n\nI am fixing the issue of the Rules and Alerts tabs in Security, as well\nas the Fleet tab in Management, that gets stalled in air-gapped\nenvironment. I am doing so by enforcing the request to be sent to the\nAPI even when offline.\n\n### Historical context:\nDuring investigation of the original issue #181808 I proved that Kibana\ndoesn't try to reach to EPR in the air-gapped environment (that is, with\nthe `xpack.fleet.isAirGapped: true` flag, and WIFI being turned ON). I\ncommented this\n[here](https://github.com/elastic/kibana/issues/181808#issuecomment-2829911511)\nand we closed the issue. However, @111andre111 reached out to us saying\nthat this wasn't enough, as the real issue remains, that is, Kibana\ndoesn't behave properly when:\n- `xpack.fleet.isAirGapped` flag is set to `true`\n- there is no Internet connection (WIFI off or cable physically\ndisconnected)\n\nThat's why we reopened the ticket and I restarted the investigation. \nMy first observation was that when I turn off the WIFI, I cannot see\nrequests to the API being sent in the Network tab in Dev Tools, most\nimportantly to the `_bootstrap` endpoint at the first entrance to the\nSolution app, and other endpoints later. I searched that the browser\ndiscovers being offline and suppresses such calls. When WIFI is back ON,\nthen the browser sends these requests. That was exactly what I saw in\nthe Network tab.\nI searched and found an option to force browser to always send the\nrequest, regardless of what it thinks about connectivity. Such option,\n`networkMode: 'always'`, can be added to TanStackQuery client.\n\nI started working on adding this option to occurences of `useQuery` and\n`useMutation`, and immediately sounded success, as the behavior was\ncorrect. However, @xcrzx rigthfully pointed out, that it would be much\nbetter to only add it to one place, that is the configuration of the\nQueryClient. I did it, and to my surprise, the problem returned.\nI noticed that adding this option to the QueryClient in Fleet solved the\nproblem in the Fleet tab immediately, but adding this option to the\n`SecuritySolutionQueryClient` does nothing, like it was completely\nignored.\nI searched different options and spent two more days debugging the\nproblem, but then, when paired up again with Dmitrii, he found that the\n`SecuritySolutionQueryClient` is overshadowed by some other QueryClient\npresent in the stack of components much below, the `CasesContext`. That\ndiscovery enabled me to add this new setting to the other QueryClient,\nand this fixes the issue. However, we think that it will be worth\ninvestigating why we need this second context, as the situation when one\nQueryClient overshadows another one, smells badly and may be a source of\nother issues as well (I will reach out to the team responsible for the\nCasesContext and ask if we can unify this somehow).\n\n## BEFORE\n\n\nhttps://github.com/user-attachments/assets/662dab73-b1bd-4d6b-9d15-c35efab679c6\n\n## AFTER\n\n\nhttps://github.com/user-attachments/assets/b905bde0-150d-478d-9734-9003fb5bcf66\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7ad35a4a33c3bd4d4f4e33acff20f4ebaa3242ce"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co> |
||
Lene Gadewoll
|
3a7dba9ff8
|
[9.0] Upgrade EUI to v102.3.0 (#222149) (#223091)
# Backport This will backport the following commits from `main` to `9.0`: - [Upgrade EUI to v102.3.0 (#222149)](https://github.com/elastic/kibana/pull/222149) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lene Gadewoll","email":"lene.gadewoll@elastic.co"},"sourceCommit":{"committedDate":"2025-06-09T09:04:46Z","message":"Upgrade EUI to v102.3.0 (#222149)\n\n`102.2.0` ⏩ `102.3.0`\n\n[Questions? Please see our Kibana upgrade\nFAQ.](https://github.com/elastic/eui/blob/main/wiki/eui-team-processes/upgrading-kibana.md#faq-for-kibana-teams)\n\n## Changes\n\n>[!IMPORTANT]\nThis release contains the visual refresh updates for buttons ⏹️ 💅 \nThese have already been available for QA ahead of time on [this\nPR](https://github.com/elastic/kibana/pull/220093).\n\n1. **EUI changes**: Adds all Visual Refresh related EUI changes on\nbutton components:\n\n- `EuiButton`\n- `EuiButtonEmpty`\n- `EuiButtonIcon`\n- `EuiButtonGroup`\n- `EuiFilterGroup`/`EuiFilterButton`\n\n2. **EUI button component API updates:** Updates instances of\n`EuiFilterButton` usages that were missing `isSelected` prop or that\nshould use the new `isToggle` prop to ensure the expected visual and\nsemantic output as toggle button.\n\n<details><summary><b>Examples of new toggle filter buttons</b></summary>\n\n| before | after |\n|---|---|\n| \n| \n|\n| \n| \n|\n| \n| \n|\n</details>\n\n\n3. **Custom styling updates:** Updates custom styling overrides on EUI\nbutton components in selected **high-visibility places** (discover,\ndashboard, lens) to ensure expected Visual Refresh output. (This is a\nfirst iteration step to ensure expected design. In the future we want to\nreplace custom buttons with proper EUI components)\n\n<details><summary><b>Updated custom button styling</b></summary>\n\n| Solution/Area | After |\n|---|---|\n| Discover(classic) | \n|\n| Discover(ES/QL) | \n|\n| Dashboard(Create Visualization) | \n|\n| Maps: Aligned map toolbar button hover | \n|\n\n</details>\n\n## Package updates\n\n### `@elastic/eui`\n\n## [`v102.3.0`](https://github.com/elastic/eui/releases/v102.3.0)\n\n- Added support for `focusTrapProps.returnFocus` on `EuiFlyout`\n([#8716](https://github.com/elastic/eui/pull/8716))\n- Updated `EuiDataGridToolbarControl` hover styles by removing\ntext-decoration and changing the badge background-color to ensure enough\ncontrast ([#8670](https://github.com/elastic/eui/pull/8670))\n- Added prop `isToggle` on `EuiFilterButton` to switch between regular\nand toggle button ([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated `hasActiveFilters` on `EuiFilterButton` to only control\nhighlighting filters, not a visual selected state\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated `EuiFilterButton` to ensure `isSelected` prop applies both\nsemantic and visual states\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated visual styling of `EuiButtonGroup`, `EuiFilterGroup` and\n`EuiFilterButton` ([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated `EuiNotificationBadge` border radius to `2px`\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated `EuiBreadcrumbs` text color for `type=\"application\"`\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Added new `refresh` design variant for button components:\n([#8595](https://github.com/elastic/eui/pull/8595))\n - `EuiButton`\n - `EuiButtonEmpty`\n - `EuiButtonIcon`\n- Added `flags.buttonVariant` with value `classic` to\n`euiThemeAmsterdam` ([#8595](https://github.com/elastic/eui/pull/8595))\n- Added new button background component tokens to Amsterdam theme:\n([#8595](https://github.com/elastic/eui/pull/8595))\n - `background{color}Hover`\n - `background{color}Active`\n - `backgroundFilled{color}Hover`\n - `backgroundFilled{color}Active`\n - `backgroundEmpty{color}Hover`\n - `backgroundEmpty{color}Active`\n\n**Bug fixes**\n\n- Fixed an issue with `EuiDataGrid` where navigating cells with\nsimultaneous key presses would result in a crash in React 18 legacy mode\n([#8698](https://github.com/elastic/eui/pull/8698))\n\n**Accessibility**\n\n- Improved the accessibility experience of `EuiMarkdownEditorFooter` by\nfixing the ARIA attributes of the `syntax help` modal.\n([#8702](https://github.com/elastic/eui/pull/8702))\n\n### `@elastic/eui-theme-borealis`\n\n## [`v1.1.0`](https://github.com/elastic/eui/releases/v1.1.0)\n\n- Added token `filterButtonBadgeBackgroundHover`\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated values for tokens `buttonGroupFocusColor` and\n`buttonGroupBackgroundDisabledSelected`\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Added `flags.buttonVariant` with value `refresh` to `euiThemeBorealis`\n([#8595](https://github.com/elastic/eui/pull/8595))\n- Added new button background component tokens:\n([#8595](https://github.com/elastic/eui/pull/8595))\n - `background{color}Hover`\n - `background{color}Active`\n - `backgroundFilled{color}Hover`\n - `backgroundFilled{color}Active`\n - `backgroundEmpty{color}Hover`\n - `backgroundEmpty{color}Active`\n- Updated `backgroundLightText` token value to `shade120`\n([#8595](https://github.com/elastic/eui/pull/8595))\n\n---------\n\nCo-authored-by: “jeramysoucy” <jeramy.soucy@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"b2d1075032238c5b6ea9a31b8271eed04a7c3b7e","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","EUI","Team:Fleet","backport:prev-minor","ci:cloud-deploy","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v9.0.2"],"title":"Upgrade EUI to v102.3.0","number":222149,"url":"https://github.com/elastic/kibana/pull/222149","mergeCommit":{"message":"Upgrade EUI to v102.3.0 (#222149)\n\n`102.2.0` ⏩ `102.3.0`\n\n[Questions? Please see our Kibana upgrade\nFAQ.](https://github.com/elastic/eui/blob/main/wiki/eui-team-processes/upgrading-kibana.md#faq-for-kibana-teams)\n\n## Changes\n\n>[!IMPORTANT]\nThis release contains the visual refresh updates for buttons ⏹️ 💅 \nThese have already been available for QA ahead of time on [this\nPR](https://github.com/elastic/kibana/pull/220093).\n\n1. **EUI changes**: Adds all Visual Refresh related EUI changes on\nbutton components:\n\n- `EuiButton`\n- `EuiButtonEmpty`\n- `EuiButtonIcon`\n- `EuiButtonGroup`\n- `EuiFilterGroup`/`EuiFilterButton`\n\n2. **EUI button component API updates:** Updates instances of\n`EuiFilterButton` usages that were missing `isSelected` prop or that\nshould use the new `isToggle` prop to ensure the expected visual and\nsemantic output as toggle button.\n\n<details><summary><b>Examples of new toggle filter buttons</b></summary>\n\n| before | after |\n|---|---|\n| \n| \n|\n| \n| \n|\n| \n| \n|\n</details>\n\n\n3. **Custom styling updates:** Updates custom styling overrides on EUI\nbutton components in selected **high-visibility places** (discover,\ndashboard, lens) to ensure expected Visual Refresh output. (This is a\nfirst iteration step to ensure expected design. In the future we want to\nreplace custom buttons with proper EUI components)\n\n<details><summary><b>Updated custom button styling</b></summary>\n\n| Solution/Area | After |\n|---|---|\n| Discover(classic) | \n|\n| Discover(ES/QL) | \n|\n| Dashboard(Create Visualization) | \n|\n| Maps: Aligned map toolbar button hover | \n|\n\n</details>\n\n## Package updates\n\n### `@elastic/eui`\n\n## [`v102.3.0`](https://github.com/elastic/eui/releases/v102.3.0)\n\n- Added support for `focusTrapProps.returnFocus` on `EuiFlyout`\n([#8716](https://github.com/elastic/eui/pull/8716))\n- Updated `EuiDataGridToolbarControl` hover styles by removing\ntext-decoration and changing the badge background-color to ensure enough\ncontrast ([#8670](https://github.com/elastic/eui/pull/8670))\n- Added prop `isToggle` on `EuiFilterButton` to switch between regular\nand toggle button ([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated `hasActiveFilters` on `EuiFilterButton` to only control\nhighlighting filters, not a visual selected state\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated `EuiFilterButton` to ensure `isSelected` prop applies both\nsemantic and visual states\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated visual styling of `EuiButtonGroup`, `EuiFilterGroup` and\n`EuiFilterButton` ([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated `EuiNotificationBadge` border radius to `2px`\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated `EuiBreadcrumbs` text color for `type=\"application\"`\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Added new `refresh` design variant for button components:\n([#8595](https://github.com/elastic/eui/pull/8595))\n - `EuiButton`\n - `EuiButtonEmpty`\n - `EuiButtonIcon`\n- Added `flags.buttonVariant` with value `classic` to\n`euiThemeAmsterdam` ([#8595](https://github.com/elastic/eui/pull/8595))\n- Added new button background component tokens to Amsterdam theme:\n([#8595](https://github.com/elastic/eui/pull/8595))\n - `background{color}Hover`\n - `background{color}Active`\n - `backgroundFilled{color}Hover`\n - `backgroundFilled{color}Active`\n - `backgroundEmpty{color}Hover`\n - `backgroundEmpty{color}Active`\n\n**Bug fixes**\n\n- Fixed an issue with `EuiDataGrid` where navigating cells with\nsimultaneous key presses would result in a crash in React 18 legacy mode\n([#8698](https://github.com/elastic/eui/pull/8698))\n\n**Accessibility**\n\n- Improved the accessibility experience of `EuiMarkdownEditorFooter` by\nfixing the ARIA attributes of the `syntax help` modal.\n([#8702](https://github.com/elastic/eui/pull/8702))\n\n### `@elastic/eui-theme-borealis`\n\n## [`v1.1.0`](https://github.com/elastic/eui/releases/v1.1.0)\n\n- Added token `filterButtonBadgeBackgroundHover`\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated values for tokens `buttonGroupFocusColor` and\n`buttonGroupBackgroundDisabledSelected`\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Added `flags.buttonVariant` with value `refresh` to `euiThemeBorealis`\n([#8595](https://github.com/elastic/eui/pull/8595))\n- Added new button background component tokens:\n([#8595](https://github.com/elastic/eui/pull/8595))\n - `background{color}Hover`\n - `background{color}Active`\n - `backgroundFilled{color}Hover`\n - `backgroundFilled{color}Active`\n - `backgroundEmpty{color}Hover`\n - `backgroundEmpty{color}Active`\n- Updated `backgroundLightText` token value to `shade120`\n([#8595](https://github.com/elastic/eui/pull/8595))\n\n---------\n\nCo-authored-by: “jeramysoucy” <jeramy.soucy@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"b2d1075032238c5b6ea9a31b8271eed04a7c3b7e"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222149","number":222149,"mergeCommit":{"message":"Upgrade EUI to v102.3.0 (#222149)\n\n`102.2.0` ⏩ `102.3.0`\n\n[Questions? Please see our Kibana upgrade\nFAQ.](https://github.com/elastic/eui/blob/main/wiki/eui-team-processes/upgrading-kibana.md#faq-for-kibana-teams)\n\n## Changes\n\n>[!IMPORTANT]\nThis release contains the visual refresh updates for buttons ⏹️ 💅 \nThese have already been available for QA ahead of time on [this\nPR](https://github.com/elastic/kibana/pull/220093).\n\n1. **EUI changes**: Adds all Visual Refresh related EUI changes on\nbutton components:\n\n- `EuiButton`\n- `EuiButtonEmpty`\n- `EuiButtonIcon`\n- `EuiButtonGroup`\n- `EuiFilterGroup`/`EuiFilterButton`\n\n2. **EUI button component API updates:** Updates instances of\n`EuiFilterButton` usages that were missing `isSelected` prop or that\nshould use the new `isToggle` prop to ensure the expected visual and\nsemantic output as toggle button.\n\n<details><summary><b>Examples of new toggle filter buttons</b></summary>\n\n| before | after |\n|---|---|\n| \n| \n|\n| \n| \n|\n| \n| \n|\n</details>\n\n\n3. **Custom styling updates:** Updates custom styling overrides on EUI\nbutton components in selected **high-visibility places** (discover,\ndashboard, lens) to ensure expected Visual Refresh output. (This is a\nfirst iteration step to ensure expected design. In the future we want to\nreplace custom buttons with proper EUI components)\n\n<details><summary><b>Updated custom button styling</b></summary>\n\n| Solution/Area | After |\n|---|---|\n| Discover(classic) | \n|\n| Discover(ES/QL) | \n|\n| Dashboard(Create Visualization) | \n|\n| Maps: Aligned map toolbar button hover | \n|\n\n</details>\n\n## Package updates\n\n### `@elastic/eui`\n\n## [`v102.3.0`](https://github.com/elastic/eui/releases/v102.3.0)\n\n- Added support for `focusTrapProps.returnFocus` on `EuiFlyout`\n([#8716](https://github.com/elastic/eui/pull/8716))\n- Updated `EuiDataGridToolbarControl` hover styles by removing\ntext-decoration and changing the badge background-color to ensure enough\ncontrast ([#8670](https://github.com/elastic/eui/pull/8670))\n- Added prop `isToggle` on `EuiFilterButton` to switch between regular\nand toggle button ([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated `hasActiveFilters` on `EuiFilterButton` to only control\nhighlighting filters, not a visual selected state\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated `EuiFilterButton` to ensure `isSelected` prop applies both\nsemantic and visual states\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated visual styling of `EuiButtonGroup`, `EuiFilterGroup` and\n`EuiFilterButton` ([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated `EuiNotificationBadge` border radius to `2px`\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated `EuiBreadcrumbs` text color for `type=\"application\"`\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Added new `refresh` design variant for button components:\n([#8595](https://github.com/elastic/eui/pull/8595))\n - `EuiButton`\n - `EuiButtonEmpty`\n - `EuiButtonIcon`\n- Added `flags.buttonVariant` with value `classic` to\n`euiThemeAmsterdam` ([#8595](https://github.com/elastic/eui/pull/8595))\n- Added new button background component tokens to Amsterdam theme:\n([#8595](https://github.com/elastic/eui/pull/8595))\n - `background{color}Hover`\n - `background{color}Active`\n - `backgroundFilled{color}Hover`\n - `backgroundFilled{color}Active`\n - `backgroundEmpty{color}Hover`\n - `backgroundEmpty{color}Active`\n\n**Bug fixes**\n\n- Fixed an issue with `EuiDataGrid` where navigating cells with\nsimultaneous key presses would result in a crash in React 18 legacy mode\n([#8698](https://github.com/elastic/eui/pull/8698))\n\n**Accessibility**\n\n- Improved the accessibility experience of `EuiMarkdownEditorFooter` by\nfixing the ARIA attributes of the `syntax help` modal.\n([#8702](https://github.com/elastic/eui/pull/8702))\n\n### `@elastic/eui-theme-borealis`\n\n## [`v1.1.0`](https://github.com/elastic/eui/releases/v1.1.0)\n\n- Added token `filterButtonBadgeBackgroundHover`\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Updated values for tokens `buttonGroupFocusColor` and\n`buttonGroupBackgroundDisabledSelected`\n([#8652](https://github.com/elastic/eui/pull/8652))\n- Added `flags.buttonVariant` with value `refresh` to `euiThemeBorealis`\n([#8595](https://github.com/elastic/eui/pull/8595))\n- Added new button background component tokens:\n([#8595](https://github.com/elastic/eui/pull/8595))\n - `background{color}Hover`\n - `background{color}Active`\n - `backgroundFilled{color}Hover`\n - `backgroundFilled{color}Active`\n - `backgroundEmpty{color}Hover`\n - `backgroundEmpty{color}Active`\n- Updated `backgroundLightText` token value to `shade120`\n([#8595](https://github.com/elastic/eui/pull/8595))\n\n---------\n\nCo-authored-by: “jeramysoucy” <jeramy.soucy@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"b2d1075032238c5b6ea9a31b8271eed04a7c3b7e"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Alejandro Fernández Haro
|
cd00c41781
|
[9.0] Update dependency @elastic/ebt to ^1.2.0 (main) (#222852) (#223112)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency @elastic/ebt to ^1.2.0 (main) (#222852)](https://github.com/elastic/kibana/pull/222852) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-06T08:13:25Z","message":"Update dependency @elastic/ebt to ^1.2.0 (main) (#222852)","sha":"6540ec423cb6f6364accfb99dd837898f8c5adc9","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:version","v9.1.0","v8.19.0"],"title":"Update dependency @elastic/ebt to ^1.2.0 (main)","number":222852,"url":"https://github.com/elastic/kibana/pull/222852","mergeCommit":{"message":"Update dependency @elastic/ebt to ^1.2.0 (main) (#222852)","sha":"6540ec423cb6f6364accfb99dd837898f8c5adc9"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.19"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222852","number":222852,"mergeCommit":{"message":"Update dependency @elastic/ebt to ^1.2.0 (main) (#222852)","sha":"6540ec423cb6f6364accfb99dd837898f8c5adc9"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
0bacbd1648
|
[9.0] Update dependency msw to ~2.8.7 (main) (#220758) (#223160)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency msw to ~2.8.7 (main) (#220758)](https://github.com/elastic/kibana/pull/220758) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-09T20:27:35Z","message":"Update dependency msw to ~2.8.7 (main) (#220758)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change | Pending |\n|---|---|---|---|---|\n| [msw](https://mswjs.io)\n([source](https://redirect.github.com/mswjs/msw)) | devDependencies |\nminor | [`~2.7.5` ->\n`~2.8.7`](https://renovatebot.com/diffs/npm/msw/2.7.5/2.8.7) | `2.10.2`\n(+3) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>mswjs/msw (msw)</summary>\n\n###\n[`v2.8.7`](https://redirect.github.com/mswjs/msw/releases/tag/v2.8.7)\n\n[Compare\nSource](https://redirect.github.com/mswjs/msw/compare/v2.8.6...v2.8.7)\n\n#### v2.8.7 (2025-05-31)\n\n##### Bug Fixes\n\n- update links to the documentation\n([#​2519]( |
||
|
Kibana Machine
|
321b4779f8
|
[9.0] Update dependency launchdarkly-js-client-sdk to ^3.8.1 (main) (#223063) (#223147)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency launchdarkly-js-client-sdk to ^3.8.1 (main) (#223063)](https://github.com/elastic/kibana/pull/223063) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-09T19:27:10Z","message":"Update dependency launchdarkly-js-client-sdk to ^3.8.1 (main) (#223063)\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>","sha":"a3f0570ca87c7ce708c0487508f837bedb4cfafa","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","Team:Security","release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"Update dependency launchdarkly-js-client-sdk to ^3.8.1 (main)","number":223063,"url":"https://github.com/elastic/kibana/pull/223063","mergeCommit":{"message":"Update dependency launchdarkly-js-client-sdk to ^3.8.1 (main) (#223063)\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>","sha":"a3f0570ca87c7ce708c0487508f837bedb4cfafa"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223063","number":223063,"mergeCommit":{"message":"Update dependency launchdarkly-js-client-sdk to ^3.8.1 (main) (#223063)\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>","sha":"a3f0570ca87c7ce708c0487508f837bedb4cfafa"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co> |
||
|
Kibana Machine
|
97dd882d3c
|
[9.0] Upgrade Node.js to 20.19.2 (#221177) (#223128)
# Backport This will backport the following commits from `main` to `9.0`: - [Upgrade Node.js to 20.19.2 (#221177)](https://github.com/elastic/kibana/pull/221177) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jon","email":"jon@elastic.co"},"sourceCommit":{"committedDate":"2025-06-09T17:17:42Z","message":"Upgrade Node.js to 20.19.2 (#221177)\n\nhttps://github.com/nodejs/node/releases/tag/v20.19.2\n\n---------\n\nCo-authored-by: Tiago Costa <tiago.costa@elastic.co>","sha":"96f48648a90333792f8da150667025423d7ff1b1","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","v9.1.0"],"title":"Upgrade Node.js to 20.19.2","number":221177,"url":"https://github.com/elastic/kibana/pull/221177","mergeCommit":{"message":"Upgrade Node.js to 20.19.2 (#221177)\n\nhttps://github.com/nodejs/node/releases/tag/v20.19.2\n\n---------\n\nCo-authored-by: Tiago Costa <tiago.costa@elastic.co>","sha":"96f48648a90333792f8da150667025423d7ff1b1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/221177","number":221177,"mergeCommit":{"message":"Upgrade Node.js to 20.19.2 (#221177)\n\nhttps://github.com/nodejs/node/releases/tag/v20.19.2\n\n---------\n\nCo-authored-by: Tiago Costa <tiago.costa@elastic.co>","sha":"96f48648a90333792f8da150667025423d7ff1b1"}}]}] BACKPORT--> Co-authored-by: Jon <jon@elastic.co> Co-authored-by: Tiago Costa <tiago.costa@elastic.co> |
||
|
Viduni Wickramarachchi
|
360283e6c7
|
[9.0] [Obs AI Assistant] Improve system prompt and instructions to work better with Claude models (#221965) (#223009)
# Backport This will backport the following commits from `main` to `9.0`: - [[Obs AI Assistant] Improve system prompt and instructions to work better with Claude models (#221965)](https://github.com/elastic/kibana/pull/221965) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Viduni Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2025-06-05T22:28:38Z","message":"[Obs AI Assistant] Improve system prompt and instructions to work better with Claude models (#221965)","sha":"76d926554ebb3d4ae8b7378615aacbcf3ae963f4","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Obs AI Assistant","ci:project-deploy-observability","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[Obs AI Assistant] Improve system prompt and instructions to work better with Claude models","number":221965,"url":"https://github.com/elastic/kibana/pull/221965","mergeCommit":{"message":"[Obs AI Assistant] Improve system prompt and instructions to work better with Claude models (#221965)","sha":"76d926554ebb3d4ae8b7378615aacbcf3ae963f4"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/221965","number":221965,"mergeCommit":{"message":"[Obs AI Assistant] Improve system prompt and instructions to work better with Claude models (#221965)","sha":"76d926554ebb3d4ae8b7378615aacbcf3ae963f4"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
86bfdd964a
|
[9.0] [Detection Engine] Fix and unskip cypress suite related to ES|QL rule creation (#222467) (#223059)
# Backport This will backport the following commits from `main` to `9.0`: - [[Detection Engine] Fix and unskip cypress suite related to ES|QL rule creation (#222467)](https://github.com/elastic/kibana/pull/222467) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ryland Herrick","email":"ryalnd@gmail.com"},"sourceCommit":{"committedDate":"2025-06-06T20:55:20Z","message":"[Detection Engine] Fix and unskip cypress suite related to ES|QL rule creation (#222467)\n\nA [recent change](https://github.com/elastic/elasticsearch/pull/128464)\nto the ES|QL syntax seems to have broken this test, which assumed that\nthe clause `limit 5 true` is a syntax error in ES|QL.\n\nRegardless of whether or not that's correct, the test just needs a\nsyntactically-invalid (and non-aggregating) query, which it now has,\nagain. Closes https://github.com/elastic/kibana/issues/222182.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"0fb44f87cdb60df506827ee1e7c07dd4dafdba83","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Feature:Rule Creation","Team:Detection Engine","backport:version","Feature: ES|QL Rule","8.19 candidate","v9.1.0","v8.19.0"],"title":"[Detection Engine] Fix and unskip cypress suite related to ES|QL rule creation","number":222467,"url":"https://github.com/elastic/kibana/pull/222467","mergeCommit":{"message":"[Detection Engine] Fix and unskip cypress suite related to ES|QL rule creation (#222467)\n\nA [recent change](https://github.com/elastic/elasticsearch/pull/128464)\nto the ES|QL syntax seems to have broken this test, which assumed that\nthe clause `limit 5 true` is a syntax error in ES|QL.\n\nRegardless of whether or not that's correct, the test just needs a\nsyntactically-invalid (and non-aggregating) query, which it now has,\nagain. Closes https://github.com/elastic/kibana/issues/222182.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"0fb44f87cdb60df506827ee1e7c07dd4dafdba83"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.19"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222467","number":222467,"mergeCommit":{"message":"[Detection Engine] Fix and unskip cypress suite related to ES|QL rule creation (#222467)\n\nA [recent change](https://github.com/elastic/elasticsearch/pull/128464)\nto the ES|QL syntax seems to have broken this test, which assumed that\nthe clause `limit 5 true` is a syntax error in ES|QL.\n\nRegardless of whether or not that's correct, the test just needs a\nsyntactically-invalid (and non-aggregating) query, which it now has,\nagain. Closes https://github.com/elastic/kibana/issues/222182.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"0fb44f87cdb60df506827ee1e7c07dd4dafdba83"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ryland Herrick <ryalnd@gmail.com> |
||
|
Kibana Machine
|
d8c6c5c977
|
[9.0] Update dependency pirates to ^4.0.7 (main) (#203259) (#222917)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency pirates to ^4.0.7 (main) (#203259)](https://github.com/elastic/kibana/pull/203259) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-06T02:04:49Z","message":"Update dependency pirates to ^4.0.7 (main) (#203259)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [pirates](https://redirect.github.com/danez/pirates) | devDependencies\n| patch | [`^4.0.1` ->\n`^4.0.7`](https://renovatebot.com/diffs/npm/pirates/4.0.6/4.0.7) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>danez/pirates (pirates)</summary>\n\n###\n[`v4.0.7`](https://redirect.github.com/danez/pirates/releases/tag/v4.0.7)\n\n[Compare\nSource](https://redirect.github.com/danez/pirates/compare/v4.0.6...v4.0.7)\n\n##### Bug Fixes\n\n- remove build process and ship source directly\n([924ccc3]( |
||
Brad White
|
57a9fd0197
|
[9.0] Update dependency sort-package-json to v3 (main) (#203289) (#222909)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency sort-package-json to v3 (main) (#203289)](https://github.com/elastic/kibana/pull/203289) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-04T19:39:39Z","message":"Update dependency sort-package-json to v3 (main) (#203289)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n|\n[sort-package-json](https://redirect.github.com/keithamus/sort-package-json)\n| devDependencies | major | [`^1.53.1` ->\n`^3.2.1`](https://renovatebot.com/diffs/npm/sort-package-json/1.53.1/3.2.1)\n|\n\n---\n\n### Release Notes\n\n<details>\n<summary>keithamus/sort-package-json (sort-package-json)</summary>\n\n###\n[`v3.2.1`](https://redirect.github.com/keithamus/sort-package-json/releases/tag/v3.2.1)\n\n[Compare\nSource](https://redirect.github.com/keithamus/sort-package-json/compare/v3.2.0...v3.2.1)\n\n##### Bug Fixes\n\n- prevent sorting when npm-run-all2 is used\n([#​361]( |
||
Michael Olorunnisola
|
89d877b21d
|
[9.0] [Performance][Security Solution][2/4] - Timeline Performance (#212478) (#222989)
# Backport This will backport the following commits from `main` to `9.0`: - [[Performance][Security Solution][2/4] - Timeline Performance (#212478)](https://github.com/elastic/kibana/pull/212478) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Michael Olorunnisola","email":"michael.olorunnisola@elastic.co"},"sourceCommit":{"committedDate":"2025-03-11T16:56:45Z","message":"[Performance][Security Solution][2/4] - Timeline Performance (#212478)\n\n## Summary\nPart 2 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\n**Areas/How to test:**\n- For the following pages, test there are no `fields` api requests in\nthe inspector network tab when visiting from another page. IF YOU\nREFRESH on any of these pages, you will see these requests as they are\ncalled by the Query Search Bar and the `useInitSourcerer` call\n - Cases Page\n - Dashboard Page\n - Timelines Page\n- Timeline\n - All Tabs\n - Does it show the loading screen on first interaction?\n - Does the `fields` api fire on first interaction with the tab\n - When you navigate back to those tabs, do they not re-render?\n- All other pages hosting timeline\n - Do you feel like the performance is generally better?\n\n\n### Background\n\nWhen investigating the performance of the security solution application,\none of the issues that was observed was queries to the `fields` api on\npages that had no reason making that request (such as Cases, or the\nDashboards list view). This was due to the background background loaded\ntabs of timeline loading the relevant `dataView` necessary for their\nsearch functionality. When the fields request is significantly large\nthis can have a massive impact on the experience of users on pages that\nshould be relatively responsive.\n\nTo fix this a few changes were made. \n\n1. First the `withDataView` HOC was removed as it was only used in 2\ncomponents that shared a parent - child relationship, and the child\n`UnifiedTimeline` was only used in the parent. The hook that HOC calls\nwas not caching the dataView being created, so `dataView.create` was\nbeing called up to 6 times unnecessarily. Now it is only called once in\neach tab.\n\n2. A new wrapper `OnDemandRenderer` (open to different naming 😅) was\ncreated that will not render any of the nested tabs until they are\nopened. Once they are opened, they stay in memory, to avoid re-calling\nexpensive api's every time a user switches tabs.\n_Note_: There is currently a known issue where navigating between\nvarious routes in security solution causes the whole application to\nunmount and re-mount. Which means every page change will lead to\ntimeline needing to be re-loaded when the tab is opened. This is being\nresolved in a separate effort.\n\n3. Additional checks were added to the `useTimelineEvents` hook to limit\nadditional re-renders caused by unnecessary reference changes when the\nunderlying values never actually change\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n### Identify risks","sha":"2d8f3c1544aa6bff74623273a278f580df0d918d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat Hunting:Investigations","ci:cloud-deploy","ci:project-redeploy","backport:version","v9.1.0","v8.19.0","v8.17.5"],"title":"[Performance][Security Solution][2/4] - Timeline Performance","number":212478,"url":"https://github.com/elastic/kibana/pull/212478","mergeCommit":{"message":"[Performance][Security Solution][2/4] - Timeline Performance (#212478)\n\n## Summary\nPart 2 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\n**Areas/How to test:**\n- For the following pages, test there are no `fields` api requests in\nthe inspector network tab when visiting from another page. IF YOU\nREFRESH on any of these pages, you will see these requests as they are\ncalled by the Query Search Bar and the `useInitSourcerer` call\n - Cases Page\n - Dashboard Page\n - Timelines Page\n- Timeline\n - All Tabs\n - Does it show the loading screen on first interaction?\n - Does the `fields` api fire on first interaction with the tab\n - When you navigate back to those tabs, do they not re-render?\n- All other pages hosting timeline\n - Do you feel like the performance is generally better?\n\n\n### Background\n\nWhen investigating the performance of the security solution application,\none of the issues that was observed was queries to the `fields` api on\npages that had no reason making that request (such as Cases, or the\nDashboards list view). This was due to the background background loaded\ntabs of timeline loading the relevant `dataView` necessary for their\nsearch functionality. When the fields request is significantly large\nthis can have a massive impact on the experience of users on pages that\nshould be relatively responsive.\n\nTo fix this a few changes were made. \n\n1. First the `withDataView` HOC was removed as it was only used in 2\ncomponents that shared a parent - child relationship, and the child\n`UnifiedTimeline` was only used in the parent. The hook that HOC calls\nwas not caching the dataView being created, so `dataView.create` was\nbeing called up to 6 times unnecessarily. Now it is only called once in\neach tab.\n\n2. A new wrapper `OnDemandRenderer` (open to different naming 😅) was\ncreated that will not render any of the nested tabs until they are\nopened. Once they are opened, they stay in memory, to avoid re-calling\nexpensive api's every time a user switches tabs.\n_Note_: There is currently a known issue where navigating between\nvarious routes in security solution causes the whole application to\nunmount and re-mount. Which means every page change will lead to\ntimeline needing to be re-loaded when the tab is opened. This is being\nresolved in a separate effort.\n\n3. Additional checks were added to the `useTimelineEvents` hook to limit\nadditional re-renders caused by unnecessary reference changes when the\nunderlying values never actually change\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n### Identify risks","sha":"2d8f3c1544aa6bff74623273a278f580df0d918d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212478","number":212478,"mergeCommit":{"message":"[Performance][Security Solution][2/4] - Timeline Performance (#212478)\n\n## Summary\nPart 2 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\n**Areas/How to test:**\n- For the following pages, test there are no `fields` api requests in\nthe inspector network tab when visiting from another page. IF YOU\nREFRESH on any of these pages, you will see these requests as they are\ncalled by the Query Search Bar and the `useInitSourcerer` call\n - Cases Page\n - Dashboard Page\n - Timelines Page\n- Timeline\n - All Tabs\n - Does it show the loading screen on first interaction?\n - Does the `fields` api fire on first interaction with the tab\n - When you navigate back to those tabs, do they not re-render?\n- All other pages hosting timeline\n - Do you feel like the performance is generally better?\n\n\n### Background\n\nWhen investigating the performance of the security solution application,\none of the issues that was observed was queries to the `fields` api on\npages that had no reason making that request (such as Cases, or the\nDashboards list view). This was due to the background background loaded\ntabs of timeline loading the relevant `dataView` necessary for their\nsearch functionality. When the fields request is significantly large\nthis can have a massive impact on the experience of users on pages that\nshould be relatively responsive.\n\nTo fix this a few changes were made. \n\n1. First the `withDataView` HOC was removed as it was only used in 2\ncomponents that shared a parent - child relationship, and the child\n`UnifiedTimeline` was only used in the parent. The hook that HOC calls\nwas not caching the dataView being created, so `dataView.create` was\nbeing called up to 6 times unnecessarily. Now it is only called once in\neach tab.\n\n2. A new wrapper `OnDemandRenderer` (open to different naming 😅) was\ncreated that will not render any of the nested tabs until they are\nopened. Once they are opened, they stay in memory, to avoid re-calling\nexpensive api's every time a user switches tabs.\n_Note_: There is currently a known issue where navigating between\nvarious routes in security solution causes the whole application to\nunmount and re-mount. Which means every page change will lead to\ntimeline needing to be re-loaded when the tab is opened. This is being\nresolved in a separate effort.\n\n3. Additional checks were added to the `useTimelineEvents` hook to limit\nadditional re-renders caused by unnecessary reference changes when the\nunderlying values never actually change\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n### Identify risks","sha":"2d8f3c1544aa6bff74623273a278f580df0d918d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/215791","number":215791,"state":"MERGED","mergeCommit":{"sha":"45922ffa0196328ccb715fa2f2af1cc9d0fae139","message":"[8.x] [Performance][Security Solution][2/4] - Timeline Performance (#212478) (#215791)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Performance][Security Solution][2/4] - Timeline Performance\n(#212478)](https://github.com/elastic/kibana/pull/212478)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n"}},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213988","number":213988,"state":"MERGED","mergeCommit":{"sha":"3febe25204eaf1c83970a7010ef63ac1d3fa8431","message":"[8.17] [Performance][Security Solution][2/4] - Timeline Performance (#212478) (#213988)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.17`:\n- [[Performance][Security Solution][2/4] - Timeline Performance\n(#212478)](https://github.com/elastic/kibana/pull/212478)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n"}},{"url":"https://github.com/elastic/kibana/pull/222987","number":222987,"branch":"8.18","state":"OPEN"}]}] BACKPORT--> |
||
Kenneth Kreindler
|
d5fd19058f
|
[9.0] [Security solution][AI assistant] bug: encode security labs content to prevent antivirus false positive (#221656) (#222951)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security solution][AI assistant] bug: encode security labs content to prevent antivirus false positive (#221656)](https://github.com/elastic/kibana/pull/221656) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Kenneth Kreindler","email":"42113355+KDKHD@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-06T09:16:48Z","message":"[Security solution][AI assistant] bug: encode security labs content to prevent antivirus false positive (#221656)\n\n## Summary\n\nFixes: https://github.com/elastic/kibana/issues/202114\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\n\nThis PR addresses the following\n[issue](https://github.com/elastic/kibana/issues/202114).\n\n#### Problem \nThe security labs' content is triggering false positive anti-virus\nalerts from [ESET cyber\nsecurity](https://www.eset.com/uk/home/cyber-security/?srsltid=AfmBOorLSTn6FfQXm9h4rm2nDpma91Q9-IfHmeUg4TuRL4TvMF9xB-Cc).\nThis is because the content contains specific words and YARA rules that\nthe antivirus picks up as malware. The content is not dangerous.\n\n#### Solution \nEncrypt the content so that the Yara rules do not trigger alerts. The\ncontent is encrypted with AES-256-ECB and the key `ELASTIC`. The\nencryption is not secure and does not need to be secure (we just want to\nobfuscate the content).\n\n#### Considerations\n- An alternative approach to fixing this issue that was considered was\nbuilding an integration so that the content is only imported after\nKibana has been started. As a team, we decided against this because it\nis convenient for airgapped systems to have the secure labs content\nshipped with the installation.\n- It would be great to test this fix against many antivirus providers,\nhowever, I haven't found a tool that lets me do this quickly.\n\n## How to test\n#### Verify the security labs content is encoded\n- Check out the PR\n- Run the following\n```bash\nyarn kbn bootstrap\nyarn build\n```\n- The build may not fully complete locally; however, you should still be\nable to see the build files at `/build`. Inspect the content of the\nfollowing folder:\n`build/kibana/node_modules/@kbn/elastic-assistant-plugin/server/knowledge_base/security_labs`\nand verify that only files ending with `.encoded.md` exist. The content\nof these files should not be human-readable.\n\n\n\n\n#### Verify the security labs content is encoded in the cloud/serverless\nbuild (optional)\n- Log into docker.elastic.co in your terminal. Do this by heading to\nhttps://docker-auth.elastic.co/ (more info\n[here](https://elasticprod.service-now.com/esc?id=kb_article&table=kb_knowledge&sys_id=e8d361c747abb910ffad4438946d439a&recordUrl=kb_view.do%3Fsysparm_article%3DKB0012946))\n- Use the latest CI run to get the serverless docker image and start an\ninteractive shell with it:\n```bash\ndocker run -it --rm docker.elastic.co/kibana-ci/kibana-serverless:pr-221656-ae41a481bbfc sh\n```\n- Inspect the contents of the following directory and verify that only\n`.encoded.md` files exist.\n```bash\ncd node_modules/@kbn/elastic-assistant-plugin/server/knowledge_base/security_labs/\nls\n```\n- Repeat the last 2 steps for the cloud deployment image (also found in\nthe CI)\n\n<img width=\"1233\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/5d308537-b0a9-4bd0-a449-6ddae1ca1bfb\"\n/>\n\n#### Verify security labs content can be installed\n- Start Kibana locally\n- Head over to\n`http://localhost:5601/app/management/kibana/securityAiAssistantManagement?tab=knowledge_base`\nand install the knowledge base.\n\n<img width=\"1454\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e8c4b557-ea45-4c58-96ff-aacce47e9982\"\n/>\n\n- Check that the security labs content is being installed\n\n<img width=\"1456\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e7c2b128-ee94-436e-b4e0-1d48cb9d19cb\"\n/>\n\n- Once the security labs content is installed, go to the security AI\nassistant and ask the following: `Which malware is mentioned in the\nsecurity labs content. Include citations`\n- Verify the assistant gives a proper response and the citation links to\nthe Elastic Security Labs page.\n\n<img width=\"859\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e89e523c-3054-4b8b-a3c3-2857cb1ed8cd\"\n/>\n\n#### Verify antivirus does not trigger (optional)\n- Download and install ESET Cyber security trial from\n[here](https://www.eset.com/uk/home/cyber-security/?srsltid=AfmBOorLSTn6FfQXm9h4rm2nDpma91Q9-IfHmeUg4TuRL4TvMF9xB-Cc)\n- Open up the ESET\n- Click on `custom scan` and run the scan on the folder `build/kibana`\n\n\n\n\n- Expect no alerts to be triggered\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [X] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [X]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [X] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [X] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [X] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [X] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by: Garrett Spong <garrett.spong@elastic.co>\nCo-authored-by: Garrett Spong <spong@users.noreply.github.com>","sha":"973c8f30a69fa785a149cc50747d99c1db4ce7b6","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","ci:cloud-deploy","ci:project-deploy-security","Team:Security Generative AI","backport:version","v9.1.0","v9.0.3","v8.18.3","v8.17.8"],"title":"[Security solution][AI assistant] bug: encode security labs content to prevent antivirus false positive","number":221656,"url":"https://github.com/elastic/kibana/pull/221656","mergeCommit":{"message":"[Security solution][AI assistant] bug: encode security labs content to prevent antivirus false positive (#221656)\n\n## Summary\n\nFixes: https://github.com/elastic/kibana/issues/202114\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\n\nThis PR addresses the following\n[issue](https://github.com/elastic/kibana/issues/202114).\n\n#### Problem \nThe security labs' content is triggering false positive anti-virus\nalerts from [ESET cyber\nsecurity](https://www.eset.com/uk/home/cyber-security/?srsltid=AfmBOorLSTn6FfQXm9h4rm2nDpma91Q9-IfHmeUg4TuRL4TvMF9xB-Cc).\nThis is because the content contains specific words and YARA rules that\nthe antivirus picks up as malware. The content is not dangerous.\n\n#### Solution \nEncrypt the content so that the Yara rules do not trigger alerts. The\ncontent is encrypted with AES-256-ECB and the key `ELASTIC`. The\nencryption is not secure and does not need to be secure (we just want to\nobfuscate the content).\n\n#### Considerations\n- An alternative approach to fixing this issue that was considered was\nbuilding an integration so that the content is only imported after\nKibana has been started. As a team, we decided against this because it\nis convenient for airgapped systems to have the secure labs content\nshipped with the installation.\n- It would be great to test this fix against many antivirus providers,\nhowever, I haven't found a tool that lets me do this quickly.\n\n## How to test\n#### Verify the security labs content is encoded\n- Check out the PR\n- Run the following\n```bash\nyarn kbn bootstrap\nyarn build\n```\n- The build may not fully complete locally; however, you should still be\nable to see the build files at `/build`. Inspect the content of the\nfollowing folder:\n`build/kibana/node_modules/@kbn/elastic-assistant-plugin/server/knowledge_base/security_labs`\nand verify that only files ending with `.encoded.md` exist. The content\nof these files should not be human-readable.\n\n\n\n\n#### Verify the security labs content is encoded in the cloud/serverless\nbuild (optional)\n- Log into docker.elastic.co in your terminal. Do this by heading to\nhttps://docker-auth.elastic.co/ (more info\n[here](https://elasticprod.service-now.com/esc?id=kb_article&table=kb_knowledge&sys_id=e8d361c747abb910ffad4438946d439a&recordUrl=kb_view.do%3Fsysparm_article%3DKB0012946))\n- Use the latest CI run to get the serverless docker image and start an\ninteractive shell with it:\n```bash\ndocker run -it --rm docker.elastic.co/kibana-ci/kibana-serverless:pr-221656-ae41a481bbfc sh\n```\n- Inspect the contents of the following directory and verify that only\n`.encoded.md` files exist.\n```bash\ncd node_modules/@kbn/elastic-assistant-plugin/server/knowledge_base/security_labs/\nls\n```\n- Repeat the last 2 steps for the cloud deployment image (also found in\nthe CI)\n\n<img width=\"1233\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/5d308537-b0a9-4bd0-a449-6ddae1ca1bfb\"\n/>\n\n#### Verify security labs content can be installed\n- Start Kibana locally\n- Head over to\n`http://localhost:5601/app/management/kibana/securityAiAssistantManagement?tab=knowledge_base`\nand install the knowledge base.\n\n<img width=\"1454\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e8c4b557-ea45-4c58-96ff-aacce47e9982\"\n/>\n\n- Check that the security labs content is being installed\n\n<img width=\"1456\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e7c2b128-ee94-436e-b4e0-1d48cb9d19cb\"\n/>\n\n- Once the security labs content is installed, go to the security AI\nassistant and ask the following: `Which malware is mentioned in the\nsecurity labs content. Include citations`\n- Verify the assistant gives a proper response and the citation links to\nthe Elastic Security Labs page.\n\n<img width=\"859\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e89e523c-3054-4b8b-a3c3-2857cb1ed8cd\"\n/>\n\n#### Verify antivirus does not trigger (optional)\n- Download and install ESET Cyber security trial from\n[here](https://www.eset.com/uk/home/cyber-security/?srsltid=AfmBOorLSTn6FfQXm9h4rm2nDpma91Q9-IfHmeUg4TuRL4TvMF9xB-Cc)\n- Open up the ESET\n- Click on `custom scan` and run the scan on the folder `build/kibana`\n\n\n\n\n- Expect no alerts to be triggered\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [X] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [X]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [X] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [X] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [X] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [X] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by: Garrett Spong <garrett.spong@elastic.co>\nCo-authored-by: Garrett Spong <spong@users.noreply.github.com>","sha":"973c8f30a69fa785a149cc50747d99c1db4ce7b6"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/221656","number":221656,"mergeCommit":{"message":"[Security solution][AI assistant] bug: encode security labs content to prevent antivirus false positive (#221656)\n\n## Summary\n\nFixes: https://github.com/elastic/kibana/issues/202114\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\n\nThis PR addresses the following\n[issue](https://github.com/elastic/kibana/issues/202114).\n\n#### Problem \nThe security labs' content is triggering false positive anti-virus\nalerts from [ESET cyber\nsecurity](https://www.eset.com/uk/home/cyber-security/?srsltid=AfmBOorLSTn6FfQXm9h4rm2nDpma91Q9-IfHmeUg4TuRL4TvMF9xB-Cc).\nThis is because the content contains specific words and YARA rules that\nthe antivirus picks up as malware. The content is not dangerous.\n\n#### Solution \nEncrypt the content so that the Yara rules do not trigger alerts. The\ncontent is encrypted with AES-256-ECB and the key `ELASTIC`. The\nencryption is not secure and does not need to be secure (we just want to\nobfuscate the content).\n\n#### Considerations\n- An alternative approach to fixing this issue that was considered was\nbuilding an integration so that the content is only imported after\nKibana has been started. As a team, we decided against this because it\nis convenient for airgapped systems to have the secure labs content\nshipped with the installation.\n- It would be great to test this fix against many antivirus providers,\nhowever, I haven't found a tool that lets me do this quickly.\n\n## How to test\n#### Verify the security labs content is encoded\n- Check out the PR\n- Run the following\n```bash\nyarn kbn bootstrap\nyarn build\n```\n- The build may not fully complete locally; however, you should still be\nable to see the build files at `/build`. Inspect the content of the\nfollowing folder:\n`build/kibana/node_modules/@kbn/elastic-assistant-plugin/server/knowledge_base/security_labs`\nand verify that only files ending with `.encoded.md` exist. The content\nof these files should not be human-readable.\n\n\n\n\n#### Verify the security labs content is encoded in the cloud/serverless\nbuild (optional)\n- Log into docker.elastic.co in your terminal. Do this by heading to\nhttps://docker-auth.elastic.co/ (more info\n[here](https://elasticprod.service-now.com/esc?id=kb_article&table=kb_knowledge&sys_id=e8d361c747abb910ffad4438946d439a&recordUrl=kb_view.do%3Fsysparm_article%3DKB0012946))\n- Use the latest CI run to get the serverless docker image and start an\ninteractive shell with it:\n```bash\ndocker run -it --rm docker.elastic.co/kibana-ci/kibana-serverless:pr-221656-ae41a481bbfc sh\n```\n- Inspect the contents of the following directory and verify that only\n`.encoded.md` files exist.\n```bash\ncd node_modules/@kbn/elastic-assistant-plugin/server/knowledge_base/security_labs/\nls\n```\n- Repeat the last 2 steps for the cloud deployment image (also found in\nthe CI)\n\n<img width=\"1233\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/5d308537-b0a9-4bd0-a449-6ddae1ca1bfb\"\n/>\n\n#### Verify security labs content can be installed\n- Start Kibana locally\n- Head over to\n`http://localhost:5601/app/management/kibana/securityAiAssistantManagement?tab=knowledge_base`\nand install the knowledge base.\n\n<img width=\"1454\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e8c4b557-ea45-4c58-96ff-aacce47e9982\"\n/>\n\n- Check that the security labs content is being installed\n\n<img width=\"1456\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e7c2b128-ee94-436e-b4e0-1d48cb9d19cb\"\n/>\n\n- Once the security labs content is installed, go to the security AI\nassistant and ask the following: `Which malware is mentioned in the\nsecurity labs content. Include citations`\n- Verify the assistant gives a proper response and the citation links to\nthe Elastic Security Labs page.\n\n<img width=\"859\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e89e523c-3054-4b8b-a3c3-2857cb1ed8cd\"\n/>\n\n#### Verify antivirus does not trigger (optional)\n- Download and install ESET Cyber security trial from\n[here](https://www.eset.com/uk/home/cyber-security/?srsltid=AfmBOorLSTn6FfQXm9h4rm2nDpma91Q9-IfHmeUg4TuRL4TvMF9xB-Cc)\n- Open up the ESET\n- Click on `custom scan` and run the scan on the folder `build/kibana`\n\n\n\n\n- Expect no alerts to be triggered\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [X] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [X]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [X] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [X] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [X] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [X] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by: Garrett Spong <garrett.spong@elastic.co>\nCo-authored-by: Garrett Spong <spong@users.noreply.github.com>","sha":"973c8f30a69fa785a149cc50747d99c1db4ce7b6"}},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Garrett Spong <garrett.spong@elastic.co> Co-authored-by: Garrett Spong <spong@users.noreply.github.com> |
||
Ersin Erdal
|
865fa67b21
|
[9.0] Upgrade Puppeteer to v24.8.1 (#220310) (#222992)
# Backport This will backport the following commits from `main` to `9.0`: - [Upgrade Puppeteer to v24.8.1 (#220310)](https://github.com/elastic/kibana/pull/220310) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ersin Erdal","email":"92688503+ersin-erdal@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-05-22T14:46:48Z","message":"Upgrade Puppeteer to v24.8.1 (#220310)\n\nThis PR upgrades Puppeteer version to v24.8.1.\n\nBelow is a screenshot to successful download of the new version.\n\n<img width=\"1543\" alt=\"Screenshot 2025-05-07 at 14 31 23\"\nsrc=\"https://github.com/user-attachments/assets/e81d70ae-3df3-4371-ab4d-090fecf93d67\"\n/>\n\n\n---\n\nTested on CI, PNG and PDF reports were successfully generated:\n<img width=\"911\" alt=\"Screenshot 2025-05-09 at 16 55 30\"\nsrc=\"https://github.com/user-attachments/assets/fa65cfe8-5af0-4114-bbb7-b324951e5d41\"\n/>\n\n---\n\nTested on Windows in a VM. PNG and PDF reports were successfully\ngenerated:\n\n<img width=\"1129\" alt=\"Screenshot 2025-05-21 at 20 28 40\"\nsrc=\"https://github.com/user-attachments/assets/9e3c16f2-03d6-4b00-a402-4d007bcd1685\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"8ec7546a561e434cf04082e23dcb7846ce657093","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","ci:cloud-deploy","backport:version","v7.17.28","v9.1.0","v8.19.0","v8.17.7","v8.18.2","v9.0.2"],"title":"Upgrade Puppeteer to v24.8.1","number":220310,"url":"https://github.com/elastic/kibana/pull/220310","mergeCommit":{"message":"Upgrade Puppeteer to v24.8.1 (#220310)\n\nThis PR upgrades Puppeteer version to v24.8.1.\n\nBelow is a screenshot to successful download of the new version.\n\n<img width=\"1543\" alt=\"Screenshot 2025-05-07 at 14 31 23\"\nsrc=\"https://github.com/user-attachments/assets/e81d70ae-3df3-4371-ab4d-090fecf93d67\"\n/>\n\n\n---\n\nTested on CI, PNG and PDF reports were successfully generated:\n<img width=\"911\" alt=\"Screenshot 2025-05-09 at 16 55 30\"\nsrc=\"https://github.com/user-attachments/assets/fa65cfe8-5af0-4114-bbb7-b324951e5d41\"\n/>\n\n---\n\nTested on Windows in a VM. PNG and PDF reports were successfully\ngenerated:\n\n<img width=\"1129\" alt=\"Screenshot 2025-05-21 at 20 28 40\"\nsrc=\"https://github.com/user-attachments/assets/9e3c16f2-03d6-4b00-a402-4d007bcd1685\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"8ec7546a561e434cf04082e23dcb7846ce657093"}},"sourceBranch":"main","suggestedTargetBranches":["7.17","8.17","8.18","9.0"],"targetPullRequestStates":[{"branch":"7.17","label":"v7.17.28","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/220310","number":220310,"mergeCommit":{"message":"Upgrade Puppeteer to v24.8.1 (#220310)\n\nThis PR upgrades Puppeteer version to v24.8.1.\n\nBelow is a screenshot to successful download of the new version.\n\n<img width=\"1543\" alt=\"Screenshot 2025-05-07 at 14 31 23\"\nsrc=\"https://github.com/user-attachments/assets/e81d70ae-3df3-4371-ab4d-090fecf93d67\"\n/>\n\n\n---\n\nTested on CI, PNG and PDF reports were successfully generated:\n<img width=\"911\" alt=\"Screenshot 2025-05-09 at 16 55 30\"\nsrc=\"https://github.com/user-attachments/assets/fa65cfe8-5af0-4114-bbb7-b324951e5d41\"\n/>\n\n---\n\nTested on Windows in a VM. PNG and PDF reports were successfully\ngenerated:\n\n<img width=\"1129\" alt=\"Screenshot 2025-05-21 at 20 28 40\"\nsrc=\"https://github.com/user-attachments/assets/9e3c16f2-03d6-4b00-a402-4d007bcd1685\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"8ec7546a561e434cf04082e23dcb7846ce657093"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/221272","number":221272,"state":"MERGED","mergeCommit":{"sha":"4a9b8e451333db25e6d4700817ac86620be60a2d","message":"[8.19] Upgrade Puppeteer to v24.8.1 (#220310) (#221272)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [Upgrade Puppeteer to v24.8.1\n(#220310)](https://github.com/elastic/kibana/pull/220310)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Ersin Erdal <92688503+ersin-erdal@users.noreply.github.com>"}},{"branch":"8.17","label":"v8.17.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
5029a22454
|
[9.0] [ftr] Increase timeout for loading package registry (#222620) (#223012)
# Backport This will backport the following commits from `main` to `9.0`: - [[ftr] Increase timeout for loading package registry (#222620)](https://github.com/elastic/kibana/pull/222620) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jon","email":"jon@elastic.co"},"sourceCommit":{"committedDate":"2025-06-06T14:40:53Z","message":"[ftr] Increase timeout for loading package registry (#222620)\n\nWe've been seeing intermittent timeouts over the last few weeks waiting\nfor package manifests to load.\n\nSuccessful runs are also near 2 minutes, which seems to indicate this\nisn't an issue with the service starting up.","sha":"f6879ad829058846874fd38e2740eab552ec9f79","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","Team:Fleet","backport:prev-major","v9.1.0","v9.0.3"],"title":"[ftr] Increase timeout for loading package registry","number":222620,"url":"https://github.com/elastic/kibana/pull/222620","mergeCommit":{"message":"[ftr] Increase timeout for loading package registry (#222620)\n\nWe've been seeing intermittent timeouts over the last few weeks waiting\nfor package manifests to load.\n\nSuccessful runs are also near 2 minutes, which seems to indicate this\nisn't an issue with the service starting up.","sha":"f6879ad829058846874fd38e2740eab552ec9f79"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222620","number":222620,"mergeCommit":{"message":"[ftr] Increase timeout for loading package registry (#222620)\n\nWe've been seeing intermittent timeouts over the last few weeks waiting\nfor package manifests to load.\n\nSuccessful runs are also near 2 minutes, which seems to indicate this\nisn't an issue with the service starting up.","sha":"f6879ad829058846874fd38e2740eab552ec9f79"}},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jon <jon@elastic.co> |
||
Cristina Amico
|
b9b9b952e7
|
[9.0] [Fleet] Fix UnenrollInactiveAgentsTask to only unenroll agents inactive for longer than unenroll_timeout (#222592) (#222943)
# Backport This will backport the following commits from `main` to `9.0`: - [[Fleet] Fix UnenrollInactiveAgentsTask to only unenroll agents inactive for longer than unenroll_timeout (#222592)](https://github.com/elastic/kibana/pull/222592) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Cristina Amico","email":"criamico@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-06T07:32:57Z","message":"[Fleet] Fix UnenrollInactiveAgentsTask to only unenroll agents inactive for longer than unenroll_timeout (#222592)\n\nFixes https://github.com/elastic/kibana/issues/220660\n\n## Summary\n\nThis bug was found through an SDH. Fixes the query that fetches the\nagents so that actually includes only those agents that have been\ninactive for longer than `unenroll_timeout`.\n\n### Testing\n- Add some inactive agents with the script in\n`x-pack/platform/plugins/shared/fleet/scripts/create_agents`. The fake\nagents are enrolled with an inactive time alraedy set to 5m. The script\nalso creates a policy.\n- In the policy setting, set `unenroll_timeout` to a time that's long\nenough, for instance 10m (600s)\n<img width=\"1351\" alt=\"Screenshot 2025-06-04 at 16 59 38\"\nsrc=\"https://github.com/user-attachments/assets/983e46c2-8b29-4340-a3d8-426fda38d061\"\n/>\n\n- the task runs every 10m so in order to test it, change [the interval\n]( |
||
Tim Sullivan
|
4b7ffddee8
|
[9.0] [SharedUX/Locators] Add limits around legacy locator (#222273) (#222692)
# Backport This will backport the following commits from `main` to `9.0`: - [[SharedUX/Locators] Add limits around legacy locator (#222273)](https://github.com/elastic/kibana/pull/222273) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tim Sullivan","email":"tsullivan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-04T19:55:47Z","message":"[SharedUX/Locators] Add limits around legacy locator (#222273)\n\n## Summary\n\nWe've decided that we want to enforce sanity checks around the \"legacy\"\nlocator and phase out its usage. This PR ensures the legacy locator can\nnot be used from the Reporting plugin.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b96e7c37b83dc3f3ec08860d10413127baf13196","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","v9.1.0","v8.19.0","v7.17.29","v9.0.3","v8.18.3","v8.17.8"],"title":"[SharedUX/Locators] Add limits around legacy locator","number":222273,"url":"https://github.com/elastic/kibana/pull/222273","mergeCommit":{"message":"[SharedUX/Locators] Add limits around legacy locator (#222273)\n\n## Summary\n\nWe've decided that we want to enforce sanity checks around the \"legacy\"\nlocator and phase out its usage. This PR ensures the legacy locator can\nnot be used from the Reporting plugin.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b96e7c37b83dc3f3ec08860d10413127baf13196"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","7.17","9.0","8.18","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222273","number":222273,"mergeCommit":{"message":"[SharedUX/Locators] Add limits around legacy locator (#222273)\n\n## Summary\n\nWe've decided that we want to enforce sanity checks around the \"legacy\"\nlocator and phase out its usage. This PR ensures the legacy locator can\nnot be used from the Reporting plugin.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b96e7c37b83dc3f3ec08860d10413127baf13196"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"7.17","label":"v7.17.29","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
4a32f8827c
|
[9.0] [Chore] Upgrade tar-fs dependency (#222855) (#222937)
# Backport This will backport the following commits from `main` to `9.0`: - [[Chore] Upgrade tar-fs dependency (#222855)](https://github.com/elastic/kibana/pull/222855) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sid","email":"siddharthmantri1@gmail.com"},"sourceCommit":{"committedDate":"2025-06-06T08:23:16Z","message":"[Chore] Upgrade tar-fs dependency (#222855)\n\n## Summary\n\nUpgrade `tar-fs` \n\n- `3.0.4`, `3.0.6`, `3.0.8` -> `3.0.9`\n- `2.1.2` -> `2.1.3`","sha":"1ccb7a6b43d9255cb7bdecc4a86d07d4af6996fe","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Security","release_note:skip","backport:all-open","v9.1.0"],"title":"[Chore] Upgrade tar-fs dependency","number":222855,"url":"https://github.com/elastic/kibana/pull/222855","mergeCommit":{"message":"[Chore] Upgrade tar-fs dependency (#222855)\n\n## Summary\n\nUpgrade `tar-fs` \n\n- `3.0.4`, `3.0.6`, `3.0.8` -> `3.0.9`\n- `2.1.2` -> `2.1.3`","sha":"1ccb7a6b43d9255cb7bdecc4a86d07d4af6996fe"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222855","number":222855,"mergeCommit":{"message":"[Chore] Upgrade tar-fs dependency (#222855)\n\n## Summary\n\nUpgrade `tar-fs` \n\n- `3.0.4`, `3.0.6`, `3.0.8` -> `3.0.9`\n- `2.1.2` -> `2.1.3`","sha":"1ccb7a6b43d9255cb7bdecc4a86d07d4af6996fe"}}]}] BACKPORT--> Co-authored-by: Sid <siddharthmantri1@gmail.com> |
||
|
Brad White
|
ba75f030dc
|
[9.0] Update dependency proxy-from-env to v1.1.0 (main) (#203265) (#222703)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency proxy-from-env to v1.1.0 (main) (#203265)](https://github.com/elastic/kibana/pull/203265) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-04T19:46:45Z","message":"Update dependency proxy-from-env to v1.1.0 (main) (#203265)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [proxy-from-env](https://redirect.github.com/Rob--W/proxy-from-env) |\ndependencies | minor | [`1.0.0` ->\n`1.1.0`](https://renovatebot.com/diffs/npm/proxy-from-env/1.0.0/1.1.0) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>Rob--W/proxy-from-env (proxy-from-env)</summary>\n\n###\n[`v1.1.0`](https://redirect.github.com/Rob--W/proxy-from-env/releases/tag/v1.1.0)\n\n[Compare\nSource](https://redirect.github.com/Rob--W/proxy-from-env/compare/v1.0.0...v1.1.0)\n\n- feat: fetch proxy configuration from NPM if any\n([#​9](https://redirect.github.com/Rob--W/proxy-from-env/issues/9))\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"0bcb4a8fcbd3c911970c3334c731fef4040ce77d","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","v9.1.0"],"title":"Update dependency proxy-from-env to v1.1.0 (main)","number":203265,"url":"https://github.com/elastic/kibana/pull/203265","mergeCommit":{"message":"Update dependency proxy-from-env to v1.1.0 (main) (#203265)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [proxy-from-env](https://redirect.github.com/Rob--W/proxy-from-env) |\ndependencies | minor | [`1.0.0` ->\n`1.1.0`](https://renovatebot.com/diffs/npm/proxy-from-env/1.0.0/1.1.0) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>Rob--W/proxy-from-env (proxy-from-env)</summary>\n\n###\n[`v1.1.0`](https://redirect.github.com/Rob--W/proxy-from-env/releases/tag/v1.1.0)\n\n[Compare\nSource](https://redirect.github.com/Rob--W/proxy-from-env/compare/v1.0.0...v1.1.0)\n\n- feat: fetch proxy configuration from NPM if any\n([#​9](https://redirect.github.com/Rob--W/proxy-from-env/issues/9))\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"0bcb4a8fcbd3c911970c3334c731fef4040ce77d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203265","number":203265,"mergeCommit":{"message":"Update dependency proxy-from-env to v1.1.0 (main) (#203265)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [proxy-from-env](https://redirect.github.com/Rob--W/proxy-from-env) |\ndependencies | minor | [`1.0.0` ->\n`1.1.0`](https://renovatebot.com/diffs/npm/proxy-from-env/1.0.0/1.1.0) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>Rob--W/proxy-from-env (proxy-from-env)</summary>\n\n###\n[`v1.1.0`](https://redirect.github.com/Rob--W/proxy-from-env/releases/tag/v1.1.0)\n\n[Compare\nSource](https://redirect.github.com/Rob--W/proxy-from-env/compare/v1.0.0...v1.1.0)\n\n- feat: fetch proxy configuration from NPM if any\n([#​9](https://redirect.github.com/Rob--W/proxy-from-env/issues/9))\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"0bcb4a8fcbd3c911970c3334c731fef4040ce77d"}},{"url":"https://github.com/elastic/kibana/pull/222669","number":222669,"branch":"8.19","state":"OPEN"}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
Brad White
|
dfc66bf0b1
|
Revert "[9.0] Update dependency sort-package-json to v3 (main) (#203289) (#222710)"
This reverts commit
|
||
|
Brad White
|
07fae5227e
|
[9.0] Update dependency sort-package-json to v3 (main) (#203289) (#222710)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency sort-package-json to v3 (main) (#203289)](https://github.com/elastic/kibana/pull/203289) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-04T19:39:39Z","message":"Update dependency sort-package-json to v3 (main) (#203289)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n|\n[sort-package-json](https://redirect.github.com/keithamus/sort-package-json)\n| devDependencies | major | [`^1.53.1` ->\n`^3.2.1`](https://renovatebot.com/diffs/npm/sort-package-json/1.53.1/3.2.1)\n|\n\n---\n\n### Release Notes\n\n<details>\n<summary>keithamus/sort-package-json (sort-package-json)</summary>\n\n###\n[`v3.2.1`](https://redirect.github.com/keithamus/sort-package-json/releases/tag/v3.2.1)\n\n[Compare\nSource](https://redirect.github.com/keithamus/sort-package-json/compare/v3.2.0...v3.2.1)\n\n##### Bug Fixes\n\n- prevent sorting when npm-run-all2 is used\n([#​361]( |
||
|
Kibana Machine
|
cb8bda122c
|
[9.0] [Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691) (#222893)
# Backport This will backport the following commits from `main` to `9.0`: - [[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)](https://github.com/elastic/kibana/pull/222691) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ryland Herrick","email":"ryalnd@gmail.com"},"sourceCommit":{"committedDate":"2025-06-05T20:05:06Z","message":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)\n\n## Summary\n\nThis test has [failed a few times\nrecently](https://github.com/elastic/kibana/issues/219112) with a\n`version_conflict_engine_exception`, stating explicitly that the\ndocuments we're trying to load already exist in elasticsearch. In one\ncase the reason was obvious (the suite was retried), but in another it\nwas not clear why the data was there to cause this exception.\n\nRegardless, adding this sanity check (deleting all the alerts) should\nensure that this behavior does not recur.\n\nCloses #219112.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329))\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7fe71b3f4ee4b68e22bb424aa7b8ccc2e3c40f1a","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","Team:Detection Engine","8.19 candidate","v9.1.0"],"title":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive","number":222691,"url":"https://github.com/elastic/kibana/pull/222691","mergeCommit":{"message":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)\n\n## Summary\n\nThis test has [failed a few times\nrecently](https://github.com/elastic/kibana/issues/219112) with a\n`version_conflict_engine_exception`, stating explicitly that the\ndocuments we're trying to load already exist in elasticsearch. In one\ncase the reason was obvious (the suite was retried), but in another it\nwas not clear why the data was there to cause this exception.\n\nRegardless, adding this sanity check (deleting all the alerts) should\nensure that this behavior does not recur.\n\nCloses #219112.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329))\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7fe71b3f4ee4b68e22bb424aa7b8ccc2e3c40f1a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222691","number":222691,"mergeCommit":{"message":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)\n\n## Summary\n\nThis test has [failed a few times\nrecently](https://github.com/elastic/kibana/issues/219112) with a\n`version_conflict_engine_exception`, stating explicitly that the\ndocuments we're trying to load already exist in elasticsearch. In one\ncase the reason was obvious (the suite was retried), but in another it\nwas not clear why the data was there to cause this exception.\n\nRegardless, adding this sanity check (deleting all the alerts) should\nensure that this behavior does not recur.\n\nCloses #219112.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329))\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7fe71b3f4ee4b68e22bb424aa7b8ccc2e3c40f1a"}}]}] BACKPORT--> Co-authored-by: Ryland Herrick <ryalnd@gmail.com> |
||
|
Kibana Machine
|
99a90a3ee3
|
[9.0] [Obs AI Assistant] Update AI connector description for the pre-configured connector (#221860) (#222886)
# Backport This will backport the following commits from `main` to `9.0`: - [[Obs AI Assistant] Update AI connector description for the pre-configured connector (#221860)](https://github.com/elastic/kibana/pull/221860) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Viduni Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2025-06-05T19:48:29Z","message":"[Obs AI Assistant] Update AI connector description for the pre-configured connector (#221860)\n\n## Summary\n\nThe AI Connector is being used to send requests to third party LLM\nproviders as well as the Elastic-Managed LLM.\nTherefore, the description was updated as `Use the Elastic Managed LLM\nfor your chat and RAG use cases.` only when the AI Connector is\npre-configured.\n\n## If pre-configured:\n\n<img width=\"714\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/6f4195e5-b8f0-4b15-a63a-bde012ed1d56\"\n/>\n\n\n## If **not** pre-configured:\n\n<img width=\"717\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/59fb691d-0e46-4967-85f7-f2e51931fee9\"\n/>\n\n<img width=\"707\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/0dc840ec-78f8-48e3-bc58-90f58af046b4\"\n/>\n\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"61a44661060150673e304835d430c5ac0b9a2e5c","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Obs AI Assistant","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[Obs AI Assistant] Update AI connector description for the pre-configured connector","number":221860,"url":"https://github.com/elastic/kibana/pull/221860","mergeCommit":{"message":"[Obs AI Assistant] Update AI connector description for the pre-configured connector (#221860)\n\n## Summary\n\nThe AI Connector is being used to send requests to third party LLM\nproviders as well as the Elastic-Managed LLM.\nTherefore, the description was updated as `Use the Elastic Managed LLM\nfor your chat and RAG use cases.` only when the AI Connector is\npre-configured.\n\n## If pre-configured:\n\n<img width=\"714\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/6f4195e5-b8f0-4b15-a63a-bde012ed1d56\"\n/>\n\n\n## If **not** pre-configured:\n\n<img width=\"717\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/59fb691d-0e46-4967-85f7-f2e51931fee9\"\n/>\n\n<img width=\"707\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/0dc840ec-78f8-48e3-bc58-90f58af046b4\"\n/>\n\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"61a44661060150673e304835d430c5ac0b9a2e5c"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/221860","number":221860,"mergeCommit":{"message":"[Obs AI Assistant] Update AI connector description for the pre-configured connector (#221860)\n\n## Summary\n\nThe AI Connector is being used to send requests to third party LLM\nproviders as well as the Elastic-Managed LLM.\nTherefore, the description was updated as `Use the Elastic Managed LLM\nfor your chat and RAG use cases.` only when the AI Connector is\npre-configured.\n\n## If pre-configured:\n\n<img width=\"714\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/6f4195e5-b8f0-4b15-a63a-bde012ed1d56\"\n/>\n\n\n## If **not** pre-configured:\n\n<img width=\"717\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/59fb691d-0e46-4967-85f7-f2e51931fee9\"\n/>\n\n<img width=\"707\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/0dc840ec-78f8-48e3-bc58-90f58af046b4\"\n/>\n\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"61a44661060150673e304835d430c5ac0b9a2e5c"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co> |
||
|
Kibana Machine
|
08e3404c94
|
[9.0] Update picomatch to v4 (main) (#203316) (#222877)
# Backport This will backport the following commits from `main` to `9.0`: - [Update picomatch to v4 (main) (#203316)](https://github.com/elastic/kibana/pull/203316) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-05T19:16:01Z","message":"Update picomatch to v4 (main) (#203316)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n|\n[@types/picomatch](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/picomatch)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/picomatch))\n| devDependencies | major | [`^2.3.0` ->\n`^4.0.0`](https://renovatebot.com/diffs/npm/@types%2fpicomatch/2.3.0/4.0.0)\n|\n| [picomatch](https://redirect.github.com/micromatch/picomatch) |\ndevDependencies | major | [`^2.3.1` ->\n`^4.0.2`](https://renovatebot.com/diffs/npm/picomatch/2.3.1/4.0.2) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>micromatch/picomatch (picomatch)</summary>\n\n###\n[`v4.0.2`]( |
||
|
Kibana Machine
|
9c738eccd7
|
[9.0] Update postcss (main) (#203261) (#222878)
# Backport This will backport the following commits from `main` to `9.0`: - [Update postcss (main) (#203261)](https://github.com/elastic/kibana/pull/203261) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-05T19:16:54Z","message":"Update postcss (main) (#203261)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change | Pending |\n|---|---|---|---|---|\n| [postcss](https://postcss.org/)\n([source](https://redirect.github.com/postcss/postcss)) |\ndevDependencies | minor | [`^8.4.31` ->\n`^8.5.3`](https://renovatebot.com/diffs/npm/postcss/8.4.49/8.5.3) |\n`8.5.4` |\n| [postcss-scss](https://redirect.github.com/postcss/postcss-scss) |\ndevDependencies | patch | [`^4.0.4` ->\n`^4.0.9`](https://renovatebot.com/diffs/npm/postcss-scss/4.0.4/4.0.9) |\n|\n\n---\n\n### Release Notes\n\n<details>\n<summary>postcss/postcss (postcss)</summary>\n\n###\n[`v8.5.3`](https://redirect.github.com/postcss/postcss/blob/HEAD/CHANGELOG.md#853)\n\n[Compare\nSource](https://redirect.github.com/postcss/postcss/compare/8.5.2...8.5.3)\n\n- Added more details to `Unknown word` error (by\n[@​hiepxanh](https://redirect.github.com/hiepxanh)).\n- Fixed types (by\n[@​romainmenke](https://redirect.github.com/romainmenke)).\n- Fixed docs (by\n[@​catnipan](https://redirect.github.com/catnipan)).\n\n###\n[`v8.5.2`](https://redirect.github.com/postcss/postcss/blob/HEAD/CHANGELOG.md#852)\n\n[Compare\nSource](https://redirect.github.com/postcss/postcss/compare/8.5.1...8.5.2)\n\n- Fixed end position of rules with semicolon (by\n[@​romainmenke](https://redirect.github.com/romainmenke)).\n\n###\n[`v8.5.1`](https://redirect.github.com/postcss/postcss/blob/HEAD/CHANGELOG.md#851)\n\n[Compare\nSource](https://redirect.github.com/postcss/postcss/compare/8.5.0...8.5.1)\n\n- Fixed backwards compatibility for complex cases (by\n[@​romainmenke](https://redirect.github.com/romainmenke)).\n\n###\n[`v8.5.0`](https://redirect.github.com/postcss/postcss/releases/tag/8.5.0):\n8.5 “Duke Alloces”\n\n[Compare\nSource]( |
||
|
Kibana Machine
|
752199a6ad
|
[9.0] Connectors List: ensure on deletion errors are handled (#221958) (#222864)
# Backport This will backport the following commits from `main` to `9.0`: - [Connectors List: ensure on deletion errors are handled (#221958)](https://github.com/elastic/kibana/pull/221958) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Melissa Alvarez","email":"melissa.alvarez@elastic.co"},"sourceCommit":{"committedDate":"2025-06-05T17:03:04Z","message":"Connectors List: ensure on deletion errors are handled (#221958)\n\n## Summary\n\nFixes |
||
elastic-vault-github-plugin-prod[bot]
|
e57c58d0a8
|
[9.0] Sync bundled packages with Package Storage (#222295)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2873 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
de11fdf3d3
|
[9.0] [APM] Fix pagination not working on Service Inventory page when progressive loading is enabled (#220514) (#222810)
# Backport This will backport the following commits from `main` to `9.0`: - [[APM] Fix pagination not working on Service Inventory page when progressive loading is enabled (#220514)](https://github.com/elastic/kibana/pull/220514) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Milosz Marcinkowski","email":"38698566+miloszmarcinkowski@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-05T12:56:11Z","message":"[APM] Fix pagination not working on Service Inventory page when progressive loading is enabled (#220514)\n\n## Summary\n\nWhile the `observability:apmProgressiveLoading` setting is enabled,\npagination on the Service Inventory page does not work properly. This\nhappens due to implementation of\n[`useProgressiveFetcher`](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/apm/public/hooks/use_progressive_fetcher.tsx),\nwhich retains the\n[`sampled`](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/apm/public/hooks/use_progressive_fetcher.tsx#L92)\ndata between component re-renders instead of returning the already\nloaded\n[`unsampled`](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/apm/public/hooks/use_progressive_fetcher.tsx#L105)\ndata. As a result, pagination receives two sets of data sequentially.\nThis behavior causes the page index to revert to the last available\nindex in `sampled` results, preventing users from paginating through the\nfull length of `unsampled` data.\n\nTo avoid the issue, we implemented `isLoading` check in pagination to\nprevent index from reverting while `unsampled` data is being loaded.\n\nBefore:\n\n\n |
||
Ying Mao
|
828470d592
|
[9.0] [Response Ops][Alerting] Fixing issue with setting cancelAlertsOnRuleTimeout=false in kibana config (#222263) (#222799)
# Backport This will backport the following commits from `main` to `9.0`: - [[Response Ops][Alerting] Fixing issue with setting `cancelAlertsOnRuleTimeout=false` in kibana config (#222263)](https://github.com/elastic/kibana/pull/222263) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ying Mao","email":"ying.mao@elastic.co"},"sourceCommit":{"committedDate":"2025-06-05T01:58:47Z","message":"[Response Ops][Alerting] Fixing issue with setting `cancelAlertsOnRuleTimeout=false` in kibana config (#222263)\n\nFixing https://github.com/elastic/kibana/issues/222127\n\n## Summary\n\nFixes issue that causes Kibana to bootloop when\n`xpack.alerting.cancelAlertsOnRuleTimeout` is set to `false` in the\nkibana config.\n\nMoves the check for incompatible `cancelAlertsOnRuleTimeout` and\n`autoRecoverAlerts` rule type config to the plugin setup code because we\nmutate some of these values before registering. So now the check\nactually checks the values set by the rule type in the code. Then we\nproceed with merging some of these values with the Kibana config.\nBecause there are issues with lifecycle rule types when\n`cancelAlertsOnRuleTimeout` is set to false, we log a warning when we\nsee this override in the config and ignore the setting for lifecycle\nrule types. Persistent rule types (detection rules) will still respect\nthis config override if set.\n\nThere will be a followup issue to deprecate this config for 9.10 and\n8.19. This PR is to address the immediate bug.\n\n## To Verify\n1. Set `xpack.alerting.cancelAlertsOnRuleTimeout: false` in the Kibana\nconfig and start Kibana.\n2. Verify Kibana starts up correctly with no errors.\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"69690c9bc58a1114ea7b56782dddae3c0b9caf46","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Alerting","Team:ResponseOps","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[Response Ops][Alerting] Fixing issue with setting `cancelAlertsOnRuleTimeout=false` in kibana config","number":222263,"url":"https://github.com/elastic/kibana/pull/222263","mergeCommit":{"message":"[Response Ops][Alerting] Fixing issue with setting `cancelAlertsOnRuleTimeout=false` in kibana config (#222263)\n\nFixing https://github.com/elastic/kibana/issues/222127\n\n## Summary\n\nFixes issue that causes Kibana to bootloop when\n`xpack.alerting.cancelAlertsOnRuleTimeout` is set to `false` in the\nkibana config.\n\nMoves the check for incompatible `cancelAlertsOnRuleTimeout` and\n`autoRecoverAlerts` rule type config to the plugin setup code because we\nmutate some of these values before registering. So now the check\nactually checks the values set by the rule type in the code. Then we\nproceed with merging some of these values with the Kibana config.\nBecause there are issues with lifecycle rule types when\n`cancelAlertsOnRuleTimeout` is set to false, we log a warning when we\nsee this override in the config and ignore the setting for lifecycle\nrule types. Persistent rule types (detection rules) will still respect\nthis config override if set.\n\nThere will be a followup issue to deprecate this config for 9.10 and\n8.19. This PR is to address the immediate bug.\n\n## To Verify\n1. Set `xpack.alerting.cancelAlertsOnRuleTimeout: false` in the Kibana\nconfig and start Kibana.\n2. Verify Kibana starts up correctly with no errors.\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"69690c9bc58a1114ea7b56782dddae3c0b9caf46"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222263","number":222263,"mergeCommit":{"message":"[Response Ops][Alerting] Fixing issue with setting `cancelAlertsOnRuleTimeout=false` in kibana config (#222263)\n\nFixing https://github.com/elastic/kibana/issues/222127\n\n## Summary\n\nFixes issue that causes Kibana to bootloop when\n`xpack.alerting.cancelAlertsOnRuleTimeout` is set to `false` in the\nkibana config.\n\nMoves the check for incompatible `cancelAlertsOnRuleTimeout` and\n`autoRecoverAlerts` rule type config to the plugin setup code because we\nmutate some of these values before registering. So now the check\nactually checks the values set by the rule type in the code. Then we\nproceed with merging some of these values with the Kibana config.\nBecause there are issues with lifecycle rule types when\n`cancelAlertsOnRuleTimeout` is set to false, we log a warning when we\nsee this override in the config and ignore the setting for lifecycle\nrule types. Persistent rule types (detection rules) will still respect\nthis config override if set.\n\nThere will be a followup issue to deprecate this config for 9.10 and\n8.19. This PR is to address the immediate bug.\n\n## To Verify\n1. Set `xpack.alerting.cancelAlertsOnRuleTimeout: false` in the Kibana\nconfig and start Kibana.\n2. Verify Kibana starts up correctly with no errors.\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"69690c9bc58a1114ea7b56782dddae3c0b9caf46"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/222729","number":222729,"state":"OPEN"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
4c661fed44
|
[9.0] [Fleet] Fix agent policy batch processing in UnenrollInactiveAgentsTask (#210216) (#222751)
# Backport This will backport the following commits from `main` to `9.0`: - [[Fleet] Fix agent policy batch processing in UnenrollInactiveAgentsTask (#210216)](https://github.com/elastic/kibana/pull/210216) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jill Guyonnet","email":"jill.guyonnet@elastic.co"},"sourceCommit":{"committedDate":"2025-02-11T09:18:36Z","message":"[Fleet] Fix agent policy batch processing in UnenrollInactiveAgentsTask (#210216)\n\n## Summary\r\n\r\nWhile working on https://github.com/elastic/ingest-dev/issues/4722 I\r\nidentified an issue in `UnenrollInactiveAgentsTask` in the batch\r\nprocessing of agent policies. As it is, the task ends if no inactive\r\nagents were found for an agent policy batch, regardless of whether there\r\ncould be inactive agents assigned to policies in further batches. This\r\nmeans that for stacks with over 500 agent policies, it could be possible\r\nthat some inactive agents never get unenrolled (or at least not\r\npredictably, since that depends on the order in which the agent policy\r\nfetcher returns them).\r\n\r\nI added a unit test to test this and also fixed a couple of other unit\r\ntests.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nLow probability of affecting automatic unenrolling of inactive agents on\r\nstacks with over 500 agent policies.\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f50c2c19035d6518d44ab1cb4553bec32fafb243","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:all-open","v9.1.0"],"title":"[Fleet] Fix agent policy batch processing in UnenrollInactiveAgentsTask","number":210216,"url":"https://github.com/elastic/kibana/pull/210216","mergeCommit":{"message":"[Fleet] Fix agent policy batch processing in UnenrollInactiveAgentsTask (#210216)\n\n## Summary\r\n\r\nWhile working on https://github.com/elastic/ingest-dev/issues/4722 I\r\nidentified an issue in `UnenrollInactiveAgentsTask` in the batch\r\nprocessing of agent policies. As it is, the task ends if no inactive\r\nagents were found for an agent policy batch, regardless of whether there\r\ncould be inactive agents assigned to policies in further batches. This\r\nmeans that for stacks with over 500 agent policies, it could be possible\r\nthat some inactive agents never get unenrolled (or at least not\r\npredictably, since that depends on the order in which the agent policy\r\nfetcher returns them).\r\n\r\nI added a unit test to test this and also fixed a couple of other unit\r\ntests.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nLow probability of affecting automatic unenrolling of inactive agents on\r\nstacks with over 500 agent policies.\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f50c2c19035d6518d44ab1cb4553bec32fafb243"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210216","number":210216,"mergeCommit":{"message":"[Fleet] Fix agent policy batch processing in UnenrollInactiveAgentsTask (#210216)\n\n## Summary\r\n\r\nWhile working on https://github.com/elastic/ingest-dev/issues/4722 I\r\nidentified an issue in `UnenrollInactiveAgentsTask` in the batch\r\nprocessing of agent policies. As it is, the task ends if no inactive\r\nagents were found for an agent policy batch, regardless of whether there\r\ncould be inactive agents assigned to policies in further batches. This\r\nmeans that for stacks with over 500 agent policies, it could be possible\r\nthat some inactive agents never get unenrolled (or at least not\r\npredictably, since that depends on the order in which the agent policy\r\nfetcher returns them).\r\n\r\nI added a unit test to test this and also fixed a couple of other unit\r\ntests.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### Identify risks\r\n\r\nLow probability of affecting automatic unenrolling of inactive agents on\r\nstacks with over 500 agent policies.\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f50c2c19035d6518d44ab1cb4553bec32fafb243"}}]}] BACKPORT--> Co-authored-by: Jill Guyonnet <jill.guyonnet@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
62e5afabbe
|
[9.0] [ML] File upload: Fixing adding additional field when pipeline is blank (#222775) (#222803)
# Backport This will backport the following commits from `main` to `9.0`: - [[ML] File upload: Fixing adding additional field when pipeline is blank (#222775)](https://github.com/elastic/kibana/pull/222775) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"James Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2025-06-05T11:53:20Z","message":"[ML] File upload: Fixing adding additional field when pipeline is blank (#222775)\n\nIf no pipeline has been generated, when adding an additional field like\nsemantic text or geo point, the empty pipeline is populated before\nadding the processor\n\nFixes https://github.com/elastic/kibana/issues/222742","sha":"b13fe6a426acbd6226a73a08036dec5b2254bdd2","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:File and Index Data Viz","Feature:File Upload","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[ML] File upload: Fixing adding additional field when pipeline is blank","number":222775,"url":"https://github.com/elastic/kibana/pull/222775","mergeCommit":{"message":"[ML] File upload: Fixing adding additional field when pipeline is blank (#222775)\n\nIf no pipeline has been generated, when adding an additional field like\nsemantic text or geo point, the empty pipeline is populated before\nadding the processor\n\nFixes https://github.com/elastic/kibana/issues/222742","sha":"b13fe6a426acbd6226a73a08036dec5b2254bdd2"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222775","number":222775,"mergeCommit":{"message":"[ML] File upload: Fixing adding additional field when pipeline is blank (#222775)\n\nIf no pipeline has been generated, when adding an additional field like\nsemantic text or geo point, the empty pipeline is populated before\nadding the processor\n\nFixes https://github.com/elastic/kibana/issues/222742","sha":"b13fe6a426acbd6226a73a08036dec5b2254bdd2"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co> |
||
Christos Nasikas
|
aa41588ee2
|
[9.0] [Cases] Extend ownership of cases (#222550) (#222771)
# Backport This will backport the following commits from `main` to `9.0`: - [[Cases] Extend ownership of cases (#222550)](https://github.com/elastic/kibana/pull/222550) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2025-06-05T08:42:19Z","message":"[Cases] Extend ownership of cases (#222550)\n\n## Summary\n\nThis PR adds the @elastic/kibana-cases team as co-owner of the cases\ncode.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b135d7007343b353d857969b1952018b916517e0","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Feature:Cases","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3","v8.17.8"],"title":"[Cases] Extend ownership of cases","number":222550,"url":"https://github.com/elastic/kibana/pull/222550","mergeCommit":{"message":"[Cases] Extend ownership of cases (#222550)\n\n## Summary\n\nThis PR adds the @elastic/kibana-cases team as co-owner of the cases\ncode.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b135d7007343b353d857969b1952018b916517e0"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222550","number":222550,"mergeCommit":{"message":"[Cases] Extend ownership of cases (#222550)\n\n## Summary\n\nThis PR adds the @elastic/kibana-cases team as co-owner of the cases\ncode.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b135d7007343b353d857969b1952018b916517e0"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/222770","number":222770,"state":"OPEN"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
e4c562e42f
|
[9.0] Update elastic-managed-llm.md (#222714) (#222744)
# Backport This will backport the following commits from `main` to `9.0`: - [Update elastic-managed-llm.md (#222714)](https://github.com/elastic/kibana/pull/222714) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Shubha Anjur Tupil","email":"at.shubha@gmail.com"},"sourceCommit":{"committedDate":"2025-06-05T07:34:56Z","message":"Update elastic-managed-llm.md (#222714)\n\nChanging optimized to vetted\n\n## Summary\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"e4b3ecb8e9ef9e265ec6b63432aaa598fa3bdb3b","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","docs","DevDocs","documentation","backport:version","v9.1.0","v9.0.3"],"title":"Update elastic-managed-llm.md","number":222714,"url":"https://github.com/elastic/kibana/pull/222714","mergeCommit":{"message":"Update elastic-managed-llm.md (#222714)\n\nChanging optimized to vetted\n\n## Summary\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"e4b3ecb8e9ef9e265ec6b63432aaa598fa3bdb3b"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222714","number":222714,"mergeCommit":{"message":"Update elastic-managed-llm.md (#222714)\n\nChanging optimized to vetted\n\n## Summary\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"e4b3ecb8e9ef9e265ec6b63432aaa598fa3bdb3b"}},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Shubha Anjur Tupil <at.shubha@gmail.com> |