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
|
598743f3f1
|
[9.0] Upgrade openpgp to 5.11.3 (#221198) (#221374)
# Backport This will backport the following commits from `main` to `9.0`: - [Upgrade openpgp to 5.11.3 (#221198)](https://github.com/elastic/kibana/pull/221198) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Kurt","email":"kc13greiner@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-05-23T13:22:40Z","message":"Upgrade openpgp to 5.11.3 (#221198)\n\n## Summary\n\nUpgrade `openpgp` from `5.10.1` to `5.11.3`\n\n## Changelog\nhttps://github.com/openpgpjs/openpgpjs/compare/v5.10.1..v5.11.3\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7ee553e59306e26934aac076758f720600da170a","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":"Upgrade openpgp to 5.11.3","number":221198,"url":"https://github.com/elastic/kibana/pull/221198","mergeCommit":{"message":"Upgrade openpgp to 5.11.3 (#221198)\n\n## Summary\n\nUpgrade `openpgp` from `5.10.1` to `5.11.3`\n\n## Changelog\nhttps://github.com/openpgpjs/openpgpjs/compare/v5.10.1..v5.11.3\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7ee553e59306e26934aac076758f720600da170a"}},"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/221198","number":221198,"mergeCommit":{"message":"Upgrade openpgp to 5.11.3 (#221198)\n\n## Summary\n\nUpgrade `openpgp` from `5.10.1` to `5.11.3`\n\n## Changelog\nhttps://github.com/openpgpjs/openpgpjs/compare/v5.10.1..v5.11.3\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7ee553e59306e26934aac076758f720600da170a"}}]}] BACKPORT--> Co-authored-by: Kurt <kc13greiner@users.noreply.github.com> |
||
|
Kibana Machine
|
9e1ce93938
|
[9.0] [Entity Analytics] [bug-fix] Do not abort risk score search request (#219858) (#220209)
# Backport This will backport the following commits from `main` to `9.0`: - [[Entity Analytics] [bug-fix] Do not abort risk score search request (#219858)](https://github.com/elastic/kibana/pull/219858) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mark Hopkin","email":"mark.hopkin@elastic.co"},"sourceCommit":{"committedDate":"2025-05-06T09:04:02Z","message":"[Entity Analytics] [bug-fix] Do not abort risk score search request (#219858)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/219490\n\nFix an error toast appearing when changing an entities asset criticality\nfrom the entity flyout. See video on issue above for more detail.\n\nWe were seeing the risk score request be aborted and this was creating\nthe error toast.\n\n- Do not toast if an abort error is thrown\n- Do not abort the request unless the component receives `skip:true`\n\n### Test Steps\n\n1. Use the security document generator `yarn start entity-store` command\nto load entities and enable the risk engine\n2. Enable the entity store\n3. from the entities table open the entity flyout\n4. Assign/change asset criticality\n5. observe the error is not present\n\n### Why did the bug happen?\nThe risk score component stops rendering because the conditions for\naborting and searching differ. So we aborted the HTTP call but didn't\nsearch again.\n\nI believe this PR https://github.com/elastic/kibana/pull/201810\nintroduced the bug\n\n---------\n\nCo-authored-by: machadoum <pablo.nevesmachado@elastic.co>","sha":"64d20bb00b9e314c9abe257c8453c2684bccc0a3","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","backport:prev-minor","Team:Entity Analytics","v9.1.0","v9.0.2"],"title":"[Entity Analytics] [bug-fix] Do not abort risk score search request","number":219858,"url":"https://github.com/elastic/kibana/pull/219858","mergeCommit":{"message":"[Entity Analytics] [bug-fix] Do not abort risk score search request (#219858)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/219490\n\nFix an error toast appearing when changing an entities asset criticality\nfrom the entity flyout. See video on issue above for more detail.\n\nWe were seeing the risk score request be aborted and this was creating\nthe error toast.\n\n- Do not toast if an abort error is thrown\n- Do not abort the request unless the component receives `skip:true`\n\n### Test Steps\n\n1. Use the security document generator `yarn start entity-store` command\nto load entities and enable the risk engine\n2. Enable the entity store\n3. from the entities table open the entity flyout\n4. Assign/change asset criticality\n5. observe the error is not present\n\n### Why did the bug happen?\nThe risk score component stops rendering because the conditions for\naborting and searching differ. So we aborted the HTTP call but didn't\nsearch again.\n\nI believe this PR https://github.com/elastic/kibana/pull/201810\nintroduced the bug\n\n---------\n\nCo-authored-by: machadoum <pablo.nevesmachado@elastic.co>","sha":"64d20bb00b9e314c9abe257c8453c2684bccc0a3"}},"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/219858","number":219858,"mergeCommit":{"message":"[Entity Analytics] [bug-fix] Do not abort risk score search request (#219858)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/219490\n\nFix an error toast appearing when changing an entities asset criticality\nfrom the entity flyout. See video on issue above for more detail.\n\nWe were seeing the risk score request be aborted and this was creating\nthe error toast.\n\n- Do not toast if an abort error is thrown\n- Do not abort the request unless the component receives `skip:true`\n\n### Test Steps\n\n1. Use the security document generator `yarn start entity-store` command\nto load entities and enable the risk engine\n2. Enable the entity store\n3. from the entities table open the entity flyout\n4. Assign/change asset criticality\n5. observe the error is not present\n\n### Why did the bug happen?\nThe risk score component stops rendering because the conditions for\naborting and searching differ. So we aborted the HTTP call but didn't\nsearch again.\n\nI believe this PR https://github.com/elastic/kibana/pull/201810\nintroduced the bug\n\n---------\n\nCo-authored-by: machadoum <pablo.nevesmachado@elastic.co>","sha":"64d20bb00b9e314c9abe257c8453c2684bccc0a3"}},{"branch":"9.0","label":"v9.0.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Mark Hopkin <mark.hopkin@elastic.co> Co-authored-by: machadoum <pablo.nevesmachado@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
Kurt
|
9f88e1552f
|
[9.0] Upgrading backport to v10 (#221183) (#221278)
# Backport This will backport the following commits from `main` to `9.0`: - [Upgrading backport to v10 (#221183)](https://github.com/elastic/kibana/pull/221183) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Kurt","email":"kc13greiner@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-05-22T12:21:13Z","message":"Upgrading backport to v10 (#221183)\n\n## Summary\n\nUpgrading `backport` from `^9.6.6` to `10.0.0`\n\nChangelog: https://github.com/sorenlouv/backport/releases\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5e80739097de1c401d13f60ed7a4bb1aaed6d1e3","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":"Upgrading backport to v10","number":221183,"url":"https://github.com/elastic/kibana/pull/221183","mergeCommit":{"message":"Upgrading backport to v10 (#221183)\n\n## Summary\n\nUpgrading `backport` from `^9.6.6` to `10.0.0`\n\nChangelog: https://github.com/sorenlouv/backport/releases\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5e80739097de1c401d13f60ed7a4bb1aaed6d1e3"}},"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/221183","number":221183,"mergeCommit":{"message":"Upgrading backport to v10 (#221183)\n\n## Summary\n\nUpgrading `backport` from `^9.6.6` to `10.0.0`\n\nChangelog: https://github.com/sorenlouv/backport/releases\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5e80739097de1c401d13f60ed7a4bb1aaed6d1e3"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
8931758b3f
|
[9.0] [ci] Increase base disk to 80gb (#221256) (#221323)
# Backport This will backport the following commits from `main` to `9.0`: - [[ci] Increase base disk to 80gb (#221256)](https://github.com/elastic/kibana/pull/221256) <!--- 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-05-22T13:12:18Z","message":"[ci] Increase base disk to 80gb (#221256)","sha":"6fc1e4a488d28fb55b56b565f455a66bf860bac8","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","skip-ci","backport:version","v9.1.0","v9.0.2"],"title":"[ci] Increase base disk to 80gb","number":221256,"url":"https://github.com/elastic/kibana/pull/221256","mergeCommit":{"message":"[ci] Increase base disk to 80gb (#221256)","sha":"6fc1e4a488d28fb55b56b565f455a66bf860bac8"}},"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/221256","number":221256,"mergeCommit":{"message":"[ci] Increase base disk to 80gb (#221256)","sha":"6fc1e4a488d28fb55b56b565f455a66bf860bac8"}},{"branch":"9.0","label":"v9.0.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"url":"https://github.com/elastic/kibana/pull/221258","number":221258,"branch":"8.18","state":"MERGED","mergeCommit":{"sha":"79ad88bb196b42a5a50a80fc47dc8f811a51dcf6","message":"[8.18] [ci] Increase base disk to 80gb (#221256) (#221258)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[ci] Increase base disk to 80gb\n(#221256)](https://github.com/elastic/kibana/pull/221256)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Jon <jon@elastic.co>"}},{"url":"https://github.com/elastic/kibana/pull/221259","number":221259,"branch":"8.19","state":"MERGED","mergeCommit":{"sha":"1a3593f1812ad29ff2537367e83f207fa5e9267f","message":"[8.19] [ci] Increase base disk to 80gb (#221256) (#221259)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [[ci] Increase base disk to 80gb\n(#221256)](https://github.com/elastic/kibana/pull/221256)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Jon <jon@elastic.co>"}}]}] BACKPORT--> Co-authored-by: Jon <jon@elastic.co> |
||
|
Kibana Machine
|
1a9703e6bc
|
[9.0] [Theme] load correct system color mode at bootstrap (#218417) (#221249)
# Backport This will backport the following commits from `main` to `9.0`: - [[Theme] load correct system color mode at bootstrap (#218417)](https://github.com/elastic/kibana/pull/218417) <!--- 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-05-22T10:34:17Z","message":"[Theme] load correct system color mode at bootstrap (#218417)\n\n## Summary\n\nThis PR fixes the theme bootstrap when the color mode is configured as\n`system`.\n\nIt uses the `prefers-color-scheme: dark` media match to check if the\npreferred color mode is dark or light and adjust the theme accordingly.\n\nBefore that PR, the `system` color mode caused kibana to bootstrap with\na light mode (even with a dark OS). Only a subsequent event/check will\nupdate the `__kbnThemeTag__` to the correct theme. But at that point the\nSCSS part of elastic-charts is already loaded with the default light\ntheme tokens (the chart theme is loaded from `src/core/public/index.ts`)\n\nWe can probably also find a way to load the chart theme in a subsequent\nstage, when the theme is resolved elsewhere, but the general behaviour\nis anyway buggy: we are loading the kibana application with a wrong\ntheme and only after loading more logic we then switch to the actual\ntheme and update the `__kbnThemeTag__` global.\n\nfix https://github.com/elastic/kibana/issues/210951\n\n\nTo test the before/after:\n- in `main` select the `system` color mode, switch to a Dark mode in\nyour OS, open Discover and apply a breakdown to the histogram: the\nlegend text is too dark and invisible\n- open this pr, select `system` color mode and do the same steps, the\nhistogram legend will now shows correctly\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b7b5173a3bb0e8cb69ecba7e3a78c4e184079fcc","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Theme] load correct system color mode at bootstrap","number":218417,"url":"https://github.com/elastic/kibana/pull/218417","mergeCommit":{"message":"[Theme] load correct system color mode at bootstrap (#218417)\n\n## Summary\n\nThis PR fixes the theme bootstrap when the color mode is configured as\n`system`.\n\nIt uses the `prefers-color-scheme: dark` media match to check if the\npreferred color mode is dark or light and adjust the theme accordingly.\n\nBefore that PR, the `system` color mode caused kibana to bootstrap with\na light mode (even with a dark OS). Only a subsequent event/check will\nupdate the `__kbnThemeTag__` to the correct theme. But at that point the\nSCSS part of elastic-charts is already loaded with the default light\ntheme tokens (the chart theme is loaded from `src/core/public/index.ts`)\n\nWe can probably also find a way to load the chart theme in a subsequent\nstage, when the theme is resolved elsewhere, but the general behaviour\nis anyway buggy: we are loading the kibana application with a wrong\ntheme and only after loading more logic we then switch to the actual\ntheme and update the `__kbnThemeTag__` global.\n\nfix https://github.com/elastic/kibana/issues/210951\n\n\nTo test the before/after:\n- in `main` select the `system` color mode, switch to a Dark mode in\nyour OS, open Discover and apply a breakdown to the histogram: the\nlegend text is too dark and invisible\n- open this pr, select `system` color mode and do the same steps, the\nhistogram legend will now shows correctly\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b7b5173a3bb0e8cb69ecba7e3a78c4e184079fcc"}},"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/218417","number":218417,"mergeCommit":{"message":"[Theme] load correct system color mode at bootstrap (#218417)\n\n## Summary\n\nThis PR fixes the theme bootstrap when the color mode is configured as\n`system`.\n\nIt uses the `prefers-color-scheme: dark` media match to check if the\npreferred color mode is dark or light and adjust the theme accordingly.\n\nBefore that PR, the `system` color mode caused kibana to bootstrap with\na light mode (even with a dark OS). Only a subsequent event/check will\nupdate the `__kbnThemeTag__` to the correct theme. But at that point the\nSCSS part of elastic-charts is already loaded with the default light\ntheme tokens (the chart theme is loaded from `src/core/public/index.ts`)\n\nWe can probably also find a way to load the chart theme in a subsequent\nstage, when the theme is resolved elsewhere, but the general behaviour\nis anyway buggy: we are loading the kibana application with a wrong\ntheme and only after loading more logic we then switch to the actual\ntheme and update the `__kbnThemeTag__` global.\n\nfix https://github.com/elastic/kibana/issues/210951\n\n\nTo test the before/after:\n- in `main` select the `system` color mode, switch to a Dark mode in\nyour OS, open Discover and apply a breakdown to the histogram: the\nlegend text is too dark and invisible\n- open this pr, select `system` color mode and do the same steps, the\nhistogram legend will now shows correctly\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b7b5173a3bb0e8cb69ecba7e3a78c4e184079fcc"}}]}] BACKPORT--> Co-authored-by: Marco Vettorello <marco.vettorello@elastic.co> |
||
Francesco Fagnani
|
23f98ea25b
|
[Synthetics] Added monitor config repository (#221089)
The monitor config repository was created in [this PR](https://github.com/elastic/kibana/pull/202325) but not backported to any other kibana version. This is causing many failures when backporting PRs involving Synthetics code. The goal of this PR is to align older versions with main and avoid future conflicts with backports. |
||
|
Kibana Machine
|
cb5a994b33
|
[9.0] Change the AI Connector description (#221154) (#221195)
# Backport This will backport the following commits from `main` to `9.0`: - [Change the AI Connector description (#221154)](https://github.com/elastic/kibana/pull/221154) <!--- 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-05-21T19:58:38Z","message":"Change the AI Connector description (#221154)\n\n## Summary\n\nChange the AI Connector description to `Send requests to AI providers\nsuch as Amazon Bedrock, OpenAI and more.`\n\n### Checklist\n\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":"6fb97d84aa4035a65f5b5020308d271c2d9f51a5","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.18.2","v9.0.2"],"title":"Change the AI Connector description","number":221154,"url":"https://github.com/elastic/kibana/pull/221154","mergeCommit":{"message":"Change the AI Connector description (#221154)\n\n## Summary\n\nChange the AI Connector description to `Send requests to AI providers\nsuch as Amazon Bedrock, OpenAI and more.`\n\n### Checklist\n\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":"6fb97d84aa4035a65f5b5020308d271c2d9f51a5"}},"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/221154","number":221154,"mergeCommit":{"message":"Change the AI Connector description (#221154)\n\n## Summary\n\nChange the AI Connector description to `Send requests to AI providers\nsuch as Amazon Bedrock, OpenAI and more.`\n\n### Checklist\n\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":"6fb97d84aa4035a65f5b5020308d271c2d9f51a5"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co> |
||
|
Kibana Machine
|
66efa8df69
|
[9.0] [Synthetics] Hide private location saved objects from management UI !! (#221160) (#221192)
# Backport This will backport the following commits from `main` to `9.0`: - [[Synthetics] Hide private location saved objects from management UI !! (#221160)](https://github.com/elastic/kibana/pull/221160) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-05-21T19:52:25Z","message":"[Synthetics] Hide private location saved objects from management UI !! (#221160)\n\n## Summary\n\nHide private location saved objects from management UI to prevent\naccidental deletion !!","sha":"560bde2edfbcaca5d9fb063a3e6a6cdcc4cc6588","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.2","v9.0.2"],"title":"[Synthetics] Hide private location saved objects from management UI !!","number":221160,"url":"https://github.com/elastic/kibana/pull/221160","mergeCommit":{"message":"[Synthetics] Hide private location saved objects from management UI !! (#221160)\n\n## Summary\n\nHide private location saved objects from management UI to prevent\naccidental deletion !!","sha":"560bde2edfbcaca5d9fb063a3e6a6cdcc4cc6588"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","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/221160","number":221160,"mergeCommit":{"message":"[Synthetics] Hide private location saved objects from management UI !! (#221160)\n\n## Summary\n\nHide private location saved objects from management UI to prevent\naccidental deletion !!","sha":"560bde2edfbcaca5d9fb063a3e6a6cdcc4cc6588"}},{"branch":"8.19","label":"v8.19.0","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: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
cfe40a747c
|
[9.0] fix(slo): handle undefined createdBy/updatedBy fields in pipeline (#221158) (#221187)
# Backport This will backport the following commits from `main` to `9.0`: - [fix(slo): handle undefined createdBy/updatedBy fields in pipeline (#221158)](https://github.com/elastic/kibana/pull/221158) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Kevin Delemme","email":"kevin.delemme@elastic.co"},"sourceCommit":{"committedDate":"2025-05-21T19:33:28Z","message":"fix(slo): handle undefined createdBy/updatedBy fields in pipeline (#221158)\n\n## Summary\n\nThis PR fixes an issue with updating SLO created prior to 8.18 which\ndon't have a createdBy and updatedBy values. When updating the SLO we\ncreate the new summary pipeline that uses the slo.createdBy and\nslo.updatedBy optional values.\n\nThe fix consists on handling the undefined values.\n\n### Release note\n\nUpdating SLO created in an older version than 8.18 was failing due to an\ninvalid ingest pipeline.","sha":"394f03fbe87f68e04cb6534b5e97584f6266e445","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.2","v9.0.2"],"title":"fix(slo): handle undefined createdBy/updatedBy fields in pipeline","number":221158,"url":"https://github.com/elastic/kibana/pull/221158","mergeCommit":{"message":"fix(slo): handle undefined createdBy/updatedBy fields in pipeline (#221158)\n\n## Summary\n\nThis PR fixes an issue with updating SLO created prior to 8.18 which\ndon't have a createdBy and updatedBy values. When updating the SLO we\ncreate the new summary pipeline that uses the slo.createdBy and\nslo.updatedBy optional values.\n\nThe fix consists on handling the undefined values.\n\n### Release note\n\nUpdating SLO created in an older version than 8.18 was failing due to an\ninvalid ingest pipeline.","sha":"394f03fbe87f68e04cb6534b5e97584f6266e445"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","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/221158","number":221158,"mergeCommit":{"message":"fix(slo): handle undefined createdBy/updatedBy fields in pipeline (#221158)\n\n## Summary\n\nThis PR fixes an issue with updating SLO created prior to 8.18 which\ndon't have a createdBy and updatedBy values. When updating the SLO we\ncreate the new summary pipeline that uses the slo.createdBy and\nslo.updatedBy optional values.\n\nThe fix consists on handling the undefined values.\n\n### Release note\n\nUpdating SLO created in an older version than 8.18 was failing due to an\ninvalid ingest pipeline.","sha":"394f03fbe87f68e04cb6534b5e97584f6266e445"}},{"branch":"8.19","label":"v8.19.0","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: Kevin Delemme <kevin.delemme@elastic.co> |
||
Lisa Cawley
|
d57c64902c
|
[9.0] Use new beat URLs in doc link service (#219310) (#220721)
# Backport This will backport the following commits from `main` to `9.0`: - [Use new beat URLs in doc link service (#219310)](https://github.com/elastic/kibana/pull/219310) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-05-09T10:01:39Z","message":"Use new beat URLs in doc link service (#219310)","sha":"5b005594cc8c231b24934bd3c4f8c2593c3561f6","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","ci:cloud-deploy","ci:project-deploy-observability","backport:version","v9.1.0","v9.0.1"],"title":"Use new beat URLs in doc link service","number":219310,"url":"https://github.com/elastic/kibana/pull/219310","mergeCommit":{"message":"Use new beat URLs in doc link service (#219310)","sha":"5b005594cc8c231b24934bd3c4f8c2593c3561f6"}},"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/219310","number":219310,"mergeCommit":{"message":"Use new beat URLs in doc link service (#219310)","sha":"5b005594cc8c231b24934bd3c4f8c2593c3561f6"}},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
fba7a932d7
|
[9.0] [CLOUD] fix defaultRoute for app/cloud/onboarding (#221029) (#221175)
# Backport This will backport the following commits from `main` to `9.0`: - [[CLOUD] fix defaultRoute for app/cloud/onboarding (#221029)](https://github.com/elastic/kibana/pull/221029) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Xavier Mouligneau","email":"xavier.mouligneau@elastic.co"},"sourceCommit":{"committedDate":"2025-05-21T18:32:00Z","message":"[CLOUD] fix defaultRoute for app/cloud/onboarding (#221029)\n\n## Summary\n\nThe uiSettings client need to have the Kibana request to send back the\ndefaultRoute for a space.\n\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":"6f41f416262e5368d12c5f8deab64fe28af9a890","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Cloud","release_note:skip","backport:version","v9.1.0","v8.19.0","v8.18.2","v9.0.2"],"title":"[CLOUD] fix defaultRoute for app/cloud/onboarding","number":221029,"url":"https://github.com/elastic/kibana/pull/221029","mergeCommit":{"message":"[CLOUD] fix defaultRoute for app/cloud/onboarding (#221029)\n\n## Summary\n\nThe uiSettings client need to have the Kibana request to send back the\ndefaultRoute for a space.\n\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":"6f41f416262e5368d12c5f8deab64fe28af9a890"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","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/221029","number":221029,"mergeCommit":{"message":"[CLOUD] fix defaultRoute for app/cloud/onboarding (#221029)\n\n## Summary\n\nThe uiSettings client need to have the Kibana request to send back the\ndefaultRoute for a space.\n\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":"6f41f416262e5368d12c5f8deab64fe28af9a890"}},{"branch":"8.19","label":"v8.19.0","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: Xavier Mouligneau <xavier.mouligneau@elastic.co> |
||
|
Kibana Machine
|
9c1c200f3e
|
[9.0] [Visualization-utils] Fix getTimezone default value (#220658) (#221171)
# Backport This will backport the following commits from `main` to `9.0`: - [[Visualization-utils] Fix getTimezone default value (#220658)](https://github.com/elastic/kibana/pull/220658) <!--- 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-05-21T18:12:13Z","message":"[Visualization-utils] Fix getTimezone default value (#220658)\n\n## Summary\n\nfix https://github.com/elastic/kibana/issues/220644\n\nThis PR fixes the mentioned issue by defaulting any non-valid IANA\ntimezone to the current browser client timezone.\n\nI'm also calling `moment.tz.guess(true)` with the true value because if\nnot moment will cache the first timezone guessed and will not be updated\nif the customer change it manually.\n>By default Moment Timezone caches the detected timezone. This means\nthat subsequent calls to moment.tz.guess() will always return the same\nvalue.\nYou can call moment.tz.guess() with an optional boolean argument\n\"ignoreCache\". If set to true, the cache will be ignored and overwritten\nwith the new value.\n\n\n## Release note \n\nThe default timezone is now correctly applied in TSVB if the user\nchanges and resets to the default the Advanced Setting timezone\nparameter.","sha":"28cc698f043df75265632fa0def65e1121fa0c04","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Visualizations","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Visualization-utils] Fix getTimezone default value","number":220658,"url":"https://github.com/elastic/kibana/pull/220658","mergeCommit":{"message":"[Visualization-utils] Fix getTimezone default value (#220658)\n\n## Summary\n\nfix https://github.com/elastic/kibana/issues/220644\n\nThis PR fixes the mentioned issue by defaulting any non-valid IANA\ntimezone to the current browser client timezone.\n\nI'm also calling `moment.tz.guess(true)` with the true value because if\nnot moment will cache the first timezone guessed and will not be updated\nif the customer change it manually.\n>By default Moment Timezone caches the detected timezone. This means\nthat subsequent calls to moment.tz.guess() will always return the same\nvalue.\nYou can call moment.tz.guess() with an optional boolean argument\n\"ignoreCache\". If set to true, the cache will be ignored and overwritten\nwith the new value.\n\n\n## Release note \n\nThe default timezone is now correctly applied in TSVB if the user\nchanges and resets to the default the Advanced Setting timezone\nparameter.","sha":"28cc698f043df75265632fa0def65e1121fa0c04"}},"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/220658","number":220658,"mergeCommit":{"message":"[Visualization-utils] Fix getTimezone default value (#220658)\n\n## Summary\n\nfix https://github.com/elastic/kibana/issues/220644\n\nThis PR fixes the mentioned issue by defaulting any non-valid IANA\ntimezone to the current browser client timezone.\n\nI'm also calling `moment.tz.guess(true)` with the true value because if\nnot moment will cache the first timezone guessed and will not be updated\nif the customer change it manually.\n>By default Moment Timezone caches the detected timezone. This means\nthat subsequent calls to moment.tz.guess() will always return the same\nvalue.\nYou can call moment.tz.guess() with an optional boolean argument\n\"ignoreCache\". If set to true, the cache will be ignored and overwritten\nwith the new value.\n\n\n## Release note \n\nThe default timezone is now correctly applied in TSVB if the user\nchanges and resets to the default the Advanced Setting timezone\nparameter.","sha":"28cc698f043df75265632fa0def65e1121fa0c04"}}]}] BACKPORT--> Co-authored-by: Marco Vettorello <marco.vettorello@elastic.co> |
||
|
Lisa Cawley
|
7e77ae87c7
|
[9.0] Use new logstash, addData, logging, ingest URLs (#219286) (#220728)
# Backport This will backport the following commits from `main` to `9.0`: - [Use new logstash, addData, logging, ingest URLs (#219286)](https://github.com/elastic/kibana/pull/219286) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-05-10T01:51:52Z","message":"Use new logstash, addData, logging, ingest URLs (#219286)\n\n\nCo-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>","sha":"b0a841c4215db4dc7ba083fe71304a78870c85c0","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","backport:version","v9.1.0","v9.0.1"],"title":"Use new logstash, addData, logging, ingest URLs","number":219286,"url":"https://github.com/elastic/kibana/pull/219286","mergeCommit":{"message":"Use new logstash, addData, logging, ingest URLs (#219286)\n\n\nCo-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>","sha":"b0a841c4215db4dc7ba083fe71304a78870c85c0"}},"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/219286","number":219286,"mergeCommit":{"message":"Use new logstash, addData, logging, ingest URLs (#219286)\n\n\nCo-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>","sha":"b0a841c4215db4dc7ba083fe71304a78870c85c0"}},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jean-Louis Leysens <jloleysens@gmail.com> Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co> |
||
|
Kibana Machine
|
873840f607
|
[9.0] deps: Bump ironbank version to 9.6 (#221098) (#221147)
# Backport This will backport the following commits from `main` to `9.0`: - [deps: Bump ironbank version to 9.6 (#221098)](https://github.com/elastic/kibana/pull/221098) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"github-actions[bot]","email":"41898282+github-actions[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-05-21T15:36:36Z","message":"deps: Bump ironbank version to 9.6 (#221098)\n\n<Actions>\n<action\nid=\"ad27da7f660d61c82c61599e0e6945827ced1590f4bf36a5f74db07e99c04215\">\n <h3>deps: Bump ironbank version</h3>\n<details\nid=\"99cabf4d5a2b44b2d93b4c18590b8ccd5df3002e8d9d506c038c9011e8e93734\">\n <summary>deps(ironbank): Bump ubi version to 9.6</summary>\n<p>change detected:
	* key "$.args.BASE_TAG" updated\nfrom "\\"9.5\\"" to "\\"9.6\\"", in file\n"src/dev/build/tasks/os_packages/docker_generator/templates/ironbank/hardening_manifest.yaml"</p>\n </details>\n<details\nid=\"21fe544f0edf8039d0165187f8204a62da22d72e50fa57839d823beb83c0df2e\">\n <summary>deps(ironbank): Bump ubi version to 9.6</summary>\n<p>changed lines [7] of file\n"/tmp/updatecli/github/elastic/kibana/src/dev/build/tasks/os_packages/docker_generator/templates/ironbank/Dockerfile"</p>\n </details>\n<a\nhref=\" |
||
|
Kibana Machine
|
6b45e699a7
|
[9.0] [ci] Bump jest disk to 80gb (#221116) (#221120)
# Backport This will backport the following commits from `main` to `9.0`: - [[ci] Bump jest disk to 80gb (#221116)](https://github.com/elastic/kibana/pull/221116) <!--- 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-05-21T13:08:56Z","message":"[ci] Bump jest disk to 80gb (#221116)","sha":"d5e2aa961c9220108e3b736e199fd0c7b86daf4d","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","skip-ci","backport:all-open","v9.1.0"],"title":"[ci] Bump jest disk to 80gb","number":221116,"url":"https://github.com/elastic/kibana/pull/221116","mergeCommit":{"message":"[ci] Bump jest disk to 80gb (#221116)","sha":"d5e2aa961c9220108e3b736e199fd0c7b86daf4d"}},"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/221116","number":221116,"mergeCommit":{"message":"[ci] Bump jest disk to 80gb (#221116)","sha":"d5e2aa961c9220108e3b736e199fd0c7b86daf4d"}}]}] BACKPORT--> Co-authored-by: Jon <jon@elastic.co> |
||
|
Kibana Machine
|
d41f5fca10
|
[9.0] [ci] Bump checks disk to 85gb (#221118) (#221124)
# Backport This will backport the following commits from `main` to `9.0`: - [[ci] Bump checks disk to 85gb (#221118)](https://github.com/elastic/kibana/pull/221118) <!--- 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-05-21T13:15:01Z","message":"[ci] Bump checks disk to 85gb (#221118)","sha":"878e7e524ac19f719210a78f7d8b7795536505e0","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","skip-ci","backport:all-open","v9.1.0"],"title":"[ci] Bump checks disk to 85gb","number":221118,"url":"https://github.com/elastic/kibana/pull/221118","mergeCommit":{"message":"[ci] Bump checks disk to 85gb (#221118)","sha":"878e7e524ac19f719210a78f7d8b7795536505e0"}},"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/221118","number":221118,"mergeCommit":{"message":"[ci] Bump checks disk to 85gb (#221118)","sha":"878e7e524ac19f719210a78f7d8b7795536505e0"}}]}] BACKPORT--> Co-authored-by: Jon <jon@elastic.co> |
||
|
Kibana Machine
|
18540293aa
|
[9.0] [Synthetics] In the status rule locations are considered only if not an empty array (#220983) (#221025)
# Backport This will backport the following commits from `main` to `9.0`: - [[Synthetics] In the status rule locations are considered only if not an empty array (#220983)](https://github.com/elastic/kibana/pull/220983) <!--- 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-05-20T15:42:01Z","message":"[Synthetics] In the status rule locations are considered only if not an empty array (#220983)\n\nThis PR fixes an\n[issue](https://github.com/elastic/sdh-kibana/issues/5452) found when\nsetting an empty array for locations in a monitor status rule.\n\nIf passing an empty array the logic should behave as when locations is\nundefined.","sha":"76034cb1123216af7f4028cb65675e3c83b66c23","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.17.7","v8.18.2","v9.0.2","author:obs-ux-management"],"title":"[Synthetics] In the status rule locations are considered only if not an empty array","number":220983,"url":"https://github.com/elastic/kibana/pull/220983","mergeCommit":{"message":"[Synthetics] In the status rule locations are considered only if not an empty array (#220983)\n\nThis PR fixes an\n[issue](https://github.com/elastic/sdh-kibana/issues/5452) found when\nsetting an empty array for locations in a monitor status rule.\n\nIf passing an empty array the logic should behave as when locations is\nundefined.","sha":"76034cb1123216af7f4028cb65675e3c83b66c23"}},"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/220983","number":220983,"mergeCommit":{"message":"[Synthetics] In the status rule locations are considered only if not an empty array (#220983)\n\nThis PR fixes an\n[issue](https://github.com/elastic/sdh-kibana/issues/5452) found when\nsetting an empty array for locations in a monitor status rule.\n\nIf passing an empty array the logic should behave as when locations is\nundefined.","sha":"76034cb1123216af7f4028cb65675e3c83b66c23"}},{"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: Francesco Fagnani <fagnani.francesco@gmail.com> |
||
|
Kibana Machine
|
66dc5bb5e2
|
[9.0] [Kibana Dev Server] Fix DELETE requests without a body in Safari (#220899) (#220968)
# Backport This will backport the following commits from `main` to `9.0`: - [[Kibana Dev Server] Fix `DELETE` requests without a body in Safari (#220899)](https://github.com/elastic/kibana/pull/220899) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-05-20T07:35:30Z","message":"[Kibana Dev Server] Fix `DELETE` requests without a body in Safari (#220899)\n\nRecently, we discovered that a `DELETE` request to one of our ML\nendpoints does not work correctly in Safari.\nAfter further investigation, it turns out that `DELETE` requests without\na body fail in Safari.\nThe issue occurs only within the Kibana Dev server, so there is no\nimpact on end users.\nThis is most likely due to a header set in the\n`packages/kbn-cli-dev-mode/src/base_path_proxy/http1.ts` file. The issue\nmentioned in the comment has already been resolved, and everything\nappears to work correctly without this outdated workaround.\n\nTo reproduce the error:\n1. Start Kibana locally and open it with Safari.\n2. Find an endpoint that uses the `DELETE` method and does not have a\nbody specified.\n3. ^ For example, go to Observability -> Cases and create a new case.\n4. Go back to the cases list and try to delete the case","sha":"fa0500c346389758fb09935be246752dcdbbb6f3","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:http","Team:Operations","release_note:skip","backport:version","v9.1.0","v8.19.0","v8.17.7","v8.18.2","v9.0.2"],"title":"[Kibana Dev Server] Fix `DELETE` requests without a body in Safari","number":220899,"url":"https://github.com/elastic/kibana/pull/220899","mergeCommit":{"message":"[Kibana Dev Server] Fix `DELETE` requests without a body in Safari (#220899)\n\nRecently, we discovered that a `DELETE` request to one of our ML\nendpoints does not work correctly in Safari.\nAfter further investigation, it turns out that `DELETE` requests without\na body fail in Safari.\nThe issue occurs only within the Kibana Dev server, so there is no\nimpact on end users.\nThis is most likely due to a header set in the\n`packages/kbn-cli-dev-mode/src/base_path_proxy/http1.ts` file. The issue\nmentioned in the comment has already been resolved, and everything\nappears to work correctly without this outdated workaround.\n\nTo reproduce the error:\n1. Start Kibana locally and open it with Safari.\n2. Find an endpoint that uses the `DELETE` method and does not have a\nbody specified.\n3. ^ For example, go to Observability -> Cases and create a new case.\n4. Go back to the cases list and try to delete the case","sha":"fa0500c346389758fb09935be246752dcdbbb6f3"}},"sourceBranch":"main","suggestedTargetBranches":["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/220899","number":220899,"mergeCommit":{"message":"[Kibana Dev Server] Fix `DELETE` requests without a body in Safari (#220899)\n\nRecently, we discovered that a `DELETE` request to one of our ML\nendpoints does not work correctly in Safari.\nAfter further investigation, it turns out that `DELETE` requests without\na body fail in Safari.\nThe issue occurs only within the Kibana Dev server, so there is no\nimpact on end users.\nThis is most likely due to a header set in the\n`packages/kbn-cli-dev-mode/src/base_path_proxy/http1.ts` file. The issue\nmentioned in the comment has already been resolved, and everything\nappears to work correctly without this outdated workaround.\n\nTo reproduce the error:\n1. Start Kibana locally and open it with Safari.\n2. Find an endpoint that uses the `DELETE` method and does not have a\nbody specified.\n3. ^ For example, go to Observability -> Cases and create a new case.\n4. Go back to the cases list and try to delete the case","sha":"fa0500c346389758fb09935be246752dcdbbb6f3"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/220964","number":220964,"state":"OPEN"},{"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: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com> |
||
|
Kibana Machine
|
6673dce5df
|
[9.0] ScopedHistory Error - Remove calling verifyAction assertion from getters (#220313) (#221071)
# Backport This will backport the following commits from `main` to `9.0`: - [ScopedHistory Error - Remove calling `verifyAction` assertion from getters (#220313)](https://github.com/elastic/kibana/pull/220313) <!--- 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-05-21T04:40:40Z","message":"ScopedHistory Error - Remove calling `verifyAction` assertion from getters (#220313)\n\n## Summary\nThis PR modifies the `CoreScopedHistory` implementation to remove scope\nverification for getter methods while maintaining it for action methods.\nThis change aims to reduce errors occurring during plugin navigation\ntransitions when components are dismounting.\n\n## Background\nCurrently, when components are dismounting during navigation between\nplugins, calls to `ScopedHistory` methods (particularly getters like\n`location`) trigger the\n\n```TypeScript\n`ScopedHistory instance has fell out of navigation scope for basePath: ${this.basePath}`\n```\n\nThis happens because the location's `pathname` has already changed while\nsome components are still in their cleanup phase.\n\n## Changes\n- Removed `verifyActive()` checks from the following getter methods:\n - `location`\n - `action`\n - `length`\n- The following methods still assert `verifyActive()`:\n - `push`\n - `replace`\n - `go`\n - `goBack`\n - `goForward`\n - `block`\n - `listen`\n - `createHref`","sha":"434dd520bdea905efee5dcec6bb7bd68e6883dbe","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.1.0"],"title":"ScopedHistory Error - Remove calling `verifyAction` assertion from getters","number":220313,"url":"https://github.com/elastic/kibana/pull/220313","mergeCommit":{"message":"ScopedHistory Error - Remove calling `verifyAction` assertion from getters (#220313)\n\n## Summary\nThis PR modifies the `CoreScopedHistory` implementation to remove scope\nverification for getter methods while maintaining it for action methods.\nThis change aims to reduce errors occurring during plugin navigation\ntransitions when components are dismounting.\n\n## Background\nCurrently, when components are dismounting during navigation between\nplugins, calls to `ScopedHistory` methods (particularly getters like\n`location`) trigger the\n\n```TypeScript\n`ScopedHistory instance has fell out of navigation scope for basePath: ${this.basePath}`\n```\n\nThis happens because the location's `pathname` has already changed while\nsome components are still in their cleanup phase.\n\n## Changes\n- Removed `verifyActive()` checks from the following getter methods:\n - `location`\n - `action`\n - `length`\n- The following methods still assert `verifyActive()`:\n - `push`\n - `replace`\n - `go`\n - `goBack`\n - `goForward`\n - `block`\n - `listen`\n - `createHref`","sha":"434dd520bdea905efee5dcec6bb7bd68e6883dbe"}},"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/220313","number":220313,"mergeCommit":{"message":"ScopedHistory Error - Remove calling `verifyAction` assertion from getters (#220313)\n\n## Summary\nThis PR modifies the `CoreScopedHistory` implementation to remove scope\nverification for getter methods while maintaining it for action methods.\nThis change aims to reduce errors occurring during plugin navigation\ntransitions when components are dismounting.\n\n## Background\nCurrently, when components are dismounting during navigation between\nplugins, calls to `ScopedHistory` methods (particularly getters like\n`location`) trigger the\n\n```TypeScript\n`ScopedHistory instance has fell out of navigation scope for basePath: ${this.basePath}`\n```\n\nThis happens because the location's `pathname` has already changed while\nsome components are still in their cleanup phase.\n\n## Changes\n- Removed `verifyActive()` checks from the following getter methods:\n - `location`\n - `action`\n - `length`\n- The following methods still assert `verifyActive()`:\n - `push`\n - `replace`\n - `go`\n - `goBack`\n - `goForward`\n - `block`\n - `listen`\n - `createHref`","sha":"434dd520bdea905efee5dcec6bb7bd68e6883dbe"}}]}] BACKPORT--> Co-authored-by: Abdul Wahab Zahid <awahab07@yahoo.com> |
||
|
Kibana Machine
|
fd23e2e0ea
|
[9.0] [Sessions] Check and allow session cookies if they are all the same (#220430) (#221062)
# Backport This will backport the following commits from `main` to `9.0`: - [[Sessions] Check and allow session cookies if they are all the same (#220430)](https://github.com/elastic/kibana/pull/220430) <!--- 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-05-20T22:10:00Z","message":"[Sessions] Check and allow session cookies if they are all the same (#220430)\n\n## Summary\nCloses https://github.com/elastic/kibana/issues/220637\nCloses https://github.com/elastic/kibana/issues/220755\n\nTesting steps:\n\n#### Steps to reproduce the bug, in firefox and on main:\n- Download/update to latest firefox version\n- Run ES and kibana locally\n- Login to Kibana\n- Set up the sample data (E-commerce for example)\n- Force cache disabling (open dev tools -> Network tab -> Ensure Disable\ncache is not checked and keep dev tools open)\n- Navigate to Stack Management -> Data views (under kibana in left nav)\n- Click on first data view \n- Triggers a logout\n\n### Verify the fix\n- Run the same steps above on this PR\n\n## Release notes\nRework cookie and session storage to prevent unexpected logouts for\ncertain users with certain use cases.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"7a3bd993cee008e9bfa369249d8e3e03e551c004","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Security/Session Management","backport:all-open","v9.1.0"],"title":"[Sessions] Check and allow session cookies if they are all the same","number":220430,"url":"https://github.com/elastic/kibana/pull/220430","mergeCommit":{"message":"[Sessions] Check and allow session cookies if they are all the same (#220430)\n\n## Summary\nCloses https://github.com/elastic/kibana/issues/220637\nCloses https://github.com/elastic/kibana/issues/220755\n\nTesting steps:\n\n#### Steps to reproduce the bug, in firefox and on main:\n- Download/update to latest firefox version\n- Run ES and kibana locally\n- Login to Kibana\n- Set up the sample data (E-commerce for example)\n- Force cache disabling (open dev tools -> Network tab -> Ensure Disable\ncache is not checked and keep dev tools open)\n- Navigate to Stack Management -> Data views (under kibana in left nav)\n- Click on first data view \n- Triggers a logout\n\n### Verify the fix\n- Run the same steps above on this PR\n\n## Release notes\nRework cookie and session storage to prevent unexpected logouts for\ncertain users with certain use cases.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"7a3bd993cee008e9bfa369249d8e3e03e551c004"}},"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/220430","number":220430,"mergeCommit":{"message":"[Sessions] Check and allow session cookies if they are all the same (#220430)\n\n## Summary\nCloses https://github.com/elastic/kibana/issues/220637\nCloses https://github.com/elastic/kibana/issues/220755\n\nTesting steps:\n\n#### Steps to reproduce the bug, in firefox and on main:\n- Download/update to latest firefox version\n- Run ES and kibana locally\n- Login to Kibana\n- Set up the sample data (E-commerce for example)\n- Force cache disabling (open dev tools -> Network tab -> Ensure Disable\ncache is not checked and keep dev tools open)\n- Navigate to Stack Management -> Data views (under kibana in left nav)\n- Click on first data view \n- Triggers a logout\n\n### Verify the fix\n- Run the same steps above on this PR\n\n## Release notes\nRework cookie and session storage to prevent unexpected logouts for\ncertain users with certain use cases.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"7a3bd993cee008e9bfa369249d8e3e03e551c004"}}]}] BACKPORT--> Co-authored-by: Sid <siddharthmantri1@gmail.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
Marshall Main
|
0c25a3b90f
|
[9.0] Update dependency buildkite-test-collector to ^1.8.1 (main) (#206164) (#221015)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency buildkite-test-collector to ^1.8.1 (main) (#206164)](https://github.com/elastic/kibana/pull/206164) <!--- 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-05-20T15:01:22Z","message":"Update dependency buildkite-test-collector to ^1.8.1 (main) (#206164)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [buildkite-test-collector](https://buildkite.com/platform/test-engine)\n([source](https://redirect.github.com/buildkite/test-collector-javascript))\n| devDependencies | minor | [`^1.7.0` ->\n`^1.8.1`](https://renovatebot.com/diffs/npm/buildkite-test-collector/1.7.0/1.8.1)\n|\n\n---\n\n### Release Notes\n\n<details>\n<summary>buildkite/test-collector-javascript\n(buildkite-test-collector)</summary>\n\n###\n[`v1.8.1`](https://redirect.github.com/buildkite/test-collector-javascript/releases/tag/v1.8.1)\n\n[Compare\nSource](https://redirect.github.com/buildkite/test-collector-javascript/compare/v1.8.0...v1.8.1)\n\n#### What's Changed\n\n- Bump axios from 1.6.8 to 1.8.2 by\n[@​dependabot](https://redirect.github.com/dependabot) in\n[https://github.com/buildkite/test-collector-javascript/pull/104](https://redirect.github.com/buildkite/test-collector-javascript/pull/104)\n\n#### Minor / internal changes\n\n- Test coverage for generic CI `run_env` by\n[@​pda](https://redirect.github.com/pda) in\n[https://github.com/buildkite/test-collector-javascript/pull/98](https://redirect.github.com/buildkite/test-collector-javascript/pull/98)\n- Analytics -> Engine renames by\n[@​wooly](https://redirect.github.com/wooly) in\n[https://github.com/buildkite/test-collector-javascript/pull/102](https://redirect.github.com/buildkite/test-collector-javascript/pull/102)\n\n#### New Contributors\n\n- [@​wooly](https://redirect.github.com/wooly) made their first\ncontribution in\n[https://github.com/buildkite/test-collector-javascript/pull/102](https://redirect.github.com/buildkite/test-collector-javascript/pull/102)\n- [@​dependabot](https://redirect.github.com/dependabot) made\ntheir first contribution in\n[https://github.com/buildkite/test-collector-javascript/pull/104](https://redirect.github.com/buildkite/test-collector-javascript/pull/104)\n\n**Full Changelog**:\nhttps://github.com/buildkite/test-collector-javascript/compare/v1.8.0...v1.8.1\n\n###\n[`v1.8.0`](https://redirect.github.com/buildkite/test-collector-javascript/releases/tag/v1.8.0)\n\n[Compare\nSource](https://redirect.github.com/buildkite/test-collector-javascript/compare/v1.7.3...v1.8.0)\n\n#### What's Changed\n\n- Introduce `tags` option by\n[@​pda](https://redirect.github.com/pda) in\n[https://github.com/buildkite/test-collector-javascript/pull/100](https://redirect.github.com/buildkite/test-collector-javascript/pull/100)\n\n##### Minor / house-keeping\n\n- playwright test server moved to less common port (8080 -> 18080) by\n[@​pda](https://redirect.github.com/pda) in\n[https://github.com/buildkite/test-collector-javascript/pull/99](https://redirect.github.com/buildkite/test-collector-javascript/pull/99)\n- Prepare v1.8.0 by [@​pda](https://redirect.github.com/pda) in\n[https://github.com/buildkite/test-collector-javascript/pull/101](https://redirect.github.com/buildkite/test-collector-javascript/pull/101)\n\n#### New Contributors\n\n- [@​pda](https://redirect.github.com/pda) made their first\ncontribution in\n[https://github.com/buildkite/test-collector-javascript/pull/99](https://redirect.github.com/buildkite/test-collector-javascript/pull/99)\n\n**Full Changelog**:\nhttps://github.com/buildkite/test-collector-javascript/compare/v1.7.3...v1.8.0\n\n###\n[`v1.7.3`](https://redirect.github.com/buildkite/test-collector-javascript/releases/tag/v1.7.3)\n\n[Compare\nSource](https://redirect.github.com/buildkite/test-collector-javascript/compare/v1.7.2...v1.7.3)\n\n#### What's Changed\n\n- Rescue errors from uploadTestResults by\n[@​nprizal](https://redirect.github.com/nprizal) in\n[https://github.com/buildkite/test-collector-javascript/pull/95](https://redirect.github.com/buildkite/test-collector-javascript/pull/95)\n\n**Full Changelog**:\nhttps://github.com/buildkite/test-collector-javascript/compare/v1.7.2...v1.7.3\n\n###\n[`v1.7.2`](https://redirect.github.com/buildkite/test-collector-javascript/releases/tag/v1.7.2)\n\n[Compare\nSource](https://redirect.github.com/buildkite/test-collector-javascript/compare/v1.7.1...v1.7.2)\n\n#### What's Changed\n\n- Run tests on a new queue by\n[@​yob](https://redirect.github.com/yob) in\n[https://github.com/buildkite/test-collector-javascript/pull/90](https://redirect.github.com/buildkite/test-collector-javascript/pull/90)\n- Fix async problem in jest reporter when trying to run `onRunComplete`\nby [@​JasonShin](https://redirect.github.com/JasonShin) in\n[https://github.com/buildkite/test-collector-javascript/pull/91](https://redirect.github.com/buildkite/test-collector-javascript/pull/91)\n- Release v1.7.2 by\n[@​nprizal](https://redirect.github.com/nprizal) in\n[https://github.com/buildkite/test-collector-javascript/pull/93](https://redirect.github.com/buildkite/test-collector-javascript/pull/93)\n\n#### New Contributors\n\n- [@​yob](https://redirect.github.com/yob) made their first\ncontribution in\n[https://github.com/buildkite/test-collector-javascript/pull/90](https://redirect.github.com/buildkite/test-collector-javascript/pull/90)\n- [@​JasonShin](https://redirect.github.com/JasonShin) made their\nfirst contribution in\n[https://github.com/buildkite/test-collector-javascript/pull/91](https://redirect.github.com/buildkite/test-collector-javascript/pull/91)\n\n**Full Changelog**:\nhttps://github.com/buildkite/test-collector-javascript/compare/v1.7.1...v1.7.2\n\n###\n[`v1.7.1`](https://redirect.github.com/buildkite/test-collector-javascript/releases/tag/v1.7.1)\n\n[Compare\nSource](https://redirect.github.com/buildkite/test-collector-javascript/compare/v1.7.0...v1.7.1)\n\n#### What's Changed\n\n- Bump axios from 1.6.2 to 1.6.8 to address CVE-2024-28849 by\n[@​gchan](https://redirect.github.com/gchan) in\n[https://github.com/buildkite/test-collector-javascript/pull/88](https://redirect.github.com/buildkite/test-collector-javascript/pull/88)\n\n**Full Changelog**:\nhttps://github.com/buildkite/test-collector-javascript/compare/v1.7.0...v1.7.1\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>","sha":"01df4b3b027992b8fc7a4a77040b6b91b8104702","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 dependency buildkite-test-collector to ^1.8.1 (main)","number":206164,"url":"https://github.com/elastic/kibana/pull/206164","mergeCommit":{"message":"Update dependency buildkite-test-collector to ^1.8.1 (main) (#206164)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [buildkite-test-collector](https://buildkite.com/platform/test-engine)\n([source](https://redirect.github.com/buildkite/test-collector-javascript))\n| devDependencies | minor | [`^1.7.0` ->\n`^1.8.1`](https://renovatebot.com/diffs/npm/buildkite-test-collector/1.7.0/1.8.1)\n|\n\n---\n\n### Release Notes\n\n<details>\n<summary>buildkite/test-collector-javascript\n(buildkite-test-collector)</summary>\n\n###\n[`v1.8.1`](https://redirect.github.com/buildkite/test-collector-javascript/releases/tag/v1.8.1)\n\n[Compare\nSource](https://redirect.github.com/buildkite/test-collector-javascript/compare/v1.8.0...v1.8.1)\n\n#### What's Changed\n\n- Bump axios from 1.6.8 to 1.8.2 by\n[@​dependabot](https://redirect.github.com/dependabot) in\n[https://github.com/buildkite/test-collector-javascript/pull/104](https://redirect.github.com/buildkite/test-collector-javascript/pull/104)\n\n#### Minor / internal changes\n\n- Test coverage for generic CI `run_env` by\n[@​pda](https://redirect.github.com/pda) in\n[https://github.com/buildkite/test-collector-javascript/pull/98](https://redirect.github.com/buildkite/test-collector-javascript/pull/98)\n- Analytics -> Engine renames by\n[@​wooly](https://redirect.github.com/wooly) in\n[https://github.com/buildkite/test-collector-javascript/pull/102](https://redirect.github.com/buildkite/test-collector-javascript/pull/102)\n\n#### New Contributors\n\n- [@​wooly](https://redirect.github.com/wooly) made their first\ncontribution in\n[https://github.com/buildkite/test-collector-javascript/pull/102](https://redirect.github.com/buildkite/test-collector-javascript/pull/102)\n- [@​dependabot](https://redirect.github.com/dependabot) made\ntheir first contribution in\n[https://github.com/buildkite/test-collector-javascript/pull/104](https://redirect.github.com/buildkite/test-collector-javascript/pull/104)\n\n**Full Changelog**:\nhttps://github.com/buildkite/test-collector-javascript/compare/v1.8.0...v1.8.1\n\n###\n[`v1.8.0`](https://redirect.github.com/buildkite/test-collector-javascript/releases/tag/v1.8.0)\n\n[Compare\nSource](https://redirect.github.com/buildkite/test-collector-javascript/compare/v1.7.3...v1.8.0)\n\n#### What's Changed\n\n- Introduce `tags` option by\n[@​pda](https://redirect.github.com/pda) in\n[https://github.com/buildkite/test-collector-javascript/pull/100](https://redirect.github.com/buildkite/test-collector-javascript/pull/100)\n\n##### Minor / house-keeping\n\n- playwright test server moved to less common port (8080 -> 18080) by\n[@​pda](https://redirect.github.com/pda) in\n[https://github.com/buildkite/test-collector-javascript/pull/99](https://redirect.github.com/buildkite/test-collector-javascript/pull/99)\n- Prepare v1.8.0 by [@​pda](https://redirect.github.com/pda) in\n[https://github.com/buildkite/test-collector-javascript/pull/101](https://redirect.github.com/buildkite/test-collector-javascript/pull/101)\n\n#### New Contributors\n\n- [@​pda](https://redirect.github.com/pda) made their first\ncontribution in\n[https://github.com/buildkite/test-collector-javascript/pull/99](https://redirect.github.com/buildkite/test-collector-javascript/pull/99)\n\n**Full Changelog**:\nhttps://github.com/buildkite/test-collector-javascript/compare/v1.7.3...v1.8.0\n\n###\n[`v1.7.3`](https://redirect.github.com/buildkite/test-collector-javascript/releases/tag/v1.7.3)\n\n[Compare\nSource](https://redirect.github.com/buildkite/test-collector-javascript/compare/v1.7.2...v1.7.3)\n\n#### What's Changed\n\n- Rescue errors from uploadTestResults by\n[@​nprizal](https://redirect.github.com/nprizal) in\n[https://github.com/buildkite/test-collector-javascript/pull/95](https://redirect.github.com/buildkite/test-collector-javascript/pull/95)\n\n**Full Changelog**:\nhttps://github.com/buildkite/test-collector-javascript/compare/v1.7.2...v1.7.3\n\n###\n[`v1.7.2`](https://redirect.github.com/buildkite/test-collector-javascript/releases/tag/v1.7.2)\n\n[Compare\nSource](https://redirect.github.com/buildkite/test-collector-javascript/compare/v1.7.1...v1.7.2)\n\n#### What's Changed\n\n- Run tests on a new queue by\n[@​yob](https://redirect.github.com/yob) in\n[https://github.com/buildkite/test-collector-javascript/pull/90](https://redirect.github.com/buildkite/test-collector-javascript/pull/90)\n- Fix async problem in jest reporter when trying to run `onRunComplete`\nby [@​JasonShin](https://redirect.github.com/JasonShin) in\n[https://github.com/buildkite/test-collector-javascript/pull/91](https://redirect.github.com/buildkite/test-collector-javascript/pull/91)\n- Release v1.7.2 by\n[@​nprizal](https://redirect.github.com/nprizal) in\n[https://github.com/buildkite/test-collector-javascript/pull/93](https://redirect.github.com/buildkite/test-collector-javascript/pull/93)\n\n#### New Contributors\n\n- [@​yob](https://redirect.github.com/yob) made their first\ncontribution in\n[https://github.com/buildkite/test-collector-javascript/pull/90](https://redirect.github.com/buildkite/test-collector-javascript/pull/90)\n- [@​JasonShin](https://redirect.github.com/JasonShin) made their\nfirst contribution in\n[https://github.com/buildkite/test-collector-javascript/pull/91](https://redirect.github.com/buildkite/test-collector-javascript/pull/91)\n\n**Full Changelog**:\nhttps://github.com/buildkite/test-collector-javascript/compare/v1.7.1...v1.7.2\n\n###\n[`v1.7.1`](https://redirect.github.com/buildkite/test-collector-javascript/releases/tag/v1.7.1)\n\n[Compare\nSource](https://redirect.github.com/buildkite/test-collector-javascript/compare/v1.7.0...v1.7.1)\n\n#### What's Changed\n\n- Bump axios from 1.6.2 to 1.6.8 to address CVE-2024-28849 by\n[@​gchan](https://redirect.github.com/gchan) in\n[https://github.com/buildkite/test-collector-javascript/pull/88](https://redirect.github.com/buildkite/test-collector-javascript/pull/88)\n\n**Full Changelog**:\nhttps://github.com/buildkite/test-collector-javascript/compare/v1.7.0...v1.7.1\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>","sha":"01df4b3b027992b8fc7a4a77040b6b91b8104702"}},"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/206164","number":206164,"mergeCommit":{"message":"Update dependency buildkite-test-collector to ^1.8.1 (main) (#206164)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [buildkite-test-collector](https://buildkite.com/platform/test-engine)\n([source](https://redirect.github.com/buildkite/test-collector-javascript))\n| devDependencies | minor | [`^1.7.0` ->\n`^1.8.1`](https://renovatebot.com/diffs/npm/buildkite-test-collector/1.7.0/1.8.1)\n|\n\n---\n\n### Release Notes\n\n<details>\n<summary>buildkite/test-collector-javascript\n(buildkite-test-collector)</summary>\n\n###\n[`v1.8.1`](https://redirect.github.com/buildkite/test-collector-javascript/releases/tag/v1.8.1)\n\n[Compare\nSource](https://redirect.github.com/buildkite/test-collector-javascript/compare/v1.8.0...v1.8.1)\n\n#### What's Changed\n\n- Bump axios from 1.6.8 to 1.8.2 by\n[@​dependabot](https://redirect.github.com/dependabot) in\n[https://github.com/buildkite/test-collector-javascript/pull/104](https://redirect.github.com/buildkite/test-collector-javascript/pull/104)\n\n#### Minor / internal changes\n\n- Test coverage for generic CI `run_env` by\n[@​pda](https://redirect.github.com/pda) in\n[https://github.com/buildkite/test-collector-javascript/pull/98](https://redirect.github.com/buildkite/test-collector-javascript/pull/98)\n- Analytics -> Engine renames by\n[@​wooly](https://redirect.github.com/wooly) in\n[https://github.com/buildkite/test-collector-javascript/pull/102](https://redirect.github.com/buildkite/test-collector-javascript/pull/102)\n\n#### New Contributors\n\n- [@​wooly](https://redirect.github.com/wooly) made their first\ncontribution in\n[https://github.com/buildkite/test-collector-javascript/pull/102](https://redirect.github.com/buildkite/test-collector-javascript/pull/102)\n- [@​dependabot](https://redirect.github.com/dependabot) made\ntheir first contribution in\n[https://github.com/buildkite/test-collector-javascript/pull/104](https://redirect.github.com/buildkite/test-collector-javascript/pull/104)\n\n**Full Changelog**:\nhttps://github.com/buildkite/test-collector-javascript/compare/v1.8.0...v1.8.1\n\n###\n[`v1.8.0`](https://redirect.github.com/buildkite/test-collector-javascript/releases/tag/v1.8.0)\n\n[Compare\nSource](https://redirect.github.com/buildkite/test-collector-javascript/compare/v1.7.3...v1.8.0)\n\n#### What's Changed\n\n- Introduce `tags` option by\n[@​pda](https://redirect.github.com/pda) in\n[https://github.com/buildkite/test-collector-javascript/pull/100](https://redirect.github.com/buildkite/test-collector-javascript/pull/100)\n\n##### Minor / house-keeping\n\n- playwright test server moved to less common port (8080 -> 18080) by\n[@​pda](https://redirect.github.com/pda) in\n[https://github.com/buildkite/test-collector-javascript/pull/99](https://redirect.github.com/buildkite/test-collector-javascript/pull/99)\n- Prepare v1.8.0 by [@​pda](https://redirect.github.com/pda) in\n[https://github.com/buildkite/test-collector-javascript/pull/101](https://redirect.github.com/buildkite/test-collector-javascript/pull/101)\n\n#### New Contributors\n\n- [@​pda](https://redirect.github.com/pda) made their first\ncontribution in\n[https://github.com/buildkite/test-collector-javascript/pull/99](https://redirect.github.com/buildkite/test-collector-javascript/pull/99)\n\n**Full Changelog**:\nhttps://github.com/buildkite/test-collector-javascript/compare/v1.7.3...v1.8.0\n\n###\n[`v1.7.3`](https://redirect.github.com/buildkite/test-collector-javascript/releases/tag/v1.7.3)\n\n[Compare\nSource](https://redirect.github.com/buildkite/test-collector-javascript/compare/v1.7.2...v1.7.3)\n\n#### What's Changed\n\n- Rescue errors from uploadTestResults by\n[@​nprizal](https://redirect.github.com/nprizal) in\n[https://github.com/buildkite/test-collector-javascript/pull/95](https://redirect.github.com/buildkite/test-collector-javascript/pull/95)\n\n**Full Changelog**:\nhttps://github.com/buildkite/test-collector-javascript/compare/v1.7.2...v1.7.3\n\n###\n[`v1.7.2`](https://redirect.github.com/buildkite/test-collector-javascript/releases/tag/v1.7.2)\n\n[Compare\nSource](https://redirect.github.com/buildkite/test-collector-javascript/compare/v1.7.1...v1.7.2)\n\n#### What's Changed\n\n- Run tests on a new queue by\n[@​yob](https://redirect.github.com/yob) in\n[https://github.com/buildkite/test-collector-javascript/pull/90](https://redirect.github.com/buildkite/test-collector-javascript/pull/90)\n- Fix async problem in jest reporter when trying to run `onRunComplete`\nby [@​JasonShin](https://redirect.github.com/JasonShin) in\n[https://github.com/buildkite/test-collector-javascript/pull/91](https://redirect.github.com/buildkite/test-collector-javascript/pull/91)\n- Release v1.7.2 by\n[@​nprizal](https://redirect.github.com/nprizal) in\n[https://github.com/buildkite/test-collector-javascript/pull/93](https://redirect.github.com/buildkite/test-collector-javascript/pull/93)\n\n#### New Contributors\n\n- [@​yob](https://redirect.github.com/yob) made their first\ncontribution in\n[https://github.com/buildkite/test-collector-javascript/pull/90](https://redirect.github.com/buildkite/test-collector-javascript/pull/90)\n- [@​JasonShin](https://redirect.github.com/JasonShin) made their\nfirst contribution in\n[https://github.com/buildkite/test-collector-javascript/pull/91](https://redirect.github.com/buildkite/test-collector-javascript/pull/91)\n\n**Full Changelog**:\nhttps://github.com/buildkite/test-collector-javascript/compare/v1.7.1...v1.7.2\n\n###\n[`v1.7.1`](https://redirect.github.com/buildkite/test-collector-javascript/releases/tag/v1.7.1)\n\n[Compare\nSource](https://redirect.github.com/buildkite/test-collector-javascript/compare/v1.7.0...v1.7.1)\n\n#### What's Changed\n\n- Bump axios from 1.6.2 to 1.6.8 to address CVE-2024-28849 by\n[@​gchan](https://redirect.github.com/gchan) in\n[https://github.com/buildkite/test-collector-javascript/pull/88](https://redirect.github.com/buildkite/test-collector-javascript/pull/88)\n\n**Full Changelog**:\nhttps://github.com/buildkite/test-collector-javascript/compare/v1.7.0...v1.7.1\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>","sha":"01df4b3b027992b8fc7a4a77040b6b91b8104702"}},{"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: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
Steph Milovic
|
1fa72211b6
|
[9.0] [Security Assistant] Improve error telemetry (#220938) (#221053)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Assistant] Improve error telemetry (#220938)](https://github.com/elastic/kibana/pull/220938) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-05-20T20:15:03Z","message":"[Security Assistant] Improve error telemetry (#220938)","sha":"7149e3edfbcd3d3272ea9efac8043a1d104e0cc1","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0","ci:security-genai-run-evals","v8.18.2","v9.0.2"],"title":"[Security Assistant] Improve error telemetry","number":220938,"url":"https://github.com/elastic/kibana/pull/220938","mergeCommit":{"message":"[Security Assistant] Improve error telemetry (#220938)","sha":"7149e3edfbcd3d3272ea9efac8043a1d104e0cc1"}},"sourceBranch":"main","suggestedTargetBranches":["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/220938","number":220938,"mergeCommit":{"message":"[Security Assistant] Improve error telemetry (#220938)","sha":"7149e3edfbcd3d3272ea9efac8043a1d104e0cc1"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/221052","number":221052,"state":"OPEN"},{"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--> |
||
|
Kibana Machine
|
aedd846efc
|
[9.0] Update dependency diff to v8 (main) (#220898) (#220946)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency diff to v8 (main) (#220898)](https://github.com/elastic/kibana/pull/220898) <!--- 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-05-20T04:05:23Z","message":"Update dependency diff to v8 (main) (#220898)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change | Pending |\n|---|---|---|---|---|\n| [diff](https://redirect.github.com/kpdecker/jsdiff) | dependencies |\nmajor | [`^7.0.0` ->\n`^8.0.0`](https://renovatebot.com/diffs/npm/diff/7.0.0/8.0.0) | `8.0.1`\n|\n\n---\n\n### Release Notes\n\n<details>\n<summary>kpdecker/jsdiff (diff)</summary>\n\n###\n[`v8.0.0`](https://redirect.github.com/kpdecker/jsdiff/blob/HEAD/release-notes.md#800)\n\n[Compare\nSource](https://redirect.github.com/kpdecker/jsdiff/compare/7.0.0...v8.0.0)\n\n- [#​580](https://redirect.github.com/kpdecker/jsdiff/pull/580)\n**Multiple tweaks to `diffSentences`**:\n- tokenization no longer takes quadratic time on pathological inputs\n(reported as a ReDOS vulnerability by Snyk); is now linear instead\n- the final sentence in the string is now handled the same by the\ntokenizer regardless of whether it has a trailing punctuation mark or\nnot. (Previously, \"foo. bar.\" tokenized to `[\"foo.\", \" \", \"bar.\"]` but\n\"foo. bar\" tokenized to `[\"foo.\", \" bar\"]` - i.e. whether the space\nbetween sentences was treated as a separate token depended upon whether\nthe final sentence had trailing punctuation or not. This was arbitrary\nand surprising; it is no longer the case.)\n- in a string that starts with a sentence end, like \"! hello.\", the \"!\"\nis now treated as a separate sentence\n- the README now correctly documents the tokenization behaviour (it was\nwrong before)\n- [#​581](https://redirect.github.com/kpdecker/jsdiff/pull/581) -\n**fixed some regex operations used for tokenization in `diffWords`\ntaking O(n^2) time** in pathological cases\n- [#​595](https://redirect.github.com/kpdecker/jsdiff/pull/595) -\n**fixed a crash in patch creation functions when handling a single hunk\nconsisting of a very large number (e.g. >130k) of lines**. (This was\ncaused by spreading indefinitely-large arrays to `.push()` using\n`.apply` or the spread operator and hitting the\nJS-implementation-specific limit on the maximum number of arguments to a\nfunction, as shown at https://stackoverflow.com/a/56809779/1709587; thus\nthe exact threshold to hit the error will depend on the environment in\nwhich you were running JsDiff.)\n- [#​596](https://redirect.github.com/kpdecker/jsdiff/pull/596) -\n**removed the `merge` function**. Previously JsDiff included an\nundocumented function called `merge` that was meant to, in some sense,\nmerge patches. It had at least a couple of serious bugs that could lead\nto it returning unambiguously wrong results, and it was difficult to\nsimply \"fix\" because it was [unclear precisely what it was meant to\ndo](https://redirect.github.com/kpdecker/jsdiff/issues/181#issuecomment-2198319542).\nFor now, the fix is to remove it entirely.\n- [#​591](https://redirect.github.com/kpdecker/jsdiff/pull/591) -\nJsDiff's source code has been rewritten in TypeScript. This change\nentails the following changes for end users:\n- **the `diff` package on npm now includes its own TypeScript type\ndefinitions**. Users who previously used the `@types/diff` npm package\nfrom DefinitelyTyped should remove that dependency when upgrading JsDiff\nto v8.\n\nNote that the transition from the DefinitelyTyped types to JsDiff's own\ntype definitions includes multiple fixes and also removes many exported\ntypes previously used for `options` arguments to diffing and\npatch-generation functions. (There are now different exported options\ntypes for abortable calls - ones with a `timeout` or `maxEditLength`\nthat may give a result of `undefined` - and non-abortable calls.) See\nthe TypeScript section of the README for some usage tips.\n\n- **The `Diff` object is now a class**. Custom extensions of `Diff`, as\ndescribed in the \"Defining custom diffing behaviors\" section of the\nREADME, can therefore now be done by writing a `class CustomDiff extends\nDiff` and overriding methods, instead of the old way based on prototype\ninheritance. (I *think* code that did things the old way should still\nwork, though!)\n\n- **`diff/lib/index.es6.js` and `diff/lib/index.mjs` no longer exist,\nand the ESM version of the library is no longer bundled into a single\nfile.**\n\n- **The `ignoreWhitespace` option for `diffWords` is no longer included\nin the type declarations**. The effect of passing `ignoreWhitespace:\ntrue` has always been to make `diffWords` just call `diffWordsWithSpace`\ninstead, which was confusing, because that behaviour doesn't seem\nproperly described as \"ignoring\" whitespace at all. The property remains\navailable to non-TypeScript applications for the sake of backwards\ncompatability, but TypeScript applications will now see a type error if\nthey try to pass `ignoreWhitespace: true` to `diffWords` and should\nchange their code to call `diffWordsWithSpace` instead.\n\n- JsDiff no longer purports to support ES3 environments. (I'm pretty\nsure it never truly did, despite claiming to in its README, since even\nthe 1.0.0 release used `Array.map` which was added in ES5.)\n- [#​601](https://redirect.github.com/kpdecker/jsdiff/pull/601) -\n**`diffJson`'s `stringifyReplacer` option behaves more like\n`JSON.stringify`'s `replacer` argument now.** In particular:\n- Each key/value pair now gets passed through the replacer once instead\nof twice\n- The `key` passed to the replacer when the top-level object is passed\nin as `value` is now `\"\"` (previously, was `undefined`), and the `key`\npassed with an array element is the array index as a string, like `\"0\"`\nor `\"1\"` (previously was whatever the key for the entire array was).\nBoth the new behaviours match that of `JSON.stringify`.\n- [#​602](https://redirect.github.com/kpdecker/jsdiff/pull/602) -\n**diffing functions now consistently return `undefined` when called in\nasync mode** (i.e. with a callback). Previously, there was an odd quirk\nwhere they would return `true` if the strings being diffed were equal\nand `undefined` otherwise.\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\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Davis McPhee <davis.mcphee@elastic.co>","sha":"dbd586662598348af0c193b354f3317bed835751","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:DataDiscovery","backport:all-open","v9.1.0"],"title":"Update dependency diff to v8 (main)","number":220898,"url":"https://github.com/elastic/kibana/pull/220898","mergeCommit":{"message":"Update dependency diff to v8 (main) (#220898)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change | Pending |\n|---|---|---|---|---|\n| [diff](https://redirect.github.com/kpdecker/jsdiff) | dependencies |\nmajor | [`^7.0.0` ->\n`^8.0.0`](https://renovatebot.com/diffs/npm/diff/7.0.0/8.0.0) | `8.0.1`\n|\n\n---\n\n### Release Notes\n\n<details>\n<summary>kpdecker/jsdiff (diff)</summary>\n\n###\n[`v8.0.0`](https://redirect.github.com/kpdecker/jsdiff/blob/HEAD/release-notes.md#800)\n\n[Compare\nSource](https://redirect.github.com/kpdecker/jsdiff/compare/7.0.0...v8.0.0)\n\n- [#​580](https://redirect.github.com/kpdecker/jsdiff/pull/580)\n**Multiple tweaks to `diffSentences`**:\n- tokenization no longer takes quadratic time on pathological inputs\n(reported as a ReDOS vulnerability by Snyk); is now linear instead\n- the final sentence in the string is now handled the same by the\ntokenizer regardless of whether it has a trailing punctuation mark or\nnot. (Previously, \"foo. bar.\" tokenized to `[\"foo.\", \" \", \"bar.\"]` but\n\"foo. bar\" tokenized to `[\"foo.\", \" bar\"]` - i.e. whether the space\nbetween sentences was treated as a separate token depended upon whether\nthe final sentence had trailing punctuation or not. This was arbitrary\nand surprising; it is no longer the case.)\n- in a string that starts with a sentence end, like \"! hello.\", the \"!\"\nis now treated as a separate sentence\n- the README now correctly documents the tokenization behaviour (it was\nwrong before)\n- [#​581](https://redirect.github.com/kpdecker/jsdiff/pull/581) -\n**fixed some regex operations used for tokenization in `diffWords`\ntaking O(n^2) time** in pathological cases\n- [#​595](https://redirect.github.com/kpdecker/jsdiff/pull/595) -\n**fixed a crash in patch creation functions when handling a single hunk\nconsisting of a very large number (e.g. >130k) of lines**. (This was\ncaused by spreading indefinitely-large arrays to `.push()` using\n`.apply` or the spread operator and hitting the\nJS-implementation-specific limit on the maximum number of arguments to a\nfunction, as shown at https://stackoverflow.com/a/56809779/1709587; thus\nthe exact threshold to hit the error will depend on the environment in\nwhich you were running JsDiff.)\n- [#​596](https://redirect.github.com/kpdecker/jsdiff/pull/596) -\n**removed the `merge` function**. Previously JsDiff included an\nundocumented function called `merge` that was meant to, in some sense,\nmerge patches. It had at least a couple of serious bugs that could lead\nto it returning unambiguously wrong results, and it was difficult to\nsimply \"fix\" because it was [unclear precisely what it was meant to\ndo](https://redirect.github.com/kpdecker/jsdiff/issues/181#issuecomment-2198319542).\nFor now, the fix is to remove it entirely.\n- [#​591](https://redirect.github.com/kpdecker/jsdiff/pull/591) -\nJsDiff's source code has been rewritten in TypeScript. This change\nentails the following changes for end users:\n- **the `diff` package on npm now includes its own TypeScript type\ndefinitions**. Users who previously used the `@types/diff` npm package\nfrom DefinitelyTyped should remove that dependency when upgrading JsDiff\nto v8.\n\nNote that the transition from the DefinitelyTyped types to JsDiff's own\ntype definitions includes multiple fixes and also removes many exported\ntypes previously used for `options` arguments to diffing and\npatch-generation functions. (There are now different exported options\ntypes for abortable calls - ones with a `timeout` or `maxEditLength`\nthat may give a result of `undefined` - and non-abortable calls.) See\nthe TypeScript section of the README for some usage tips.\n\n- **The `Diff` object is now a class**. Custom extensions of `Diff`, as\ndescribed in the \"Defining custom diffing behaviors\" section of the\nREADME, can therefore now be done by writing a `class CustomDiff extends\nDiff` and overriding methods, instead of the old way based on prototype\ninheritance. (I *think* code that did things the old way should still\nwork, though!)\n\n- **`diff/lib/index.es6.js` and `diff/lib/index.mjs` no longer exist,\nand the ESM version of the library is no longer bundled into a single\nfile.**\n\n- **The `ignoreWhitespace` option for `diffWords` is no longer included\nin the type declarations**. The effect of passing `ignoreWhitespace:\ntrue` has always been to make `diffWords` just call `diffWordsWithSpace`\ninstead, which was confusing, because that behaviour doesn't seem\nproperly described as \"ignoring\" whitespace at all. The property remains\navailable to non-TypeScript applications for the sake of backwards\ncompatability, but TypeScript applications will now see a type error if\nthey try to pass `ignoreWhitespace: true` to `diffWords` and should\nchange their code to call `diffWordsWithSpace` instead.\n\n- JsDiff no longer purports to support ES3 environments. (I'm pretty\nsure it never truly did, despite claiming to in its README, since even\nthe 1.0.0 release used `Array.map` which was added in ES5.)\n- [#​601](https://redirect.github.com/kpdecker/jsdiff/pull/601) -\n**`diffJson`'s `stringifyReplacer` option behaves more like\n`JSON.stringify`'s `replacer` argument now.** In particular:\n- Each key/value pair now gets passed through the replacer once instead\nof twice\n- The `key` passed to the replacer when the top-level object is passed\nin as `value` is now `\"\"` (previously, was `undefined`), and the `key`\npassed with an array element is the array index as a string, like `\"0\"`\nor `\"1\"` (previously was whatever the key for the entire array was).\nBoth the new behaviours match that of `JSON.stringify`.\n- [#​602](https://redirect.github.com/kpdecker/jsdiff/pull/602) -\n**diffing functions now consistently return `undefined` when called in\nasync mode** (i.e. with a callback). Previously, there was an odd quirk\nwhere they would return `true` if the strings being diffed were equal\nand `undefined` otherwise.\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\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Davis McPhee <davis.mcphee@elastic.co>","sha":"dbd586662598348af0c193b354f3317bed835751"}},"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/220898","number":220898,"mergeCommit":{"message":"Update dependency diff to v8 (main) (#220898)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change | Pending |\n|---|---|---|---|---|\n| [diff](https://redirect.github.com/kpdecker/jsdiff) | dependencies |\nmajor | [`^7.0.0` ->\n`^8.0.0`](https://renovatebot.com/diffs/npm/diff/7.0.0/8.0.0) | `8.0.1`\n|\n\n---\n\n### Release Notes\n\n<details>\n<summary>kpdecker/jsdiff (diff)</summary>\n\n###\n[`v8.0.0`](https://redirect.github.com/kpdecker/jsdiff/blob/HEAD/release-notes.md#800)\n\n[Compare\nSource](https://redirect.github.com/kpdecker/jsdiff/compare/7.0.0...v8.0.0)\n\n- [#​580](https://redirect.github.com/kpdecker/jsdiff/pull/580)\n**Multiple tweaks to `diffSentences`**:\n- tokenization no longer takes quadratic time on pathological inputs\n(reported as a ReDOS vulnerability by Snyk); is now linear instead\n- the final sentence in the string is now handled the same by the\ntokenizer regardless of whether it has a trailing punctuation mark or\nnot. (Previously, \"foo. bar.\" tokenized to `[\"foo.\", \" \", \"bar.\"]` but\n\"foo. bar\" tokenized to `[\"foo.\", \" bar\"]` - i.e. whether the space\nbetween sentences was treated as a separate token depended upon whether\nthe final sentence had trailing punctuation or not. This was arbitrary\nand surprising; it is no longer the case.)\n- in a string that starts with a sentence end, like \"! hello.\", the \"!\"\nis now treated as a separate sentence\n- the README now correctly documents the tokenization behaviour (it was\nwrong before)\n- [#​581](https://redirect.github.com/kpdecker/jsdiff/pull/581) -\n**fixed some regex operations used for tokenization in `diffWords`\ntaking O(n^2) time** in pathological cases\n- [#​595](https://redirect.github.com/kpdecker/jsdiff/pull/595) -\n**fixed a crash in patch creation functions when handling a single hunk\nconsisting of a very large number (e.g. >130k) of lines**. (This was\ncaused by spreading indefinitely-large arrays to `.push()` using\n`.apply` or the spread operator and hitting the\nJS-implementation-specific limit on the maximum number of arguments to a\nfunction, as shown at https://stackoverflow.com/a/56809779/1709587; thus\nthe exact threshold to hit the error will depend on the environment in\nwhich you were running JsDiff.)\n- [#​596](https://redirect.github.com/kpdecker/jsdiff/pull/596) -\n**removed the `merge` function**. Previously JsDiff included an\nundocumented function called `merge` that was meant to, in some sense,\nmerge patches. It had at least a couple of serious bugs that could lead\nto it returning unambiguously wrong results, and it was difficult to\nsimply \"fix\" because it was [unclear precisely what it was meant to\ndo](https://redirect.github.com/kpdecker/jsdiff/issues/181#issuecomment-2198319542).\nFor now, the fix is to remove it entirely.\n- [#​591](https://redirect.github.com/kpdecker/jsdiff/pull/591) -\nJsDiff's source code has been rewritten in TypeScript. This change\nentails the following changes for end users:\n- **the `diff` package on npm now includes its own TypeScript type\ndefinitions**. Users who previously used the `@types/diff` npm package\nfrom DefinitelyTyped should remove that dependency when upgrading JsDiff\nto v8.\n\nNote that the transition from the DefinitelyTyped types to JsDiff's own\ntype definitions includes multiple fixes and also removes many exported\ntypes previously used for `options` arguments to diffing and\npatch-generation functions. (There are now different exported options\ntypes for abortable calls - ones with a `timeout` or `maxEditLength`\nthat may give a result of `undefined` - and non-abortable calls.) See\nthe TypeScript section of the README for some usage tips.\n\n- **The `Diff` object is now a class**. Custom extensions of `Diff`, as\ndescribed in the \"Defining custom diffing behaviors\" section of the\nREADME, can therefore now be done by writing a `class CustomDiff extends\nDiff` and overriding methods, instead of the old way based on prototype\ninheritance. (I *think* code that did things the old way should still\nwork, though!)\n\n- **`diff/lib/index.es6.js` and `diff/lib/index.mjs` no longer exist,\nand the ESM version of the library is no longer bundled into a single\nfile.**\n\n- **The `ignoreWhitespace` option for `diffWords` is no longer included\nin the type declarations**. The effect of passing `ignoreWhitespace:\ntrue` has always been to make `diffWords` just call `diffWordsWithSpace`\ninstead, which was confusing, because that behaviour doesn't seem\nproperly described as \"ignoring\" whitespace at all. The property remains\navailable to non-TypeScript applications for the sake of backwards\ncompatability, but TypeScript applications will now see a type error if\nthey try to pass `ignoreWhitespace: true` to `diffWords` and should\nchange their code to call `diffWordsWithSpace` instead.\n\n- JsDiff no longer purports to support ES3 environments. (I'm pretty\nsure it never truly did, despite claiming to in its README, since even\nthe 1.0.0 release used `Array.map` which was added in ES5.)\n- [#​601](https://redirect.github.com/kpdecker/jsdiff/pull/601) -\n**`diffJson`'s `stringifyReplacer` option behaves more like\n`JSON.stringify`'s `replacer` argument now.** In particular:\n- Each key/value pair now gets passed through the replacer once instead\nof twice\n- The `key` passed to the replacer when the top-level object is passed\nin as `value` is now `\"\"` (previously, was `undefined`), and the `key`\npassed with an array element is the array index as a string, like `\"0\"`\nor `\"1\"` (previously was whatever the key for the entire array was).\nBoth the new behaviours match that of `JSON.stringify`.\n- [#​602](https://redirect.github.com/kpdecker/jsdiff/pull/602) -\n**diffing functions now consistently return `undefined` when called in\nasync mode** (i.e. with a callback). Previously, there was an odd quirk\nwhere they would return `true` if the strings being diffed were equal\nand `undefined` otherwise.\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\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Davis McPhee <davis.mcphee@elastic.co>","sha":"dbd586662598348af0c193b354f3317bed835751"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Davis McPhee <davis.mcphee@elastic.co> |
||
|
Kibana Machine
|
e026743785
|
[9.0] fix: [Security:Cases:Create page]Modal dialogs missing title from announcement (#220756) (#220986)
# Backport This will backport the following commits from `main` to `9.0`: - [fix: [Security:Cases:Create page]Modal dialogs missing title from announcement (#220756)](https://github.com/elastic/kibana/pull/220756) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-05-20T10:00:56Z","message":"fix: [Security:Cases:Create page]Modal dialogs missing title from announcement (#220756)\n\nPart of: #205615\n\n> [!IMPORTANT]\n> `Syntax help` part will be fixed in the `elastic/eui` repo \n\n## Changes made: \n\n1. Added required **a11y** attributes for for `EuiConfirmModal`\n\n\n## Screen: \n\n<img width=\"1516\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/29622975-864c-4927-892a-956f17002d8d\"\n/>","sha":"ed56c63420cdcc139880960ca4617d942eb682a4","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","backport:prev-minor","v9.1.0"],"title":"fix: [Security:Cases:Create page]Modal dialogs missing title from announcement","number":220756,"url":"https://github.com/elastic/kibana/pull/220756","mergeCommit":{"message":"fix: [Security:Cases:Create page]Modal dialogs missing title from announcement (#220756)\n\nPart of: #205615\n\n> [!IMPORTANT]\n> `Syntax help` part will be fixed in the `elastic/eui` repo \n\n## Changes made: \n\n1. Added required **a11y** attributes for for `EuiConfirmModal`\n\n\n## Screen: \n\n<img width=\"1516\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/29622975-864c-4927-892a-956f17002d8d\"\n/>","sha":"ed56c63420cdcc139880960ca4617d942eb682a4"}},"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/220756","number":220756,"mergeCommit":{"message":"fix: [Security:Cases:Create page]Modal dialogs missing title from announcement (#220756)\n\nPart of: #205615\n\n> [!IMPORTANT]\n> `Syntax help` part will be fixed in the `elastic/eui` repo \n\n## Changes made: \n\n1. Added required **a11y** attributes for for `EuiConfirmModal`\n\n\n## Screen: \n\n<img width=\"1516\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/29622975-864c-4927-892a-956f17002d8d\"\n/>","sha":"ed56c63420cdcc139880960ca4617d942eb682a4"}},{"url":"https://github.com/elastic/kibana/pull/220978","number":220978,"branch":"8.18","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/220979","number":220979,"branch":"8.19","state":"OPEN"}]}] BACKPORT--> Co-authored-by: Alexey Antonov <alexwizp@gmail.com> |
||
|
Kibana Machine
|
e24e83dd13
|
[9.0] [Data Views] Do not return failed cached requests from dataViews.create (#220934) (#220961)
# Backport This will backport the following commits from `main` to `9.0`: - [[Data Views] Do not return failed cached requests from `dataViews.create` (#220934)](https://github.com/elastic/kibana/pull/220934) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lukas Olson","email":"lukas@elastic.co"},"sourceCommit":{"committedDate":"2025-05-20T08:17:35Z","message":"[Data Views] Do not return failed cached requests from `dataViews.create` (#220934)\n\nPreviously, `dataViews.create` could return a rejected promise from the cache when a prior HTTP request failed. Now we `await` the cached `dataViewPromise` before returning, ensuring that `create` never propagates a failed HTTP promise.\n\nThis preserves the cache behavior for simultaneous `get` calls—avoiding redundant HTTP requests—while guaranteeing that `create` replaces any failed promise in the cache with the result of a fresh, successful create operation.\n\n- Ensures `dataViews.create` doesn’t return failed promises\n- Maintains caching goals by awaiting the cached promise rather than conditionally caching only on success\n- Updates unit/functional tests to cover simultaneous `get` + subsequent `create` scenarios","sha":"b3911213f8d005af1b95d8d2fe3453640e717ffa","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Data Views","release_note:skip","Team:DataDiscovery","backport:all-open","v9.1.0"],"title":"[Data Views] Do not return failed cached requests from `dataViews.create`","number":220934,"url":"https://github.com/elastic/kibana/pull/220934","mergeCommit":{"message":"[Data Views] Do not return failed cached requests from `dataViews.create` (#220934)\n\nPreviously, `dataViews.create` could return a rejected promise from the cache when a prior HTTP request failed. Now we `await` the cached `dataViewPromise` before returning, ensuring that `create` never propagates a failed HTTP promise.\n\nThis preserves the cache behavior for simultaneous `get` calls—avoiding redundant HTTP requests—while guaranteeing that `create` replaces any failed promise in the cache with the result of a fresh, successful create operation.\n\n- Ensures `dataViews.create` doesn’t return failed promises\n- Maintains caching goals by awaiting the cached promise rather than conditionally caching only on success\n- Updates unit/functional tests to cover simultaneous `get` + subsequent `create` scenarios","sha":"b3911213f8d005af1b95d8d2fe3453640e717ffa"}},"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/220934","number":220934,"mergeCommit":{"message":"[Data Views] Do not return failed cached requests from `dataViews.create` (#220934)\n\nPreviously, `dataViews.create` could return a rejected promise from the cache when a prior HTTP request failed. Now we `await` the cached `dataViewPromise` before returning, ensuring that `create` never propagates a failed HTTP promise.\n\nThis preserves the cache behavior for simultaneous `get` calls—avoiding redundant HTTP requests—while guaranteeing that `create` replaces any failed promise in the cache with the result of a fresh, successful create operation.\n\n- Ensures `dataViews.create` doesn’t return failed promises\n- Maintains caching goals by awaiting the cached promise rather than conditionally caching only on success\n- Updates unit/functional tests to cover simultaneous `get` + subsequent `create` scenarios","sha":"b3911213f8d005af1b95d8d2fe3453640e717ffa"}}]}] BACKPORT--> Co-authored-by: Lukas Olson <lukas@elastic.co> |
||
|
Kibana Machine
|
ef12ea76d7
|
[9.0] [Oblt Onboarding][Auto Detect] Handle Agent's DEGRADED state (#220527) (#221021)
# Backport This will backport the following commits from `main` to `9.0`: - [[Oblt Onboarding][Auto Detect] Handle Agent's DEGRADED state (#220527)](https://github.com/elastic/kibana/pull/220527) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2025-05-20T15:39:42Z","message":"[Oblt Onboarding][Auto Detect] Handle Agent's DEGRADED state (#220527)\n\nCloses https://github.com/elastic/observability-dev/issues/4505\n\nThis change updates the logic for Auto Detect flow to handle `DEGRADED`\nstate reported by Elastic Agent.\n\n## Context\nPreviously, if any of the the configured data streams were in a degraded\nstate, we would report to the user that the flow has failed even though\nsome data streams might be healthy and even send the data, and Kibana in\nturn would never check for incoming data and wouldn't report any\nadditional telemetry events.\n\nAdditionally, if user installs any of the integrations that require\nfurther configuration (e.g. MySQL or Postgres) they would be guarantied\nto be in a degraded state because Fleet API provides configuration for\nmetrics data streams and they require login and password.\n\nThis change makes handling degraded state more optimistic. If there is\nat least one data stream in a `HEALTHY` state, we're now reporting a\nsuccessful status of the whole flow to the user. Additional, we're\nshowing status of the unhealthy data stream as a separate message if\nthere are any (see screenshots). We report the whole flow as failed only\nwhen none of the data streams are healthy.\n\n| All data streams healthy | Some data streams degraded |\n| --- | --- |\n| \n| \n|\n\n\n## How to test\n\nGo through the Auto Detect flow once with integrations that don't\nrequire additional configuration (e.g. System, Nginx) and another time\nwith something like MySQL or Postgres. Make sure that everything works\nas expected and messages from the script make sense.\n\nCo-authored-by: Joe Reuter <johannes.reuter@elastic.co>","sha":"239162df723bc7e1cab386252220a5b34db6d0f2","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","ci:project-deploy-observability","Feature: Observability Onboarding","backport:version","v9.1.0","v8.19.0","v8.18.2","v9.0.2"],"title":"[Oblt Onboarding][Auto Detect] Handle Agent's DEGRADED state","number":220527,"url":"https://github.com/elastic/kibana/pull/220527","mergeCommit":{"message":"[Oblt Onboarding][Auto Detect] Handle Agent's DEGRADED state (#220527)\n\nCloses https://github.com/elastic/observability-dev/issues/4505\n\nThis change updates the logic for Auto Detect flow to handle `DEGRADED`\nstate reported by Elastic Agent.\n\n## Context\nPreviously, if any of the the configured data streams were in a degraded\nstate, we would report to the user that the flow has failed even though\nsome data streams might be healthy and even send the data, and Kibana in\nturn would never check for incoming data and wouldn't report any\nadditional telemetry events.\n\nAdditionally, if user installs any of the integrations that require\nfurther configuration (e.g. MySQL or Postgres) they would be guarantied\nto be in a degraded state because Fleet API provides configuration for\nmetrics data streams and they require login and password.\n\nThis change makes handling degraded state more optimistic. If there is\nat least one data stream in a `HEALTHY` state, we're now reporting a\nsuccessful status of the whole flow to the user. Additional, we're\nshowing status of the unhealthy data stream as a separate message if\nthere are any (see screenshots). We report the whole flow as failed only\nwhen none of the data streams are healthy.\n\n| All data streams healthy | Some data streams degraded |\n| --- | --- |\n| \n| \n|\n\n\n## How to test\n\nGo through the Auto Detect flow once with integrations that don't\nrequire additional configuration (e.g. System, Nginx) and another time\nwith something like MySQL or Postgres. Make sure that everything works\nas expected and messages from the script make sense.\n\nCo-authored-by: Joe Reuter <johannes.reuter@elastic.co>","sha":"239162df723bc7e1cab386252220a5b34db6d0f2"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","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/220527","number":220527,"mergeCommit":{"message":"[Oblt Onboarding][Auto Detect] Handle Agent's DEGRADED state (#220527)\n\nCloses https://github.com/elastic/observability-dev/issues/4505\n\nThis change updates the logic for Auto Detect flow to handle `DEGRADED`\nstate reported by Elastic Agent.\n\n## Context\nPreviously, if any of the the configured data streams were in a degraded\nstate, we would report to the user that the flow has failed even though\nsome data streams might be healthy and even send the data, and Kibana in\nturn would never check for incoming data and wouldn't report any\nadditional telemetry events.\n\nAdditionally, if user installs any of the integrations that require\nfurther configuration (e.g. MySQL or Postgres) they would be guarantied\nto be in a degraded state because Fleet API provides configuration for\nmetrics data streams and they require login and password.\n\nThis change makes handling degraded state more optimistic. If there is\nat least one data stream in a `HEALTHY` state, we're now reporting a\nsuccessful status of the whole flow to the user. Additional, we're\nshowing status of the unhealthy data stream as a separate message if\nthere are any (see screenshots). We report the whole flow as failed only\nwhen none of the data streams are healthy.\n\n| All data streams healthy | Some data streams degraded |\n| --- | --- |\n| \n| \n|\n\n\n## How to test\n\nGo through the Auto Detect flow once with integrations that don't\nrequire additional configuration (e.g. System, Nginx) and another time\nwith something like MySQL or Postgres. Make sure that everything works\nas expected and messages from the script make sense.\n\nCo-authored-by: Joe Reuter <johannes.reuter@elastic.co>","sha":"239162df723bc7e1cab386252220a5b34db6d0f2"}},{"branch":"8.19","label":"v8.19.0","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: Mykola Harmash <mykola.harmash@gmail.com> Co-authored-by: Joe Reuter <johannes.reuter@elastic.co> |
||
|
Kibana Machine
|
1846e0f44e | skip failing test suite (#220822) | ||
|
Kibana Machine
|
e89549babc | skip failing test suite (#199905) | ||
|
Kibana Machine
|
a6d573870b | skip failing test suite (#213784) | ||
|
Kibana Machine
|
13cb0f8e97
|
[9.0] [Docs] Add Kibana Accessibility statement page (#220997) (#221005)
# Backport This will backport the following commits from `main` to `9.0`: - [[Docs] Add Kibana Accessibility statement page (#220997)](https://github.com/elastic/kibana/pull/220997) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"florent-leborgne","email":"florent.leborgne@elastic.co"},"sourceCommit":{"committedDate":"2025-05-20T14:11:48Z","message":"[Docs] Add Kibana Accessibility statement page (#220997)\n\nThis PR re-makes the Kibana accessibility statement page its own page to\nease sharing.","sha":"0ce0f65f491cbd24ddf9d5db42a9b3d7c96b834c","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","backport:version","v9.1.0","v9.0.2"],"title":"[Docs] Add Kibana Accessibility statement page","number":220997,"url":"https://github.com/elastic/kibana/pull/220997","mergeCommit":{"message":"[Docs] Add Kibana Accessibility statement page (#220997)\n\nThis PR re-makes the Kibana accessibility statement page its own page to\nease sharing.","sha":"0ce0f65f491cbd24ddf9d5db42a9b3d7c96b834c"}},"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/220997","number":220997,"mergeCommit":{"message":"[Docs] Add Kibana Accessibility statement page (#220997)\n\nThis PR re-makes the Kibana accessibility statement page its own page to\nease sharing.","sha":"0ce0f65f491cbd24ddf9d5db42a9b3d7c96b834c"}},{"branch":"9.0","label":"v9.0.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> |
||
Ersin Erdal
|
01973c0886
|
[9.0] Alerts created within a Maintenance Windows trigger actions after the MW expires (#219797) (#220935)
# Backport This will backport the following commits from `main` to `9.0`: - [Alerts created within a Maintenance Windows trigger actions after the MW expires (#219797)](https://github.com/elastic/kibana/pull/219797) <!--- Backport version: 9.6.6 --> ### 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-05T23:26:43Z","message":"Alerts created within a Maintenance Windows trigger actions after the MW expires (#219797)\n\nResolves: #215634\n\nThis PR removes the expired maintenance window ids from the\n`alert.meta.maintenanceWindowIds` list of the active and the recovered\nalerts.\nSo the actions for those alerts would be triggered once the MW expires.\n\n## To verify:\nCreate a Maintenance Window that lasts a couple of minutes.\nCreate a rule that generates an alert.\nActions for the alert should not be triggered while the MW is active.\nWait for the MW to expire, an action for the alert should be triggered\nfor the alert.\nChange the rule to make the alert recovered, a recevored action for the\nalert should be triggered as well.\n\nCreate another MW with a filter.\nDo the same tests with an action with `summary-of-alerts` config.\nNote: [this PR](https://github.com/elastic/kibana/pull/219793) should be\nmerged to be able to test an MW with filters.","sha":"b748de163e79a79ddbad7354fbd71e41276b2303","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:ResponseOps","backport:version","v9.1.0","v8.19.0","v8.17.7","v8.18.2","v9.0.2"],"title":"Alerts created within a Maintenance Windows trigger actions after the MW expires","number":219797,"url":"https://github.com/elastic/kibana/pull/219797","mergeCommit":{"message":"Alerts created within a Maintenance Windows trigger actions after the MW expires (#219797)\n\nResolves: #215634\n\nThis PR removes the expired maintenance window ids from the\n`alert.meta.maintenanceWindowIds` list of the active and the recovered\nalerts.\nSo the actions for those alerts would be triggered once the MW expires.\n\n## To verify:\nCreate a Maintenance Window that lasts a couple of minutes.\nCreate a rule that generates an alert.\nActions for the alert should not be triggered while the MW is active.\nWait for the MW to expire, an action for the alert should be triggered\nfor the alert.\nChange the rule to make the alert recovered, a recevored action for the\nalert should be triggered as well.\n\nCreate another MW with a filter.\nDo the same tests with an action with `summary-of-alerts` config.\nNote: [this PR](https://github.com/elastic/kibana/pull/219793) should be\nmerged to be able to test an MW with filters.","sha":"b748de163e79a79ddbad7354fbd71e41276b2303"}},"sourceBranch":"main","suggestedTargetBranches":["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/219797","number":219797,"mergeCommit":{"message":"Alerts created within a Maintenance Windows trigger actions after the MW expires (#219797)\n\nResolves: #215634\n\nThis PR removes the expired maintenance window ids from the\n`alert.meta.maintenanceWindowIds` list of the active and the recovered\nalerts.\nSo the actions for those alerts would be triggered once the MW expires.\n\n## To verify:\nCreate a Maintenance Window that lasts a couple of minutes.\nCreate a rule that generates an alert.\nActions for the alert should not be triggered while the MW is active.\nWait for the MW to expire, an action for the alert should be triggered\nfor the alert.\nChange the rule to make the alert recovered, a recevored action for the\nalert should be triggered as well.\n\nCreate another MW with a filter.\nDo the same tests with an action with `summary-of-alerts` config.\nNote: [this PR](https://github.com/elastic/kibana/pull/219793) should be\nmerged to be able to test an MW with filters.","sha":"b748de163e79a79ddbad7354fbd71e41276b2303"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/220177","number":220177,"state":"MERGED","mergeCommit":{"sha":"ade3f8fc875061b324359198fad0b5d41625c2a1","message":"[8.19] Alerts created within a Maintenance Windows trigger actions after the MW expires (#219797) (#220177)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [Alerts created within a Maintenance Windows trigger actions after the\nMW expires (#219797)](https://github.com/elastic/kibana/pull/219797)\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--> |
||
|
Kibana Machine
|
966c70fa78
|
[9.0] [Docs] Add behavioral analytics removal to Kibana 9.0 breaking changes (#220906) (#220969)
# Backport This will backport the following commits from `main` to `9.0`: - [[Docs] Add behavioral analytics removal to Kibana 9.0 breaking changes (#220906)](https://github.com/elastic/kibana/pull/220906) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"florent-leborgne","email":"florent.leborgne@elastic.co"},"sourceCommit":{"committedDate":"2025-05-20T09:00:55Z","message":"[Docs] Add behavioral analytics removal to Kibana 9.0 breaking changes (#220906)\n\nBehavioral analytics was hidden from the UI and its associated APIs were\ndeprecated in 9.0, but only the API deprecation was called out in\nElasticseach release notes. This PR addresses the UI communication gap\nby adding a mention to the 9.0 breaking changes (while it's technically\na deprecation, the fact that it's been hidden in Kibana makes it look\nmore like a breaking change from a customer perspective).\n\nRel: https://github.com/elastic/docs-content/issues/1417\nRel: https://github.com/elastic/kibana/pull/212031","sha":"edd73b2df6d4b302deeb10f9687b2174a4603762","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","backport:version","v9.1.0","v9.0.2"],"title":"[Docs] Add behavioral analytics removal to Kibana 9.0 breaking changes","number":220906,"url":"https://github.com/elastic/kibana/pull/220906","mergeCommit":{"message":"[Docs] Add behavioral analytics removal to Kibana 9.0 breaking changes (#220906)\n\nBehavioral analytics was hidden from the UI and its associated APIs were\ndeprecated in 9.0, but only the API deprecation was called out in\nElasticseach release notes. This PR addresses the UI communication gap\nby adding a mention to the 9.0 breaking changes (while it's technically\na deprecation, the fact that it's been hidden in Kibana makes it look\nmore like a breaking change from a customer perspective).\n\nRel: https://github.com/elastic/docs-content/issues/1417\nRel: https://github.com/elastic/kibana/pull/212031","sha":"edd73b2df6d4b302deeb10f9687b2174a4603762"}},"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/220906","number":220906,"mergeCommit":{"message":"[Docs] Add behavioral analytics removal to Kibana 9.0 breaking changes (#220906)\n\nBehavioral analytics was hidden from the UI and its associated APIs were\ndeprecated in 9.0, but only the API deprecation was called out in\nElasticseach release notes. This PR addresses the UI communication gap\nby adding a mention to the 9.0 breaking changes (while it's technically\na deprecation, the fact that it's been hidden in Kibana makes it look\nmore like a breaking change from a customer perspective).\n\nRel: https://github.com/elastic/docs-content/issues/1417\nRel: https://github.com/elastic/kibana/pull/212031","sha":"edd73b2df6d4b302deeb10f9687b2174a4603762"}},{"branch":"9.0","label":"v9.0.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> |
||
|
Kibana Machine
|
afa4e6f557
|
[9.0] Update dependency semver to ^7.7.2 (main) (#220932) (#220942)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency semver to ^7.7.2 (main) (#220932)](https://github.com/elastic/kibana/pull/220932) <!--- 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-05-19T22:01:34Z","message":"Update dependency semver to ^7.7.2 (main) (#220932)\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"dccd491080bb55f02a5309ab1fde5a37cf13d765","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:all-open","v9.1.0"],"title":"Update dependency semver to ^7.7.2 (main)","number":220932,"url":"https://github.com/elastic/kibana/pull/220932","mergeCommit":{"message":"Update dependency semver to ^7.7.2 (main) (#220932)\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"dccd491080bb55f02a5309ab1fde5a37cf13d765"}},"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/220932","number":220932,"mergeCommit":{"message":"Update dependency semver to ^7.7.2 (main) (#220932)\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"dccd491080bb55f02a5309ab1fde5a37cf13d765"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co> |
||
Tiago Costa
|
17bbf4c150
|
skip flaky suite (#182447) | ||
|
Kibana Machine
|
14ea2cb55e | skip failing test suite (#199905) | ||
|
Kibana Machine
|
fc409afb69
|
[9.0] [docs] Add products to docset.yml (#220848) (#220871)
# Backport This will backport the following commits from `main` to `9.0`: - [[docs] Add `products` to `docset.yml` (#220848)](https://github.com/elastic/kibana/pull/220848) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Colleen McGinnis","email":"colleen.mcginnis@elastic.co"},"sourceCommit":{"committedDate":"2025-05-16T15:17:06Z","message":"[docs] Add `products` to `docset.yml` (#220848)\n\nRelated to https://github.com/elastic/docs-builder/issues/1200\n\nAdd `products` to `docset.yml` to be used in the search experience.\n\ncc @KOTungseth","sha":"266def5a2605156522ec808ab5f333d8845678c2","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","documentation","backport:version","v9.1.0","v9.0.2"],"title":"[docs] Add `products` to `docset.yml`","number":220848,"url":"https://github.com/elastic/kibana/pull/220848","mergeCommit":{"message":"[docs] Add `products` to `docset.yml` (#220848)\n\nRelated to https://github.com/elastic/docs-builder/issues/1200\n\nAdd `products` to `docset.yml` to be used in the search experience.\n\ncc @KOTungseth","sha":"266def5a2605156522ec808ab5f333d8845678c2"}},"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/220848","number":220848,"mergeCommit":{"message":"[docs] Add `products` to `docset.yml` (#220848)\n\nRelated to https://github.com/elastic/docs-builder/issues/1200\n\nAdd `products` to `docset.yml` to be used in the search experience.\n\ncc @KOTungseth","sha":"266def5a2605156522ec808ab5f333d8845678c2"}},{"branch":"9.0","label":"v9.0.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Colleen McGinnis <colleen.mcginnis@elastic.co> |
||
Andreana Malama
|
cfae324a4b
|
[9.0] [Lens] Avoid label rounding of percentile value after 3 decimal digits (#220035) (#220851)
# Backport This will backport the following commits from `main` to `9.0`: - [[Lens] Avoid label rounding of percentile value after 3 decimal digits (#220035)](https://github.com/elastic/kibana/pull/220035) <!--- Backport version: 9.6.6 --> ### 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-05-15T15:03:54Z","message":"[Lens] Avoid label rounding of percentile value after 3 decimal digits (#220035)\n\nFix #166585 \n\n## Summary\n\nThis PR fixes the issue of rounding the percentile value after 3 decimal\ndigits in the label.\n\n- Before the fix:\n\n\n- After the fix:\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] [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- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"1611d55ce1847181d51e46f798795b06a35d6d67","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","v8.18.2","v9.0.2"],"title":"[Lens] Avoid label rounding of percentile value after 3 decimal digits","number":220035,"url":"https://github.com/elastic/kibana/pull/220035","mergeCommit":{"message":"[Lens] Avoid label rounding of percentile value after 3 decimal digits (#220035)\n\nFix #166585 \n\n## Summary\n\nThis PR fixes the issue of rounding the percentile value after 3 decimal\ndigits in the label.\n\n- Before the fix:\n\n\n- After the fix:\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] [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- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"1611d55ce1847181d51e46f798795b06a35d6d67"}},"sourceBranch":"main","suggestedTargetBranches":["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/220035","number":220035,"mergeCommit":{"message":"[Lens] Avoid label rounding of percentile value after 3 decimal digits (#220035)\n\nFix #166585 \n\n## Summary\n\nThis PR fixes the issue of rounding the percentile value after 3 decimal\ndigits in the label.\n\n- Before the fix:\n\n\n- After the fix:\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] [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- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"1611d55ce1847181d51e46f798795b06a35d6d67"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/220833","number":220833,"state":"MERGED","mergeCommit":{"sha":"189c8a210db3a59da20f33df2c1e8dc0451fdd1a","message":"[8.19] [Lens] Avoid label rounding of percentile value after 3 decimal digits (#220035) (#220833)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [[Lens] Avoid label rounding of percentile value after 3 decimal\ndigits (#220035)](https://github.com/elastic/kibana/pull/220035)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Andreana Malama <72010092+andrimal@users.noreply.github.com>"}},{"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--> |
||
|
Kibana Machine
|
27ac78e297 | skip failing test suite (#220822) | ||
Hannah Mudge
|
e9e3b2eb43
|
[9.0] [Dashboard] Keep panel state when saved in an error state (#220841)
Closes https://github.com/elastic/kibana/issues/220799 ## Summary This PR ensures that, if a panel has an error that causes the child API to not be available, we default to the state stored in the `panels$` behaviour subject rather than `{ rawState: {} }`. Otherwise, **all state is lost** when saving a dashboard in an error state, which makes it impossible to restore the panel even once the error has been resolved. ### Checklist - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) |
||
|
Kibana Machine
|
5140987754
|
[9.0] [9.x] ESQL: link to index modes in LOOKUP JOIN reference (#215712) (#220839)
# Backport This will backport the following commits from `main` to `9.0`: - [[9.x] ESQL: link to index modes in LOOKUP JOIN reference (#215712)](https://github.com/elastic/kibana/pull/215712) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexander Spies","email":"alexander.spies@elastic.co"},"sourceCommit":{"committedDate":"2025-05-15T16:17:37Z","message":"[9.x] ESQL: link to index modes in LOOKUP JOIN reference (#215712)\n\n\n\nCo-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"26d803a6ae5725ff14ffcc58a06d8fe0e71fa8ab","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:ES|QL","Team:ESQL","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[9.x] ESQL: link to index modes in LOOKUP JOIN reference","number":215712,"url":"https://github.com/elastic/kibana/pull/215712","mergeCommit":{"message":"[9.x] ESQL: link to index modes in LOOKUP JOIN reference (#215712)\n\n\n\nCo-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"26d803a6ae5725ff14ffcc58a06d8fe0e71fa8ab"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","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/215712","number":215712,"mergeCommit":{"message":"[9.x] ESQL: link to index modes in LOOKUP JOIN reference (#215712)\n\n\n\nCo-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"26d803a6ae5725ff14ffcc58a06d8fe0e71fa8ab"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","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--> Co-authored-by: Alexander Spies <alexander.spies@elastic.co> Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co> |
||
|
Kibana Machine
|
ae60366332
|
[9.0] [DOCS] Adds Elastic Managed LLM to Kibana connectors (#220247) (#220797)
# Backport This will backport the following commits from `main` to `9.0`: - [[DOCS] Adds Elastic Managed LLM to Kibana connectors (#220247)](https://github.com/elastic/kibana/pull/220247) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"István Zoltán Szabó","email":"szabosteve@gmail.com"},"sourceCommit":{"committedDate":"2025-05-14T18:27:35Z","message":"[DOCS] Adds Elastic Managed LLM to Kibana connectors (#220247)\n\n## Summary\n\nRelated to https://github.com/elastic/search-team/issues/9890\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials","sha":"e499dd4e6dd4148e0b3b4ea07865d823171602c8","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","docs","backport:version","v9.1.0","v9.0.2"],"title":"[DOCS] Adds Elastic Managed LLM to Kibana connectors","number":220247,"url":"https://github.com/elastic/kibana/pull/220247","mergeCommit":{"message":"[DOCS] Adds Elastic Managed LLM to Kibana connectors (#220247)\n\n## Summary\n\nRelated to https://github.com/elastic/search-team/issues/9890\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials","sha":"e499dd4e6dd4148e0b3b4ea07865d823171602c8"}},"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/220247","number":220247,"mergeCommit":{"message":"[DOCS] Adds Elastic Managed LLM to Kibana connectors (#220247)\n\n## Summary\n\nRelated to https://github.com/elastic/search-team/issues/9890\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials","sha":"e499dd4e6dd4148e0b3b4ea07865d823171602c8"}},{"branch":"9.0","label":"v9.0.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com> |
||
Søren Louv-Jansen
|
6a31095102
|
[9.0] [Obs AI Assistant] Use update-by-query for semantic_text migration (#220255) (#220647)
# Backport This will backport the following commits from `main` to `9.0`: - [[Obs AI Assistant] Use update-by-query for semantic_text migration (#220255)](https://github.com/elastic/kibana/pull/220255) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Søren Louv-Jansen","email":"soren.louv@elastic.co"},"sourceCommit":{"committedDate":"2025-05-08T21:52:33Z","message":"[Obs AI Assistant] Use update-by-query for semantic_text migration (#220255)\n\nCloses: https://github.com/elastic/kibana/issues/220339\n\n**Background**\nThe `semantic_text` migration will migrate content from `text` field to\n`semantic_text` field. It does so with a recursive function that\ncontinuously retrieves knowledge base entries if they do not contain\n`semantic_text` and updates them accordingly.\n\n**Problem**\nIt is possible to save empty knowledge base entries\n(https://github.com/elastic/kibana/issues/220342) where `text` and\n`semantic_text` will be empty. Doing this will cause the migration\nscript to run indefinitely leading to OOM on the affected clusters.\n\n## Workarounds for clusters that cannot / won't upgrade\n\nTemporary workaround is to delete empty knowledge base entries:\n\n```jsonc\nPOST .kibana-observability-ai-assistant-kb/_delete_by_query\n{\n \"query\": {\n \"bool\": {\n \"must\": [{ \"exists\": { \"field\": \"text\" }}],\n \"must_not\": [ { \"wildcard\": { \"text\": \"*\" } }\n ]\n }\n }\n}\n```\n\nIf you want to perform a dry run (find offending documents without\ndeleting them) run this:\n```jsonc\nGET .kibana-observability-ai-assistant-kb/_search\n{\n \"query\": {\n \"bool\": {\n \"must\": [{ \"exists\": { \"field\": \"text\" }}],\n \"must_not\": [ { \"wildcard\": { \"text\": \"*\" } }\n ]\n }\n }\n}\n```","sha":"96d1692ae20172ea3d8a5f7062c55c10d38ed9a2","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Obs AI Assistant","ci:project-deploy-observability","backport:version","v9.1.0","v8.19.0","v8.17.7","v8.18.2","v9.0.2"],"title":"[Obs AI Assistant] Use update-by-query for semantic_text migration","number":220255,"url":"https://github.com/elastic/kibana/pull/220255","mergeCommit":{"message":"[Obs AI Assistant] Use update-by-query for semantic_text migration (#220255)\n\nCloses: https://github.com/elastic/kibana/issues/220339\n\n**Background**\nThe `semantic_text` migration will migrate content from `text` field to\n`semantic_text` field. It does so with a recursive function that\ncontinuously retrieves knowledge base entries if they do not contain\n`semantic_text` and updates them accordingly.\n\n**Problem**\nIt is possible to save empty knowledge base entries\n(https://github.com/elastic/kibana/issues/220342) where `text` and\n`semantic_text` will be empty. Doing this will cause the migration\nscript to run indefinitely leading to OOM on the affected clusters.\n\n## Workarounds for clusters that cannot / won't upgrade\n\nTemporary workaround is to delete empty knowledge base entries:\n\n```jsonc\nPOST .kibana-observability-ai-assistant-kb/_delete_by_query\n{\n \"query\": {\n \"bool\": {\n \"must\": [{ \"exists\": { \"field\": \"text\" }}],\n \"must_not\": [ { \"wildcard\": { \"text\": \"*\" } }\n ]\n }\n }\n}\n```\n\nIf you want to perform a dry run (find offending documents without\ndeleting them) run this:\n```jsonc\nGET .kibana-observability-ai-assistant-kb/_search\n{\n \"query\": {\n \"bool\": {\n \"must\": [{ \"exists\": { \"field\": \"text\" }}],\n \"must_not\": [ { \"wildcard\": { \"text\": \"*\" } }\n ]\n }\n }\n}\n```","sha":"96d1692ae20172ea3d8a5f7062c55c10d38ed9a2"}},"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/220255","number":220255,"mergeCommit":{"message":"[Obs AI Assistant] Use update-by-query for semantic_text migration (#220255)\n\nCloses: https://github.com/elastic/kibana/issues/220339\n\n**Background**\nThe `semantic_text` migration will migrate content from `text` field to\n`semantic_text` field. It does so with a recursive function that\ncontinuously retrieves knowledge base entries if they do not contain\n`semantic_text` and updates them accordingly.\n\n**Problem**\nIt is possible to save empty knowledge base entries\n(https://github.com/elastic/kibana/issues/220342) where `text` and\n`semantic_text` will be empty. Doing this will cause the migration\nscript to run indefinitely leading to OOM on the affected clusters.\n\n## Workarounds for clusters that cannot / won't upgrade\n\nTemporary workaround is to delete empty knowledge base entries:\n\n```jsonc\nPOST .kibana-observability-ai-assistant-kb/_delete_by_query\n{\n \"query\": {\n \"bool\": {\n \"must\": [{ \"exists\": { \"field\": \"text\" }}],\n \"must_not\": [ { \"wildcard\": { \"text\": \"*\" } }\n ]\n }\n }\n}\n```\n\nIf you want to perform a dry run (find offending documents without\ndeleting them) run this:\n```jsonc\nGET .kibana-observability-ai-assistant-kb/_search\n{\n \"query\": {\n \"bool\": {\n \"must\": [{ \"exists\": { \"field\": \"text\" }}],\n \"must_not\": [ { \"wildcard\": { \"text\": \"*\" } }\n ]\n }\n }\n}\n```","sha":"96d1692ae20172ea3d8a5f7062c55c10d38ed9a2"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/220640","number":220640,"state":"OPEN"},{"branch":"8.17","label":"v8.17.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/220642","number":220642,"state":"OPEN"},{"branch":"8.18","label":"v8.18.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/220646","number":220646,"state":"OPEN"},{"branch":"9.0","label":"v9.0.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co> |
||
Ola Pawlus
|
0d4cf66dd1
|
[9.0] Fix: success message and scroll after adding panel from library (#220122) (#220776)
# Backport This will backport the following commits from `main` to `9.0`: - [Fix: success message and scroll after adding panel from library (#220122)](https://github.com/elastic/kibana/pull/220122) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ola Pawlus","email":"98127445+olapawlus@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-05-09T17:24:49Z","message":"Fix: success message and scroll after adding panel from library (#220122)\n\nInitially there was no success message for any type in the library and\nthere was no scrolling to added panel.\n\nThis change sets displaySuccessMessage to true for each plugin\nregistered in the Add from Library flyout.\n\nIt ensures that:\n- users see a success toast after adding a panel,\n- the newly added panel is automatically scrolled into view.\n\nCloses: #188775\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e7e8d2f13b44ae78b33ada4a3904b17066c6fd37","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Feature:Dashboard","Feature:Embedding","regression","release_note:fix","Team:Presentation","loe:small","impact:high","backport:version","v9.1.0","v8.19.0","v8.18.2","v9.0.2"],"title":"Fix: success message and scroll after adding panel from library","number":220122,"url":"https://github.com/elastic/kibana/pull/220122","mergeCommit":{"message":"Fix: success message and scroll after adding panel from library (#220122)\n\nInitially there was no success message for any type in the library and\nthere was no scrolling to added panel.\n\nThis change sets displaySuccessMessage to true for each plugin\nregistered in the Add from Library flyout.\n\nIt ensures that:\n- users see a success toast after adding a panel,\n- the newly added panel is automatically scrolled into view.\n\nCloses: #188775\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e7e8d2f13b44ae78b33ada4a3904b17066c6fd37"}},"sourceBranch":"main","suggestedTargetBranches":["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/220122","number":220122,"mergeCommit":{"message":"Fix: success message and scroll after adding panel from library (#220122)\n\nInitially there was no success message for any type in the library and\nthere was no scrolling to added panel.\n\nThis change sets displaySuccessMessage to true for each plugin\nregistered in the Add from Library flyout.\n\nIt ensures that:\n- users see a success toast after adding a panel,\n- the newly added panel is automatically scrolled into view.\n\nCloses: #188775\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e7e8d2f13b44ae78b33ada4a3904b17066c6fd37"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/220703","number":220703,"state":"MERGED","mergeCommit":{"sha":"7501611e3277d378ea00e1731b39be0ebeb7769b","message":"[8.19] Fix: success message and scroll after adding panel from library (#220122) (#220703)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [Fix: success message and scroll after adding panel from library\n(#220122)](https://github.com/elastic/kibana/pull/220122)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Ola Pawlus <98127445+olapawlus@users.noreply.github.com>"}},{"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> |
||
|
Ola Pawlus
|
bd1fe418b4
|
[9.0] Fixing layout of the embeddablePanelHeading containing description an… (#219428) (#220752)
# Backport This will backport the following commits from `main` to `9.0`: - [Fixing layout of the embeddablePanelHeading containing description an… (#219428)](https://github.com/elastic/kibana/pull/219428) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ola Pawlus","email":"98127445+olapawlus@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-05-06T08:48:33Z","message":"Fixing layout of the embeddablePanelHeading containing description an… (#219428)\n\nIt has been assumed that everything of the embeddable panel heading will\nstay on one line, and this is a proposal based on that assumption.\n\nThis video shows how the layout responds:\n\n\nhttps://github.com/user-attachments/assets/db7f3e38-1fbd-4d21-a0a2-96ed1768b744\n\n\n\nIntroduced ellipsis for panel titles and custom time range badges when\nthe text overflows.\n\nFixed the issue with the description icon, which was wrapping to the\nnext line.\n\nFixed the layout of the embeddable panel heading containing three\nelements: title, icon, and badge.\n\nCloses: #211252 and #219868\n\n\nImproved layout of children within the parent container, as the previous\nstyles didn’t prevent significant disproportion caused by varying title\nand time-range-badge text lengths (disproportion is shown in the first\nscreenshot below).\n\nNow, each child (which is title and time-range-badge) will grow/shrink\nproportionally, ensuring consistent layout regardless of their content\nlength. (as shown in the screenshots below)\n\n\n\n---------\n\nCo-authored-by: Hannah Mudge <Heenawter@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"ca062472b949de4efb480611c0eebff411f67b00","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Feature:Dashboard","regression","release_note:fix","Team:Presentation","loe:small","impact:high","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"Fixing layout of the embeddablePanelHeading containing description an…","number":219428,"url":"https://github.com/elastic/kibana/pull/219428","mergeCommit":{"message":"Fixing layout of the embeddablePanelHeading containing description an… (#219428)\n\nIt has been assumed that everything of the embeddable panel heading will\nstay on one line, and this is a proposal based on that assumption.\n\nThis video shows how the layout responds:\n\n\nhttps://github.com/user-attachments/assets/db7f3e38-1fbd-4d21-a0a2-96ed1768b744\n\n\n\nIntroduced ellipsis for panel titles and custom time range badges when\nthe text overflows.\n\nFixed the issue with the description icon, which was wrapping to the\nnext line.\n\nFixed the layout of the embeddable panel heading containing three\nelements: title, icon, and badge.\n\nCloses: #211252 and #219868\n\n\nImproved layout of children within the parent container, as the previous\nstyles didn’t prevent significant disproportion caused by varying title\nand time-range-badge text lengths (disproportion is shown in the first\nscreenshot below).\n\nNow, each child (which is title and time-range-badge) will grow/shrink\nproportionally, ensuring consistent layout regardless of their content\nlength. (as shown in the screenshots below)\n\n\n\n---------\n\nCo-authored-by: Hannah Mudge <Heenawter@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"ca062472b949de4efb480611c0eebff411f67b00"}},"sourceBranch":"main","suggestedTargetBranches":["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/219428","number":219428,"mergeCommit":{"message":"Fixing layout of the embeddablePanelHeading containing description an… (#219428)\n\nIt has been assumed that everything of the embeddable panel heading will\nstay on one line, and this is a proposal based on that assumption.\n\nThis video shows how the layout responds:\n\n\nhttps://github.com/user-attachments/assets/db7f3e38-1fbd-4d21-a0a2-96ed1768b744\n\n\n\nIntroduced ellipsis for panel titles and custom time range badges when\nthe text overflows.\n\nFixed the issue with the description icon, which was wrapping to the\nnext line.\n\nFixed the layout of the embeddable panel heading containing three\nelements: title, icon, and badge.\n\nCloses: #211252 and #219868\n\n\nImproved layout of children within the parent container, as the previous\nstyles didn’t prevent significant disproportion caused by varying title\nand time-range-badge text lengths (disproportion is shown in the first\nscreenshot below).\n\nNow, each child (which is title and time-range-badge) will grow/shrink\nproportionally, ensuring consistent layout regardless of their content\nlength. (as shown in the screenshots below)\n\n\n\n---------\n\nCo-authored-by: Hannah Mudge <Heenawter@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"ca062472b949de4efb480611c0eebff411f67b00"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/220206","number":220206,"state":"MERGED","mergeCommit":{"sha":"b3450affa4dd7a2c827a29b4769ad79e966686a7","message":"[8.19] Fixing layout of the embeddablePanelHeading containing description an… (#219428) (#220206)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [Fixing layout of the embeddablePanelHeading containing description\nan… (#219428)](https://github.com/elastic/kibana/pull/219428)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Ola Pawlus <98127445+olapawlus@users.noreply.github.com>\nCo-authored-by: Hannah Mudge <Heenawter@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>"}},{"branch":"8.18","label":"v8.18.1","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
|
0aab471826
|
[9.0] Update LaunchDarkly (main) (#220312) (#220738)
# Backport This will backport the following commits from `main` to `9.0`: - [Update LaunchDarkly (main) (#220312)](https://github.com/elastic/kibana/pull/220312) <!--- 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-05-11T09:47:01Z","message":"Update LaunchDarkly (main) (#220312)","sha":"392037c632d476d3ed1dbae764f973441c7517c8","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 LaunchDarkly (main)","number":220312,"url":"https://github.com/elastic/kibana/pull/220312","mergeCommit":{"message":"Update LaunchDarkly (main) (#220312)","sha":"392037c632d476d3ed1dbae764f973441c7517c8"}},"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/220312","number":220312,"mergeCommit":{"message":"Update LaunchDarkly (main) (#220312)","sha":"392037c632d476d3ed1dbae764f973441c7517c8"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
Ying Mao
|
7f108100ec
|
[9.0] [Response Ops][Alerting] Skip writing alerts when rule exceeds configured timeout (#220147) (#220725)
# Backport This will backport the following commits from `main` to `9.0`: - [[Response Ops][Alerting] Skip writing alerts when rule exceeds configured timeout (#220147)](https://github.com/elastic/kibana/pull/220147) <!--- Backport version: 9.6.6 --> ### 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-05-09T22:38:30Z","message":"[Response Ops][Alerting] Skip writing alerts when rule exceeds configured timeout (#220147)\n\nFixes https://github.com/elastic/kibana/issues/219152\n\n## Summary\n\nWe added the ability to short circuit rule execution (skip scheduling\nactions and writing event log docs) when an execution is cancelled due\nto timeout but at the time we added this ability, we were not persisting\nalert documents. When we added framework alerts-as-data, we did not add\na check to ensure rule execution had not timed out before writing the\nalerts. This PR adds the missing check. This should also respect the\n`cancelAlertsOnRuleTimeout` flag that can be set in the config or the\nrule type that can force persisting alerts regardless of timeout.\n\n## To verify\n\n1. Set a short `ruleTaskTimeout` on a rule type and add a delay to the\nrule executor that will force the rule to timeout.\n2. Create a rule of that type that generates alerts. Verify that when\nthe rule execution times out, no alerts are written.","sha":"437a9fa4f3c009bd5b1ebc1383de4459f45200f5","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","backport:version","v9.1.0","v8.19.0","v8.18.2","v9.0.2"],"title":"[Response Ops][Alerting] Skip writing alerts when rule exceeds configured timeout","number":220147,"url":"https://github.com/elastic/kibana/pull/220147","mergeCommit":{"message":"[Response Ops][Alerting] Skip writing alerts when rule exceeds configured timeout (#220147)\n\nFixes https://github.com/elastic/kibana/issues/219152\n\n## Summary\n\nWe added the ability to short circuit rule execution (skip scheduling\nactions and writing event log docs) when an execution is cancelled due\nto timeout but at the time we added this ability, we were not persisting\nalert documents. When we added framework alerts-as-data, we did not add\na check to ensure rule execution had not timed out before writing the\nalerts. This PR adds the missing check. This should also respect the\n`cancelAlertsOnRuleTimeout` flag that can be set in the config or the\nrule type that can force persisting alerts regardless of timeout.\n\n## To verify\n\n1. Set a short `ruleTaskTimeout` on a rule type and add a delay to the\nrule executor that will force the rule to timeout.\n2. Create a rule of that type that generates alerts. Verify that when\nthe rule execution times out, no alerts are written.","sha":"437a9fa4f3c009bd5b1ebc1383de4459f45200f5"}},"sourceBranch":"main","suggestedTargetBranches":["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/220147","number":220147,"mergeCommit":{"message":"[Response Ops][Alerting] Skip writing alerts when rule exceeds configured timeout (#220147)\n\nFixes https://github.com/elastic/kibana/issues/219152\n\n## Summary\n\nWe added the ability to short circuit rule execution (skip scheduling\nactions and writing event log docs) when an execution is cancelled due\nto timeout but at the time we added this ability, we were not persisting\nalert documents. When we added framework alerts-as-data, we did not add\na check to ensure rule execution had not timed out before writing the\nalerts. This PR adds the missing check. This should also respect the\n`cancelAlertsOnRuleTimeout` flag that can be set in the config or the\nrule type that can force persisting alerts regardless of timeout.\n\n## To verify\n\n1. Set a short `ruleTaskTimeout` on a rule type and add a delay to the\nrule executor that will force the rule to timeout.\n2. Create a rule of that type that generates alerts. Verify that when\nthe rule execution times out, no alerts are written.","sha":"437a9fa4f3c009bd5b1ebc1383de4459f45200f5"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/220724","number":220724,"state":"OPEN"},{"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--> |
||
|
Lisa Cawley
|
d030390d3d
|
[9.0] Update Elasticsearch URLs in doc link service (#219656) (#220450)
# Backport This will backport the following commits from `main` to `9.0`: - [Update Elasticsearch URLs in doc link service (#219656)](https://github.com/elastic/kibana/pull/219656) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-05-07T15:57:18Z","message":"Update Elasticsearch URLs in doc link service (#219656)\n\nCo-authored-by: Jean-Louis Leysens <jeanlouis.leysens@elastic.co>","sha":"2ae840624e724c91061ea7e8e0f67efbcc28cf78","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","backport:version","v9.1.0","v9.0.1"],"title":"Update Elasticsearch URLs in doc link service","number":219656,"url":"https://github.com/elastic/kibana/pull/219656","mergeCommit":{"message":"Update Elasticsearch URLs in doc link service (#219656)\n\nCo-authored-by: Jean-Louis Leysens <jeanlouis.leysens@elastic.co>","sha":"2ae840624e724c91061ea7e8e0f67efbcc28cf78"}},"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/219656","number":219656,"mergeCommit":{"message":"Update Elasticsearch URLs in doc link service (#219656)\n\nCo-authored-by: Jean-Louis Leysens <jeanlouis.leysens@elastic.co>","sha":"2ae840624e724c91061ea7e8e0f67efbcc28cf78"}},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jean-Louis Leysens <jeanlouis.leysens@elastic.co> |
||
|
Steph Milovic
|
79d0cfb01d
|
[9.0] [Security Assistant] Added examples for necessary AI Assistant OpenAPI docs (#219883) (#220710)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Assistant] Added examples for necessary AI Assistant OpenAPI docs (#219883)](https://github.com/elastic/kibana/pull/219883) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-05-09T14:47:44Z","message":"[Security Assistant] Added examples for necessary AI Assistant OpenAPI docs (#219883)","sha":"214c5f099e61a9e0c5e893e0c417d12636e3e000","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0","v9.0.1","v8.18.2"],"title":"[Security Assistant] Added examples for necessary AI Assistant OpenAPI docs","number":219883,"url":"https://github.com/elastic/kibana/pull/219883","mergeCommit":{"message":"[Security Assistant] Added examples for necessary AI Assistant OpenAPI docs (#219883)","sha":"214c5f099e61a9e0c5e893e0c417d12636e3e000"}},"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/219883","number":219883,"mergeCommit":{"message":"[Security Assistant] Added examples for necessary AI Assistant OpenAPI docs (#219883)","sha":"214c5f099e61a9e0c5e893e0c417d12636e3e000"}},{"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"},{"branch":"8.18","label":"v8.18.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
b0d5ab28f8
|
[9.0] [Cloud Security] Cloud Security Posture - remove GCP required error state (#220676) (#220715)
# Backport This will backport the following commits from `main` to `9.0`: - [[Cloud Security] Cloud Security Posture - remove GCP required error state (#220676)](https://github.com/elastic/kibana/pull/220676) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"seanrathier","email":"sean.rathier@gmail.com"},"sourceCommit":{"committedDate":"2025-05-09T19:26:31Z","message":"[Cloud Security] Cloud Security Posture - remove GCP required error state (#220676)","sha":"473bab1189d77ee0537ab255d271b2b522d32a5c","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Cloud Security","backport:version","9.1 candidate","v9.1.0","v8.19.0","v9.0.1"],"title":"[Cloud Security] Cloud Security Posture - remove GCP required error state","number":220676,"url":"https://github.com/elastic/kibana/pull/220676","mergeCommit":{"message":"[Cloud Security] Cloud Security Posture - remove GCP required error state (#220676)","sha":"473bab1189d77ee0537ab255d271b2b522d32a5c"}},"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/220676","number":220676,"mergeCommit":{"message":"[Cloud Security] Cloud Security Posture - remove GCP required error state (#220676)","sha":"473bab1189d77ee0537ab255d271b2b522d32a5c"}},{"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--> Co-authored-by: seanrathier <sean.rathier@gmail.com> |
||
|
Kibana Machine
|
57d3008cdc
|
[9.0] [Security Assistant] Simplifies Security Gen AI Evaluation secret management (#219885) (#220701)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Assistant] Simplifies Security Gen AI Evaluation secret management (#219885)](https://github.com/elastic/kibana/pull/219885) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Garrett Spong","email":"spong@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-05-09T17:01:36Z","message":"[Security Assistant] Simplifies Security Gen AI Evaluation secret management (#219885)\n\n## Summary\n\nSimplifies secret management for running the Security Gen AI\nEvaluations. See updated README.md for full details, but includes:\n\n* Consolidation of multiple vault keys to a single\n`KIBANA_SECURITY_GEN_AI_CONFIG` key, which contains all connectors,\nlangsmith creds and now a way to specify `evaluatorConnectorId`.\n* Added `vault` params to both `retrieve_secrets.js` and\n`upload_secrets.js` for specifying the vault. Defaults to `sieam-team`\nsecrets.elastic.co for ease of use by developers.\n* Introduces `get_commands.js` script for fetching commands to hand off\nto either Kibana Ops for updating, or specifying config overrides when\nmanually running BuildKite pipelines.\n* Deleted `export_env_secrets.js` as it couldn't be used for setting env\nvars locally for the dev testing experience.\n* Updated `connectors` as per team discussion to include: GPT-4.1,\nClaude 3.5/3.7, and Gemini 2.5 Pro. This was a config change made by\nKibana Ops, so no code change present. But you can confirm by running\n`retrieve_secrets.js`.\n\nAnd finally, a much more detailed `README.md` for testing locally, on\nPR's and CI, and the process for updating secrets. See full\n[README.md](https://github.com/spong/kibana/blob/ci-eval-tweaks/x-pack/test/security_solution_api_integration/test_suites/genai/evaluations/README.md)\n\n\n\nExample LangSmith Runs:\n\n* `ES|QL Generation Regression Suite`: [Run\n298372]( |
