[8.x] Sync bundled packages with Package Storage #211977
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![elastic-vault-github-plugin-prod[bot]](https://avatars.githubusercontent.com/u/6764390?s=60&v=4){kind=small}
…201455) (#202797) # Backport This will backport the following commits from `main` to `8.16`: - [[Search] a11y make index mappings search results accessible (#201455)](#201455) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Saarika Bhasi","email":"55930906+saarikabhasi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-03T18:37:51Z","message":"[Search] a11y make index mappings search results accessible (#201455)\n\n## Summary\r\nMake index mappings search results accessible so that it can read by\r\nscreen reader when navigated by keyboard","sha":"5480451f27639ad923fd04c865b56c58666473fd","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","v8.16.0","backport:version","v8.17.0","v8.16.1","v8.16.2"],"title":"[Search] a11y make index mappings search results accessible ","number":201455,"url":"https://github.com/elastic/kibana/pull/201455","mergeCommit":{"message":"[Search] a11y make index mappings search results accessible (#201455)\n\n## Summary\r\nMake index mappings search results accessible so that it can read by\r\nscreen reader when navigated by keyboard","sha":"5480451f27639ad923fd04c865b56c58666473fd"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201455","number":201455,"mergeCommit":{"message":"[Search] a11y make index mappings search results accessible (#201455)\n\n## Summary\r\nMake index mappings search results accessible so that it can read by\r\nscreen reader when navigated by keyboard","sha":"5480451f27639ad923fd04c865b56c58666473fd"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Saarika Bhasi <55930906+saarikabhasi@users.noreply.github.com>
… message (#202226) (#202802) # Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] Modify copy of the install rules title and message (#202226)](#202226) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jacek Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2024-12-03T19:28:32Z","message":"[Security Solution] Modify copy of the install rules title and message (#202226)\n\n**Resolves: #200521**\n\n## Summary\n\nI am changing the copy of the install rules title and message.\n\n# BEFORE\n\n\n\n<img width=\"873\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/5f4b82f1-094e-432f-9d25-c31042b7585b\">\n\n# AFTER\n<img width=\"611\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/bf211743-2edc-4573-8d10-1c156000d875\">\n\n<img width=\"791\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/612b90b1-290d-40e5-96eb-c88182f78673\">\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [X] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n\n---------\n\nCo-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>","sha":"530b4d482c8b293bd7d36aeb698d75df401f349f","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.17.0","v8.18.0","v8.16.2"],"title":"[Security Solution] Modify copy of the install rules title and message","number":202226,"url":"https://github.com/elastic/kibana/pull/202226","mergeCommit":{"message":"[Security Solution] Modify copy of the install rules title and message (#202226)\n\n**Resolves: #200521**\n\n## Summary\n\nI am changing the copy of the install rules title and message.\n\n# BEFORE\n\n\n\n<img width=\"873\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/5f4b82f1-094e-432f-9d25-c31042b7585b\">\n\n# AFTER\n<img width=\"611\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/bf211743-2edc-4573-8d10-1c156000d875\">\n\n<img width=\"791\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/612b90b1-290d-40e5-96eb-c88182f78673\">\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [X] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n\n---------\n\nCo-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>","sha":"530b4d482c8b293bd7d36aeb698d75df401f349f"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202226","number":202226,"mergeCommit":{"message":"[Security Solution] Modify copy of the install rules title and message (#202226)\n\n**Resolves: #200521**\n\n## Summary\n\nI am changing the copy of the install rules title and message.\n\n# BEFORE\n\n\n\n<img width=\"873\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/5f4b82f1-094e-432f-9d25-c31042b7585b\">\n\n# AFTER\n<img width=\"611\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/bf211743-2edc-4573-8d10-1c156000d875\">\n\n<img width=\"791\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/612b90b1-290d-40e5-96eb-c88182f78673\">\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [X] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n\n---------\n\nCo-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>","sha":"530b4d482c8b293bd7d36aeb698d75df401f349f"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co>
## Summary When switching branches in the devcontainer, if the configuration is different from the previous branch or missing entirely, the container can easily get in a bad state or trigger rebuilds. We want the devcontainer to be seamless between branches.
…#201856) (#202710) # Backport This will backport the following commits from `main` to `8.16`: - [Update dependency @elastic/request-converter to ^8.16.2 (main) (#201856)](#201856) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-27T13:46:35Z","message":"Update dependency @elastic/request-converter to ^8.16.2 (main) (#201856)","sha":"4fbec3f31838f06e011c5a9ac9bb4d5d4ec97c84","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","backport:skip","v9.0.0","backport:prev-minor","v8.16.0","v8.17.0"],"number":201856,"url":"https://github.com/elastic/kibana/pull/201856","mergeCommit":{"message":"Update dependency @elastic/request-converter to ^8.16.2 (main) (#201856)","sha":"4fbec3f31838f06e011c5a9ac9bb4d5d4ec97c84"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201856","number":201856,"mergeCommit":{"message":"Update dependency @elastic/request-converter to ^8.16.2 (main) (#201856)","sha":"4fbec3f31838f06e011c5a9ac9bb4d5d4ec97c84"}},{"branch":"8.16","label":"v8.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","labelRegex":"^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>
…ture flag is off (#201825) (#202751) # Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] Skip isCustomized calculation when the feature flag is off (#201825)](#201825) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dmitrii Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2024-12-03T12:11:24Z","message":"[Security Solution] Skip isCustomized calculation when the feature flag is off (#201825)\n\n**Resolves: https://github.com/elastic/kibana/issues/201632**\r\n\r\n## Summary \r\n\r\nWhen the rule customization feature flag is disabled, we should always\r\nreturn `isCustomized: false`, regardless of any changes introduced to a\r\nrule. This ensures that we do not accidentally mark prebuilt rules as\r\ncustomized in 8.16 with the feature flag off. For more details, refer to\r\nthe related issue: https://github.com/elastic/kibana/issues/201632\r\n\r\n### Main Changes \r\n\r\n- The primary change in this PR is encapsulated in the\r\n`calculateIsCustomized` function\r\n- Other changes involve passing the feature flag to this function\r\n- Added integration tests to cover all API CRUD operations that can be\r\nperformed with rules","sha":"22911c1828f40160cf3a2935300aec18c11b56e9","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.17.0","v8.18.0","v8.16.2"],"number":201825,"url":"https://github.com/elastic/kibana/pull/201825","mergeCommit":{"message":"[Security Solution] Skip isCustomized calculation when the feature flag is off (#201825)\n\n**Resolves: https://github.com/elastic/kibana/issues/201632**\r\n\r\n## Summary \r\n\r\nWhen the rule customization feature flag is disabled, we should always\r\nreturn `isCustomized: false`, regardless of any changes introduced to a\r\nrule. This ensures that we do not accidentally mark prebuilt rules as\r\ncustomized in 8.16 with the feature flag off. For more details, refer to\r\nthe related issue: https://github.com/elastic/kibana/issues/201632\r\n\r\n### Main Changes \r\n\r\n- The primary change in this PR is encapsulated in the\r\n`calculateIsCustomized` function\r\n- Other changes involve passing the feature flag to this function\r\n- Added integration tests to cover all API CRUD operations that can be\r\nperformed with rules","sha":"22911c1828f40160cf3a2935300aec18c11b56e9"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201825","number":201825,"mergeCommit":{"message":"[Security Solution] Skip isCustomized calculation when the feature flag is off (#201825)\n\n**Resolves: https://github.com/elastic/kibana/issues/201632**\r\n\r\n## Summary \r\n\r\nWhen the rule customization feature flag is disabled, we should always\r\nreturn `isCustomized: false`, regardless of any changes introduced to a\r\nrule. This ensures that we do not accidentally mark prebuilt rules as\r\ncustomized in 8.16 with the feature flag off. For more details, refer to\r\nthe related issue: https://github.com/elastic/kibana/issues/201632\r\n\r\n### Main Changes \r\n\r\n- The primary change in this PR is encapsulated in the\r\n`calculateIsCustomized` function\r\n- Other changes involve passing the feature flag to this function\r\n- Added integration tests to cover all API CRUD operations that can be\r\nperformed with rules","sha":"22911c1828f40160cf3a2935300aec18c11b56e9"}},{"branch":"8.17","label":"v8.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/202696","number":202696,"state":"MERGED","mergeCommit":{"sha":"487149e077e61341f81c871b74f36a9e20df67c0","message":"[8.17] [Security Solution] Skip isCustomized calculation when the feature flag is off (#201825) (#202696)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.17`:\n- [[Security Solution] Skip isCustomized calculation when the feature\nflag is off (#201825)](https://github.com/elastic/kibana/pull/201825)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Dmitrii\nShevchenko\",\"email\":\"dmitrii.shevchenko@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-12-03T12:11:24Z\",\"message\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is off\n(#201825)\\n\\n**Resolves:\nhttps://github.com//issues/201632**\\r\\n\\r\\n## Summary\n\\r\\n\\r\\nWhen the rule customization feature flag is disabled, we should\nalways\\r\\nreturn `isCustomized: false`, regardless of any changes\nintroduced to a\\r\\nrule. This ensures that we do not accidentally mark\nprebuilt rules as\\r\\ncustomized in 8.16 with the feature flag off. For\nmore details, refer to\\r\\nthe related issue:\nhttps://github.com//issues/201632\\r\\n\\r\\n### Main Changes\n\\r\\n\\r\\n- The primary change in this PR is encapsulated in\nthe\\r\\n`calculateIsCustomized` function\\r\\n- Other changes involve\npassing the feature flag to this function\\r\\n- Added integration tests\nto cover all API CRUD operations that can be\\r\\nperformed with\nrules\",\"sha\":\"22911c1828f40160cf3a2935300aec18c11b56e9\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:skip\",\"v9.0.0\",\"Team:Detections\nand Resp\",\"Team: SecuritySolution\",\"Team:Detection Rule\nManagement\",\"Feature:Prebuilt Detection\nRules\",\"backport:version\",\"v8.17.0\",\"v8.18.0\",\"v8.16.2\"],\"title\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is\noff\",\"number\":201825,\"url\":\"https://github.com/elastic/kibana/pull/201825\",\"mergeCommit\":{\"message\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is off\n(#201825)\\n\\n**Resolves:\nhttps://github.com//issues/201632**\\r\\n\\r\\n## Summary\n\\r\\n\\r\\nWhen the rule customization feature flag is disabled, we should\nalways\\r\\nreturn `isCustomized: false`, regardless of any changes\nintroduced to a\\r\\nrule. This ensures that we do not accidentally mark\nprebuilt rules as\\r\\ncustomized in 8.16 with the feature flag off. For\nmore details, refer to\\r\\nthe related issue:\nhttps://github.com//issues/201632\\r\\n\\r\\n### Main Changes\n\\r\\n\\r\\n- The primary change in this PR is encapsulated in\nthe\\r\\n`calculateIsCustomized` function\\r\\n- Other changes involve\npassing the feature flag to this function\\r\\n- Added integration tests\nto cover all API CRUD operations that can be\\r\\nperformed with\nrules\",\"sha\":\"22911c1828f40160cf3a2935300aec18c11b56e9\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.17\",\"8.x\",\"8.16\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/201825\",\"number\":201825,\"mergeCommit\":{\"message\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is off\n(#201825)\\n\\n**Resolves:\nhttps://github.com//issues/201632**\\r\\n\\r\\n## Summary\n\\r\\n\\r\\nWhen the rule customization feature flag is disabled, we should\nalways\\r\\nreturn `isCustomized: false`, regardless of any changes\nintroduced to a\\r\\nrule. This ensures that we do not accidentally mark\nprebuilt rules as\\r\\ncustomized in 8.16 with the feature flag off. For\nmore details, refer to\\r\\nthe related issue:\nhttps://github.com//issues/201632\\r\\n\\r\\n### Main Changes\n\\r\\n\\r\\n- The primary change in this PR is encapsulated in\nthe\\r\\n`calculateIsCustomized` function\\r\\n- Other changes involve\npassing the feature flag to this function\\r\\n- Added integration tests\nto cover all API CRUD operations that can be\\r\\nperformed with\nrules\",\"sha\":\"22911c1828f40160cf3a2935300aec18c11b56e9\"}},{\"branch\":\"8.17\",\"label\":\"v8.17.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.x\",\"label\":\"v8.18.0\",\"branchLabelMappingKey\":\"^v8.18.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.2\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Dmitrii Shevchenko <dmitrii.shevchenko@elastic.co>"}},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/202697","number":202697,"state":"MERGED","mergeCommit":{"sha":"8c9181aa48796a8467e38ad1431238ebaa78de7e","message":"[8.x] [Security Solution] Skip isCustomized calculation when the feature flag is off (#201825) (#202697)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Solution] Skip isCustomized calculation when the feature\nflag is off (#201825)](https://github.com/elastic/kibana/pull/201825)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Dmitrii\nShevchenko\",\"email\":\"dmitrii.shevchenko@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-12-03T12:11:24Z\",\"message\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is off\n(#201825)\\n\\n**Resolves:\nhttps://github.com//issues/201632**\\r\\n\\r\\n## Summary\n\\r\\n\\r\\nWhen the rule customization feature flag is disabled, we should\nalways\\r\\nreturn `isCustomized: false`, regardless of any changes\nintroduced to a\\r\\nrule. This ensures that we do not accidentally mark\nprebuilt rules as\\r\\ncustomized in 8.16 with the feature flag off. For\nmore details, refer to\\r\\nthe related issue:\nhttps://github.com//issues/201632\\r\\n\\r\\n### Main Changes\n\\r\\n\\r\\n- The primary change in this PR is encapsulated in\nthe\\r\\n`calculateIsCustomized` function\\r\\n- Other changes involve\npassing the feature flag to this function\\r\\n- Added integration tests\nto cover all API CRUD operations that can be\\r\\nperformed with\nrules\",\"sha\":\"22911c1828f40160cf3a2935300aec18c11b56e9\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:skip\",\"v9.0.0\",\"Team:Detections\nand Resp\",\"Team: SecuritySolution\",\"Team:Detection Rule\nManagement\",\"Feature:Prebuilt Detection\nRules\",\"backport:version\",\"v8.17.0\",\"v8.18.0\",\"v8.16.2\"],\"title\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is\noff\",\"number\":201825,\"url\":\"https://github.com/elastic/kibana/pull/201825\",\"mergeCommit\":{\"message\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is off\n(#201825)\\n\\n**Resolves:\nhttps://github.com//issues/201632**\\r\\n\\r\\n## Summary\n\\r\\n\\r\\nWhen the rule customization feature flag is disabled, we should\nalways\\r\\nreturn `isCustomized: false`, regardless of any changes\nintroduced to a\\r\\nrule. This ensures that we do not accidentally mark\nprebuilt rules as\\r\\ncustomized in 8.16 with the feature flag off. For\nmore details, refer to\\r\\nthe related issue:\nhttps://github.com//issues/201632\\r\\n\\r\\n### Main Changes\n\\r\\n\\r\\n- The primary change in this PR is encapsulated in\nthe\\r\\n`calculateIsCustomized` function\\r\\n- Other changes involve\npassing the feature flag to this function\\r\\n- Added integration tests\nto cover all API CRUD operations that can be\\r\\nperformed with\nrules\",\"sha\":\"22911c1828f40160cf3a2935300aec18c11b56e9\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.17\",\"8.x\",\"8.16\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/201825\",\"number\":201825,\"mergeCommit\":{\"message\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is off\n(#201825)\\n\\n**Resolves:\nhttps://github.com//issues/201632**\\r\\n\\r\\n## Summary\n\\r\\n\\r\\nWhen the rule customization feature flag is disabled, we should\nalways\\r\\nreturn `isCustomized: false`, regardless of any changes\nintroduced to a\\r\\nrule. This ensures that we do not accidentally mark\nprebuilt rules as\\r\\ncustomized in 8.16 with the feature flag off. For\nmore details, refer to\\r\\nthe related issue:\nhttps://github.com//issues/201632\\r\\n\\r\\n### Main Changes\n\\r\\n\\r\\n- The primary change in this PR is encapsulated in\nthe\\r\\n`calculateIsCustomized` function\\r\\n- Other changes involve\npassing the feature flag to this function\\r\\n- Added integration tests\nto cover all API CRUD operations that can be\\r\\nperformed with\nrules\",\"sha\":\"22911c1828f40160cf3a2935300aec18c11b56e9\"}},{\"branch\":\"8.17\",\"label\":\"v8.17.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.x\",\"label\":\"v8.18.0\",\"branchLabelMappingKey\":\"^v8.18.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.2\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Dmitrii Shevchenko <dmitrii.shevchenko@elastic.co>"}},{"branch":"8.16","label":"v8.16.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
…kbn requests (#201915) (#202676) # Backport This will backport the following commits from `main` to `8.16`: - [[Console] Only `copy as curl` should be allowed for kbn requests (#201915)](#201915) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ignacio Rivas","email":"rivasign@gmail.com"},"sourceCommit":{"committedDate":"2024-12-03T11:07:48Z","message":"[Console] Only `copy as curl` should be allowed for kbn requests (#201915)","sha":"27e828c669aa7e0ec39ddc2b0707b583e84be9d9","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-minor","v8.16.0","v8.17.0"],"title":"[Console] Only `copy as curl` should be allowed for kbn requests","number":201915,"url":"https://github.com/elastic/kibana/pull/201915","mergeCommit":{"message":"[Console] Only `copy as curl` should be allowed for kbn requests (#201915)","sha":"27e828c669aa7e0ec39ddc2b0707b583e84be9d9"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201915","number":201915,"mergeCommit":{"message":"[Console] Only `copy as curl` should be allowed for kbn requests (#201915)","sha":"27e828c669aa7e0ec39ddc2b0707b583e84be9d9"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ignacio Rivas <rivasign@gmail.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
…02919) # Backport This will backport the following commits from `main` to `8.16`: - [Updates 'Create and manage rules' page (#202648)](#202648) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"kosabogi","email":"105062005+kosabogi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-04T13:25:44Z","message":"Updates 'Create and manage rules' page (#202648)\n\n### Overview\r\n\r\nThis PR updates the [Create and manage\r\nrules](http://localhost:8000/guide/create-and-manage-rules.html) page:\r\n- by adding a new screenshot showing how to navigate to the Rules page.\r\n- updating the instructions based on this\r\n[issue's](https://github.com/elastic/docs-content/issues/96\r\n) suggestion.\r\n\r\n### Related issue\r\n\r\nhttps://github.com/elastic/docs-content/issues/96\r\n\r\n(Based on my discussion with @tatianafinamor, this issue suggests\r\nupdating the [Kibana guide > Create and manage\r\nrules](https://www.elastic.co/guide/en/kibana/master/create-and-manage-rules.html)\r\npage, not the Serverless guide. Users need clearer guidance on how to\r\nnavigate to the **Rules** section.","sha":"d754458aebef14e4dafabe9ea6274b6c9bdf6122","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","v8.16.0","backport:version","v8.17.0","v8.18.0"],"title":"Updates 'Create and manage rules' page","number":202648,"url":"https://github.com/elastic/kibana/pull/202648","mergeCommit":{"message":"Updates 'Create and manage rules' page (#202648)\n\n### Overview\r\n\r\nThis PR updates the [Create and manage\r\nrules](http://localhost:8000/guide/create-and-manage-rules.html) page:\r\n- by adding a new screenshot showing how to navigate to the Rules page.\r\n- updating the instructions based on this\r\n[issue's](https://github.com/elastic/docs-content/issues/96\r\n) suggestion.\r\n\r\n### Related issue\r\n\r\nhttps://github.com/elastic/docs-content/issues/96\r\n\r\n(Based on my discussion with @tatianafinamor, this issue suggests\r\nupdating the [Kibana guide > Create and manage\r\nrules](https://www.elastic.co/guide/en/kibana/master/create-and-manage-rules.html)\r\npage, not the Serverless guide. Users need clearer guidance on how to\r\nnavigate to the **Rules** section.","sha":"d754458aebef14e4dafabe9ea6274b6c9bdf6122"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202648","number":202648,"mergeCommit":{"message":"Updates 'Create and manage rules' page (#202648)\n\n### Overview\r\n\r\nThis PR updates the [Create and manage\r\nrules](http://localhost:8000/guide/create-and-manage-rules.html) page:\r\n- by adding a new screenshot showing how to navigate to the Rules page.\r\n- updating the instructions based on this\r\n[issue's](https://github.com/elastic/docs-content/issues/96\r\n) suggestion.\r\n\r\n### Related issue\r\n\r\nhttps://github.com/elastic/docs-content/issues/96\r\n\r\n(Based on my discussion with @tatianafinamor, this issue suggests\r\nupdating the [Kibana guide > Create and manage\r\nrules](https://www.elastic.co/guide/en/kibana/master/create-and-manage-rules.html)\r\npage, not the Serverless guide. Users need clearer guidance on how to\r\nnavigate to the **Rules** section.","sha":"d754458aebef14e4dafabe9ea6274b6c9bdf6122"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: kosabogi <105062005+kosabogi@users.noreply.github.com>
…ew rule form (#202315) (#202932) # Backport This will backport the following commits from `main` to `8.16`: - [[ResponseOps][Alerting] Show missing Slack connectors in the new rule form (#202315)](#202315) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Georgiana-Andreea Onoleață","email":"georgiana.onoleata@elastic.co"},"sourceCommit":{"committedDate":"2024-12-04T14:05:38Z","message":"[ResponseOps][Alerting] Show missing Slack connectors in the new rule form (#202315)\n\nCloses https://github.com/elastic/kibana/issues/201673\r\n\r\n## Summary\r\n\r\n- changed the logic to create the connectorsMap (which gives us the\r\nconnector type filters):\r\n- Only the '**slack'** and **'slack API'** connector types include a\r\n`subtype` array. I updated the logic so that when the `actionTypeModel`\r\nhas **hideInUi** set to true (indicating a 'slack API' connector), it\r\nsearches for a **'slack'** connector in the subtype. If a **'slack'**\r\nconnector is found, `otherActionTypeId` is set to 'slack'; otherwise, it\r\nis set to `undefined`. This effectively \"maps\" the 'slack API' type to\r\nthe 'slack' type within the `connectorsMap`\r\n\r\n- changed the logic to create the `filteredConnectors` (which gives us\r\nthe connectors to display, filtered after the type):\r\n- The **selectedConnectorType** can only be '**slack'** because, in the\r\n`connectorsMap`, the '**slack API'** option has already been mapped to\r\n'**slack'** and is no longer included as a separate type.\r\n- If the `subtype` includes **'slack',** the filter will return\r\nconnectors with `actionTypeId` of either 'slack' or 'slack API'.\r\n- This ensures that both 'slack' and 'slack API' connectors are\r\ndisplayed, as 'slack API' is associated with the 'slack' type through\r\nthe subtype.\r\n \r\n\r\n\r\nhttps://github.com/user-attachments/assets/9cccaf42-b6db-4eea-b2fd-8f37f0e24745\r\n\r\n## Release note\r\nFix Slack API connectors not displayed under Slack connector type when\r\nadding new connector to rule.","sha":"2884d903de43c5f846a96385215b303397826973","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:ResponseOps","v9.0.0","backport:prev-minor","v8.17.0","v8.16.2"],"title":"[ResponseOps][Alerting] Show missing Slack connectors in the new rule form","number":202315,"url":"https://github.com/elastic/kibana/pull/202315","mergeCommit":{"message":"[ResponseOps][Alerting] Show missing Slack connectors in the new rule form (#202315)\n\nCloses https://github.com/elastic/kibana/issues/201673\r\n\r\n## Summary\r\n\r\n- changed the logic to create the connectorsMap (which gives us the\r\nconnector type filters):\r\n- Only the '**slack'** and **'slack API'** connector types include a\r\n`subtype` array. I updated the logic so that when the `actionTypeModel`\r\nhas **hideInUi** set to true (indicating a 'slack API' connector), it\r\nsearches for a **'slack'** connector in the subtype. If a **'slack'**\r\nconnector is found, `otherActionTypeId` is set to 'slack'; otherwise, it\r\nis set to `undefined`. This effectively \"maps\" the 'slack API' type to\r\nthe 'slack' type within the `connectorsMap`\r\n\r\n- changed the logic to create the `filteredConnectors` (which gives us\r\nthe connectors to display, filtered after the type):\r\n- The **selectedConnectorType** can only be '**slack'** because, in the\r\n`connectorsMap`, the '**slack API'** option has already been mapped to\r\n'**slack'** and is no longer included as a separate type.\r\n- If the `subtype` includes **'slack',** the filter will return\r\nconnectors with `actionTypeId` of either 'slack' or 'slack API'.\r\n- This ensures that both 'slack' and 'slack API' connectors are\r\ndisplayed, as 'slack API' is associated with the 'slack' type through\r\nthe subtype.\r\n \r\n\r\n\r\nhttps://github.com/user-attachments/assets/9cccaf42-b6db-4eea-b2fd-8f37f0e24745\r\n\r\n## Release note\r\nFix Slack API connectors not displayed under Slack connector type when\r\nadding new connector to rule.","sha":"2884d903de43c5f846a96385215b303397826973"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202315","number":202315,"mergeCommit":{"message":"[ResponseOps][Alerting] Show missing Slack connectors in the new rule form (#202315)\n\nCloses https://github.com/elastic/kibana/issues/201673\r\n\r\n## Summary\r\n\r\n- changed the logic to create the connectorsMap (which gives us the\r\nconnector type filters):\r\n- Only the '**slack'** and **'slack API'** connector types include a\r\n`subtype` array. I updated the logic so that when the `actionTypeModel`\r\nhas **hideInUi** set to true (indicating a 'slack API' connector), it\r\nsearches for a **'slack'** connector in the subtype. If a **'slack'**\r\nconnector is found, `otherActionTypeId` is set to 'slack'; otherwise, it\r\nis set to `undefined`. This effectively \"maps\" the 'slack API' type to\r\nthe 'slack' type within the `connectorsMap`\r\n\r\n- changed the logic to create the `filteredConnectors` (which gives us\r\nthe connectors to display, filtered after the type):\r\n- The **selectedConnectorType** can only be '**slack'** because, in the\r\n`connectorsMap`, the '**slack API'** option has already been mapped to\r\n'**slack'** and is no longer included as a separate type.\r\n- If the `subtype` includes **'slack',** the filter will return\r\nconnectors with `actionTypeId` of either 'slack' or 'slack API'.\r\n- This ensures that both 'slack' and 'slack API' connectors are\r\ndisplayed, as 'slack API' is associated with the 'slack' type through\r\nthe subtype.\r\n \r\n\r\n\r\nhttps://github.com/user-attachments/assets/9cccaf42-b6db-4eea-b2fd-8f37f0e24745\r\n\r\n## Release note\r\nFix Slack API connectors not displayed under Slack connector type when\r\nadding new connector to rule.","sha":"2884d903de43c5f846a96385215b303397826973"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Georgiana-Andreea Onoleață <georgiana.onoleata@elastic.co>
…ess (#202885) (#202942) # Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] Fix PATCH rule API test failure in Serverless (#202885)](#202885) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2024-12-04T13:53:41Z","message":"[Security Solution] Fix PATCH rule API test failure in Serverless (#202885)\n\n**Resolves: https://github.com/elastic/kibana/issues/202812**\r\n\r\n## Summary\r\nThis PR fixes a problem in the MKI Serverless periodic pipeline that was\r\nintroduced in #201825. The issue happened because the test tried to\r\ndelete prebuilt rule assets stored in .kibana_security_solution, but you\r\ncan’t access this index in Serverless MKI.\r\n\r\nThe fix makes sure this call only runs in non-Serverless MKI\r\nenvironments.","sha":"0e10dbfc8190c77ed684284a4b2dc53eada437ea","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","backport:version","v8.17.0","v8.18.0","v8.16.2"],"number":202885,"url":"https://github.com/elastic/kibana/pull/202885","mergeCommit":{"message":"[Security Solution] Fix PATCH rule API test failure in Serverless (#202885)\n\n**Resolves: https://github.com/elastic/kibana/issues/202812**\r\n\r\n## Summary\r\nThis PR fixes a problem in the MKI Serverless periodic pipeline that was\r\nintroduced in #201825. The issue happened because the test tried to\r\ndelete prebuilt rule assets stored in .kibana_security_solution, but you\r\ncan’t access this index in Serverless MKI.\r\n\r\nThe fix makes sure this call only runs in non-Serverless MKI\r\nenvironments.","sha":"0e10dbfc8190c77ed684284a4b2dc53eada437ea"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202885","number":202885,"mergeCommit":{"message":"[Security Solution] Fix PATCH rule API test failure in Serverless (#202885)\n\n**Resolves: https://github.com/elastic/kibana/issues/202812**\r\n\r\n## Summary\r\nThis PR fixes a problem in the MKI Serverless periodic pipeline that was\r\nintroduced in #201825. The issue happened because the test tried to\r\ndelete prebuilt rule assets stored in .kibana_security_solution, but you\r\ncan’t access this index in Serverless MKI.\r\n\r\nThe fix makes sure this call only runs in non-Serverless MKI\r\nenvironments.","sha":"0e10dbfc8190c77ed684284a4b2dc53eada437ea"}},{"branch":"8.17","label":"v8.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
…02951) # Backport This will backport the following commits from `main` to `8.16`: - [[Console] Add highlighting for painless language (#202695)](#202695) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-04T14:48:16Z","message":"[Console] Add highlighting for painless language (#202695)\n\nCloses https://github.com/elastic/kibana/issues/201672?reload=1?reload=1\r\n\r\n## Summary\r\n\r\nThis PR adds existing painless rules to the console language so that the\r\npainless scripts are correctly highlighted. We are adding a painless\r\nstarting rule that matches a string `\"*_script\"`, `\"inline\"`, or\r\n`\"source\"`, followed by a triple quote, in order to prevent clashing\r\nwith the existing rules for triple-quote strings.\r\n\r\nExample request with a script:\r\n\r\n```\r\nPOST _ingest/pipeline/_simulate\r\n{\r\n \"pipeline\": { \r\n \"processors\": [\r\n {\r\n \"script\": {\r\n \"description\": \"Extract 'tags' from 'env' field\",\r\n \"lang\": \"painless\",\r\n \"source\": \"\"\"\r\n String[] envSplit = ctx['env'].splitOnToken(params['delimiter']);\r\n ArrayList tags = new ArrayList();\r\n tags.add(envSplit[params['position']].trim());\r\n ctx['tags'] = tags;\r\n \"\"\",\r\n \"params\": {\r\n \"delimiter\": \"-\",\r\n \"position\": 1\r\n }\r\n }\r\n }\r\n ]\r\n },\r\n \"docs\": [\r\n {\r\n \"_source\": {\r\n \"env\": \"es01-prod\"\r\n }\r\n }\r\n ]\r\n}\r\n```\r\n\r\n<img width=\"1049\" alt=\"Screenshot 2024-12-03 at 12 02 52\"\r\nsrc=\"https://github.com/user-attachments/assets/fb249953-a998-40c0-9775-3474e15b5de2\">","sha":"2fcd323927e42b4e7648f2aaa1a38dd3c7ea3900","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-minor","v8.16.0","v8.17.0"],"title":"[Console] Add highlighting for painless language","number":202695,"url":"https://github.com/elastic/kibana/pull/202695","mergeCommit":{"message":"[Console] Add highlighting for painless language (#202695)\n\nCloses https://github.com/elastic/kibana/issues/201672?reload=1?reload=1\r\n\r\n## Summary\r\n\r\nThis PR adds existing painless rules to the console language so that the\r\npainless scripts are correctly highlighted. We are adding a painless\r\nstarting rule that matches a string `\"*_script\"`, `\"inline\"`, or\r\n`\"source\"`, followed by a triple quote, in order to prevent clashing\r\nwith the existing rules for triple-quote strings.\r\n\r\nExample request with a script:\r\n\r\n```\r\nPOST _ingest/pipeline/_simulate\r\n{\r\n \"pipeline\": { \r\n \"processors\": [\r\n {\r\n \"script\": {\r\n \"description\": \"Extract 'tags' from 'env' field\",\r\n \"lang\": \"painless\",\r\n \"source\": \"\"\"\r\n String[] envSplit = ctx['env'].splitOnToken(params['delimiter']);\r\n ArrayList tags = new ArrayList();\r\n tags.add(envSplit[params['position']].trim());\r\n ctx['tags'] = tags;\r\n \"\"\",\r\n \"params\": {\r\n \"delimiter\": \"-\",\r\n \"position\": 1\r\n }\r\n }\r\n }\r\n ]\r\n },\r\n \"docs\": [\r\n {\r\n \"_source\": {\r\n \"env\": \"es01-prod\"\r\n }\r\n }\r\n ]\r\n}\r\n```\r\n\r\n<img width=\"1049\" alt=\"Screenshot 2024-12-03 at 12 02 52\"\r\nsrc=\"https://github.com/user-attachments/assets/fb249953-a998-40c0-9775-3474e15b5de2\">","sha":"2fcd323927e42b4e7648f2aaa1a38dd3c7ea3900"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202695","number":202695,"mergeCommit":{"message":"[Console] Add highlighting for painless language (#202695)\n\nCloses https://github.com/elastic/kibana/issues/201672?reload=1?reload=1\r\n\r\n## Summary\r\n\r\nThis PR adds existing painless rules to the console language so that the\r\npainless scripts are correctly highlighted. We are adding a painless\r\nstarting rule that matches a string `\"*_script\"`, `\"inline\"`, or\r\n`\"source\"`, followed by a triple quote, in order to prevent clashing\r\nwith the existing rules for triple-quote strings.\r\n\r\nExample request with a script:\r\n\r\n```\r\nPOST _ingest/pipeline/_simulate\r\n{\r\n \"pipeline\": { \r\n \"processors\": [\r\n {\r\n \"script\": {\r\n \"description\": \"Extract 'tags' from 'env' field\",\r\n \"lang\": \"painless\",\r\n \"source\": \"\"\"\r\n String[] envSplit = ctx['env'].splitOnToken(params['delimiter']);\r\n ArrayList tags = new ArrayList();\r\n tags.add(envSplit[params['position']].trim());\r\n ctx['tags'] = tags;\r\n \"\"\",\r\n \"params\": {\r\n \"delimiter\": \"-\",\r\n \"position\": 1\r\n }\r\n }\r\n }\r\n ]\r\n },\r\n \"docs\": [\r\n {\r\n \"_source\": {\r\n \"env\": \"es01-prod\"\r\n }\r\n }\r\n ]\r\n}\r\n```\r\n\r\n<img width=\"1049\" alt=\"Screenshot 2024-12-03 at 12 02 52\"\r\nsrc=\"https://github.com/user-attachments/assets/fb249953-a998-40c0-9775-3474e15b5de2\">","sha":"2fcd323927e42b4e7648f2aaa1a38dd3c7ea3900"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com>
# Backport This will backport the following commits from `main` to `8.16`: - [[SLOs] Added $state into filters schema !! (#202887)](#202887) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2024-12-05T09:12:48Z","message":"[SLOs] Added $state into filters schema !! (#202887)\n\n## Summary\r\n\r\nfixes https://github.com/elastic/kibana/issues/202999\r\n\r\nAdded $state into filters schema !!","sha":"51e63eeaccd9998d473ef62d11d530697a836e7f","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-major"],"title":"[SLOs] Added $state into filters schema !!","number":202887,"url":"https://github.com/elastic/kibana/pull/202887","mergeCommit":{"message":"[SLOs] Added $state into filters schema !! (#202887)\n\n## Summary\r\n\r\nfixes https://github.com/elastic/kibana/issues/202999\r\n\r\nAdded $state into filters schema !!","sha":"51e63eeaccd9998d473ef62d11d530697a836e7f"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202887","number":202887,"mergeCommit":{"message":"[SLOs] Added $state into filters schema !! (#202887)\n\n## Summary\r\n\r\nfixes https://github.com/elastic/kibana/issues/202999\r\n\r\nAdded $state into filters schema !!","sha":"51e63eeaccd9998d473ef62d11d530697a836e7f"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com>
… (#202987) # Backport This will backport the following commits from `main` to `8.16`: - [[ResponseOps][Cases] Fix edit cases settings privilege (#202053)](#202053) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Janki Salvi","email":"117571355+js-jankisalvi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-04T15:55:08Z","message":"[ResponseOps][Cases] Fix edit cases settings privilege (#202053)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/197650\r\n\r\nAlso fixes an issue where user has `cases: all ` and `edit case\r\nsettings: false`, user was able to edit settings.\r\n\r\nUsed `permissions.settings` instead of `permissions.update` and\r\n`permissions.create` for custom fields and templates.\r\n\r\n### How to test\r\n- Verify by creating a user with different combinations of cases and\r\nedit case settings privileges\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"8e8ba53116c16cc9b9122de27415cf8519cc1863","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","v9.0.0","Feature:Cases","backport:prev-minor","v8.17.0","v8.18.0","v8.16.2"],"number":202053,"url":"https://github.com/elastic/kibana/pull/202053","mergeCommit":{"message":"[ResponseOps][Cases] Fix edit cases settings privilege (#202053)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/197650\r\n\r\nAlso fixes an issue where user has `cases: all ` and `edit case\r\nsettings: false`, user was able to edit settings.\r\n\r\nUsed `permissions.settings` instead of `permissions.update` and\r\n`permissions.create` for custom fields and templates.\r\n\r\n### How to test\r\n- Verify by creating a user with different combinations of cases and\r\nedit case settings privileges\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"8e8ba53116c16cc9b9122de27415cf8519cc1863"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202053","number":202053,"mergeCommit":{"message":"[ResponseOps][Cases] Fix edit cases settings privilege (#202053)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/197650\r\n\r\nAlso fixes an issue where user has `cases: all ` and `edit case\r\nsettings: false`, user was able to edit settings.\r\n\r\nUsed `permissions.settings` instead of `permissions.update` and\r\n`permissions.create` for custom fields and templates.\r\n\r\n### How to test\r\n- Verify by creating a user with different combinations of cases and\r\nedit case settings privileges\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"8e8ba53116c16cc9b9122de27415cf8519cc1863"}},{"branch":"8.17","label":"v8.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/202970","number":202970,"state":"OPEN"},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/202971","number":202971,"state":"OPEN"},{"branch":"8.16","label":"v8.16.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
…bles (#202947) (#203090) # Backport This will backport the following commits from `main` to `8.16`: - [[Discover] Support "Inspect" in saved search embeddables (#202947)](#202947) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2024-12-05T12:04:01Z","message":"[Discover] Support \"Inspect\" in saved search embeddables (#202947)\n\n- Closes https://github.com/elastic/kibana/issues/202301\r\n\r\n## Summary\r\n\r\nThis PR enables \"Inspect\" option for saved search Dashboard panels.\r\n\r\n<img width=\"1619\" alt=\"Screenshot 2024-12-04 at 16 02 33\"\r\nsrc=\"https://github.com/user-attachments/assets/a1eab597-4683-4069-b48f-b33b977db578\">\r\n<img width=\"1620\" alt=\"Screenshot 2024-12-04 at 16 02 43\"\r\nsrc=\"https://github.com/user-attachments/assets/0dc734c3-f930-4397-9b68-69d959400924\">\r\n<img width=\"1618\" alt=\"Screenshot 2024-12-04 at 16 03 03\"\r\nsrc=\"https://github.com/user-attachments/assets/460d8432-dc14-480e-b49d-81ab743815d2\">\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"3f0008ab5d38fd070b121e2e710ec6fff6efcd07","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:DataDiscovery","v8.16.0","backport:version","v8.17.0","v8.18.0"],"title":"[Discover] Support \"Inspect\" in saved search embeddables","number":202947,"url":"https://github.com/elastic/kibana/pull/202947","mergeCommit":{"message":"[Discover] Support \"Inspect\" in saved search embeddables (#202947)\n\n- Closes https://github.com/elastic/kibana/issues/202301\r\n\r\n## Summary\r\n\r\nThis PR enables \"Inspect\" option for saved search Dashboard panels.\r\n\r\n<img width=\"1619\" alt=\"Screenshot 2024-12-04 at 16 02 33\"\r\nsrc=\"https://github.com/user-attachments/assets/a1eab597-4683-4069-b48f-b33b977db578\">\r\n<img width=\"1620\" alt=\"Screenshot 2024-12-04 at 16 02 43\"\r\nsrc=\"https://github.com/user-attachments/assets/0dc734c3-f930-4397-9b68-69d959400924\">\r\n<img width=\"1618\" alt=\"Screenshot 2024-12-04 at 16 03 03\"\r\nsrc=\"https://github.com/user-attachments/assets/460d8432-dc14-480e-b49d-81ab743815d2\">\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"3f0008ab5d38fd070b121e2e710ec6fff6efcd07"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202947","number":202947,"mergeCommit":{"message":"[Discover] Support \"Inspect\" in saved search embeddables (#202947)\n\n- Closes https://github.com/elastic/kibana/issues/202301\r\n\r\n## Summary\r\n\r\nThis PR enables \"Inspect\" option for saved search Dashboard panels.\r\n\r\n<img width=\"1619\" alt=\"Screenshot 2024-12-04 at 16 02 33\"\r\nsrc=\"https://github.com/user-attachments/assets/a1eab597-4683-4069-b48f-b33b977db578\">\r\n<img width=\"1620\" alt=\"Screenshot 2024-12-04 at 16 02 43\"\r\nsrc=\"https://github.com/user-attachments/assets/0dc734c3-f930-4397-9b68-69d959400924\">\r\n<img width=\"1618\" alt=\"Screenshot 2024-12-04 at 16 03 03\"\r\nsrc=\"https://github.com/user-attachments/assets/460d8432-dc14-480e-b49d-81ab743815d2\">\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"3f0008ab5d38fd070b121e2e710ec6fff6efcd07"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co>
… (#202988) # Backport This will backport the following commits from `main` to `8.16`: - [[Synthetics] Fix overview trends for read-only user !! (#202914)](#202914) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2024-12-04T17:24:07Z","message":"[Synthetics] Fix overview trends for read-only user !! (#202914)\n\n## Summary\r\n\r\nFix overview trends for read-only user , we wrongly assume that this\r\n`POST` route needs write permission.","sha":"16817cc44dd02fbb9b7e10e7d03871c299267dfb","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","ci:project-deploy-observability","Team:obs-ux-management","backport:version","v8.17.0","v8.18.0","v8.16.3"],"title":"[Synthetics] Fix overview trends for read-only user !!","number":202914,"url":"https://github.com/elastic/kibana/pull/202914","mergeCommit":{"message":"[Synthetics] Fix overview trends for read-only user !! (#202914)\n\n## Summary\r\n\r\nFix overview trends for read-only user , we wrongly assume that this\r\n`POST` route needs write permission.","sha":"16817cc44dd02fbb9b7e10e7d03871c299267dfb"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202914","number":202914,"mergeCommit":{"message":"[Synthetics] Fix overview trends for read-only user !! (#202914)\n\n## Summary\r\n\r\nFix overview trends for read-only user , we wrongly assume that this\r\n`POST` route needs write permission.","sha":"16817cc44dd02fbb9b7e10e7d03871c299267dfb"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Shahzad <shahzad31comp@gmail.com>
…202463) (#203115) # Backport This will backport the following commits from `main` to `8.16`: - [Add prompt for connector configuration being in editable mode (#202463)](#202463) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Artem Shelkovnikov","email":"artem.shelkovnikov@elastic.co"},"sourceCommit":{"committedDate":"2024-12-05T14:44:16Z","message":"Add prompt for connector configuration being in editable mode (#202463)\n\n### Closes https://github.com/elastic/search-team/issues/8547\r\n## Summary\r\n\r\nUser creates connectors following a set of steps. During configuration\r\nstep they are able to open configuration form and then click \"Next\" -\r\nconfiguration will not be saved and user will not be prompted about it.\r\n\r\nThis change adds a prompt for this step - if the configuration is in\r\neditable state, the prompt will be shown. It does not check that the\r\nform was edited, however, and it's on purpose. I'm open to changing it\r\nto only prompt if any value changed, but I feel that it's important to\r\nprompt even if no values were entered, just to confirm with the user\r\nthat they want to move on without specifying any values.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/af768d6d-282d-4f67-a1d0-c54bcf1cb2d0\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b8a41013ca6f13bea26dd78eaed990104741dc40","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-major"],"title":"Add prompt for connector configuration being in editable mode","number":202463,"url":"https://github.com/elastic/kibana/pull/202463","mergeCommit":{"message":"Add prompt for connector configuration being in editable mode (#202463)\n\n### Closes https://github.com/elastic/search-team/issues/8547\r\n## Summary\r\n\r\nUser creates connectors following a set of steps. During configuration\r\nstep they are able to open configuration form and then click \"Next\" -\r\nconfiguration will not be saved and user will not be prompted about it.\r\n\r\nThis change adds a prompt for this step - if the configuration is in\r\neditable state, the prompt will be shown. It does not check that the\r\nform was edited, however, and it's on purpose. I'm open to changing it\r\nto only prompt if any value changed, but I feel that it's important to\r\nprompt even if no values were entered, just to confirm with the user\r\nthat they want to move on without specifying any values.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/af768d6d-282d-4f67-a1d0-c54bcf1cb2d0\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b8a41013ca6f13bea26dd78eaed990104741dc40"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202463","number":202463,"mergeCommit":{"message":"Add prompt for connector configuration being in editable mode (#202463)\n\n### Closes https://github.com/elastic/search-team/issues/8547\r\n## Summary\r\n\r\nUser creates connectors following a set of steps. During configuration\r\nstep they are able to open configuration form and then click \"Next\" -\r\nconfiguration will not be saved and user will not be prompted about it.\r\n\r\nThis change adds a prompt for this step - if the configuration is in\r\neditable state, the prompt will be shown. It does not check that the\r\nform was edited, however, and it's on purpose. I'm open to changing it\r\nto only prompt if any value changed, but I feel that it's important to\r\nprompt even if no values were entered, just to confirm with the user\r\nthat they want to move on without specifying any values.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/af768d6d-282d-4f67-a1d0-c54bcf1cb2d0\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b8a41013ca6f13bea26dd78eaed990104741dc40"}}]}] BACKPORT--> Co-authored-by: Artem Shelkovnikov <artem.shelkovnikov@elastic.co>
) (#203075) # Backport This will backport the following commits from `main` to `8.16`: - [[APM] `Time spent by span type` chart rendering problems (#202755)](#202755) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Milosz Marcinkowski","email":"38698566+miloszmarcinkowski@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-05T10:08:05Z","message":"[APM] `Time spent by span type` chart rendering problems (#202755)\n\nCloses #202343\r\n\r\n## Summary\r\n\r\nThis PR solves the following issues in `Time spent by span type` chart:\r\n- limits percentages between 0% and 100% (converts negative values to\r\n0%),\r\n\r\nbefore: \r\n<img width=\"1134\" alt=\"Screenshot 2024-12-04 at 15 28 18\"\r\nsrc=\"https://github.com/user-attachments/assets/73285e87-3aef-4b2d-8e2a-7e3ec87680f3\">\r\nafter:\r\n<img width=\"1135\" alt=\"Screenshot 2024-12-04 at 15 30 25\"\r\nsrc=\"https://github.com/user-attachments/assets/ae25cb85-d31a-490a-96c7-d4475952c734\">\r\n\r\n---\r\n\r\n- rounds percentage to 8 decimal points to prevent scientific notation\r\nin charts (poor readability)\r\n\r\nbefore: \r\n<img width=\"1132\" alt=\"Screenshot 2024-12-04 at 14 36 54\"\r\nsrc=\"https://github.com/user-attachments/assets/528cda4b-ae84-4dbd-9d3f-88896e63a369\">\r\nafter:\r\n<img width=\"1132\" alt=\"Screenshot 2024-12-04 at 14 35 39\"\r\nsrc=\"https://github.com/user-attachments/assets/9a0bdce9-6d66-4aaf-a131-18644eab1892\">","sha":"ab9de649fe32b22b4f847d190be73fbf229a1ac8","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services"],"number":202755,"url":"https://github.com/elastic/kibana/pull/202755","mergeCommit":{"message":"[APM] `Time spent by span type` chart rendering problems (#202755)\n\nCloses #202343\r\n\r\n## Summary\r\n\r\nThis PR solves the following issues in `Time spent by span type` chart:\r\n- limits percentages between 0% and 100% (converts negative values to\r\n0%),\r\n\r\nbefore: \r\n<img width=\"1134\" alt=\"Screenshot 2024-12-04 at 15 28 18\"\r\nsrc=\"https://github.com/user-attachments/assets/73285e87-3aef-4b2d-8e2a-7e3ec87680f3\">\r\nafter:\r\n<img width=\"1135\" alt=\"Screenshot 2024-12-04 at 15 30 25\"\r\nsrc=\"https://github.com/user-attachments/assets/ae25cb85-d31a-490a-96c7-d4475952c734\">\r\n\r\n---\r\n\r\n- rounds percentage to 8 decimal points to prevent scientific notation\r\nin charts (poor readability)\r\n\r\nbefore: \r\n<img width=\"1132\" alt=\"Screenshot 2024-12-04 at 14 36 54\"\r\nsrc=\"https://github.com/user-attachments/assets/528cda4b-ae84-4dbd-9d3f-88896e63a369\">\r\nafter:\r\n<img width=\"1132\" alt=\"Screenshot 2024-12-04 at 14 35 39\"\r\nsrc=\"https://github.com/user-attachments/assets/9a0bdce9-6d66-4aaf-a131-18644eab1892\">","sha":"ab9de649fe32b22b4f847d190be73fbf229a1ac8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202755","number":202755,"mergeCommit":{"message":"[APM] `Time spent by span type` chart rendering problems (#202755)\n\nCloses #202343\r\n\r\n## Summary\r\n\r\nThis PR solves the following issues in `Time spent by span type` chart:\r\n- limits percentages between 0% and 100% (converts negative values to\r\n0%),\r\n\r\nbefore: \r\n<img width=\"1134\" alt=\"Screenshot 2024-12-04 at 15 28 18\"\r\nsrc=\"https://github.com/user-attachments/assets/73285e87-3aef-4b2d-8e2a-7e3ec87680f3\">\r\nafter:\r\n<img width=\"1135\" alt=\"Screenshot 2024-12-04 at 15 30 25\"\r\nsrc=\"https://github.com/user-attachments/assets/ae25cb85-d31a-490a-96c7-d4475952c734\">\r\n\r\n---\r\n\r\n- rounds percentage to 8 decimal points to prevent scientific notation\r\nin charts (poor readability)\r\n\r\nbefore: \r\n<img width=\"1132\" alt=\"Screenshot 2024-12-04 at 14 36 54\"\r\nsrc=\"https://github.com/user-attachments/assets/528cda4b-ae84-4dbd-9d3f-88896e63a369\">\r\nafter:\r\n<img width=\"1132\" alt=\"Screenshot 2024-12-04 at 14 35 39\"\r\nsrc=\"https://github.com/user-attachments/assets/9a0bdce9-6d66-4aaf-a131-18644eab1892\">","sha":"ab9de649fe32b22b4f847d190be73fbf229a1ac8"}},{"url":"https://github.com/elastic/kibana/pull/203066","number":203066,"branch":"8.x","state":"OPEN"}]}] BACKPORT-->
…e new rule form in serverless (#200727) (#203127) # Backport This will backport the following commits from `main` to `8.16`: - [[ResponseOps][Rules] Hide the "Role visibility" dropdown in the new rule form in serverless (#200727)](#200727) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Antonio","email":"antonio.coelho@elastic.co"},"sourceCommit":{"committedDate":"2024-12-05T11:20:37Z","message":"[ResponseOps][Rules] Hide the \"Role visibility\" dropdown in the new rule form in serverless (#200727)\n\nFixes #199642\r\n\r\n## Summary\r\n\r\n~~This PR hides the role visibility dropdown in the new rule form when\r\nin serverless.~~\r\n\r\nThis PR hides the role visibility dropdown in the new rule form **when\r\nonly one consumer is available**.\r\n\r\n## How to test\r\n\r\n1. Run Kibana security serverless and confirm the rules in stack\r\nmanagement do not have the role visibility dropdown.\r\n2. Please also make sure that the drop-down still shows when\r\nneeded(outside of serverless).","sha":"7498ab00618baf5d5d30d32b989d4ba93da2803e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Feature:Alerting","release_note:skip","Team:ResponseOps","v9.0.0","backport:prev-minor","v8.17.0","v8.18.0","v8.16.2"],"number":200727,"url":"https://github.com/elastic/kibana/pull/200727","mergeCommit":{"message":"[ResponseOps][Rules] Hide the \"Role visibility\" dropdown in the new rule form in serverless (#200727)\n\nFixes #199642\r\n\r\n## Summary\r\n\r\n~~This PR hides the role visibility dropdown in the new rule form when\r\nin serverless.~~\r\n\r\nThis PR hides the role visibility dropdown in the new rule form **when\r\nonly one consumer is available**.\r\n\r\n## How to test\r\n\r\n1. Run Kibana security serverless and confirm the rules in stack\r\nmanagement do not have the role visibility dropdown.\r\n2. Please also make sure that the drop-down still shows when\r\nneeded(outside of serverless).","sha":"7498ab00618baf5d5d30d32b989d4ba93da2803e"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200727","number":200727,"mergeCommit":{"message":"[ResponseOps][Rules] Hide the \"Role visibility\" dropdown in the new rule form in serverless (#200727)\n\nFixes #199642\r\n\r\n## Summary\r\n\r\n~~This PR hides the role visibility dropdown in the new rule form when\r\nin serverless.~~\r\n\r\nThis PR hides the role visibility dropdown in the new rule form **when\r\nonly one consumer is available**.\r\n\r\n## How to test\r\n\r\n1. Run Kibana security serverless and confirm the rules in stack\r\nmanagement do not have the role visibility dropdown.\r\n2. Please also make sure that the drop-down still shows when\r\nneeded(outside of serverless).","sha":"7498ab00618baf5d5d30d32b989d4ba93da2803e"}},{"branch":"8.17","label":"v8.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/203077","number":203077,"state":"MERGED","mergeCommit":{"sha":"43f0dfaa131a1d7eed12b59ba0b9afc1a87633e9","message":"[8.x] [ResponseOps][Rules] Hide the "Role visibility" dropdown in the new rule form in serverless (#200727) (#203077)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[ResponseOps][Rules] Hide the "Role visibility" dropdown in\nthe new rule form in serverless\n(#200727)](https://github.com/elastic/kibana/pull/200727)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT\n[{\"author\":{\"name\":\"Antonio\",\"email\":\"antonio.coelho@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-12-05T11:20:37Z\",\"message\":\"[ResponseOps][Rules]\nHide the \\\"Role visibility\\\" dropdown in the new rule form in serverless\n(#200727)\\n\\nFixes #199642\\r\\n\\r\\n## Summary\\r\\n\\r\\n~~This PR hides the\nrole visibility dropdown in the new rule form when\\r\\nin\nserverless.~~\\r\\n\\r\\nThis PR hides the role visibility dropdown in the\nnew rule form **when\\r\\nonly one consumer is available**.\\r\\n\\r\\n## How\nto test\\r\\n\\r\\n1. Run Kibana security serverless and confirm the rules\nin stack\\r\\nmanagement do not have the role visibility dropdown.\\r\\n2.\nPlease also make sure that the drop-down still shows\nwhen\\r\\nneeded(outside of\nserverless).\",\"sha\":\"7498ab00618baf5d5d30d32b989d4ba93da2803e\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"Feature:Alerting\",\"release_note:skip\",\"Team:ResponseOps\",\"v9.0.0\",\"backport:prev-minor\",\"v8.17.0\",\"v8.18.0\",\"v8.16.2\"],\"title\":\"[ResponseOps][Rules]\nHide the \\\"Role visibility\\\" dropdown in the new rule form in\nserverless\",\"number\":200727,\"url\":\"https://github.com/elastic/kibana/pull/200727\",\"mergeCommit\":{\"message\":\"[ResponseOps][Rules]\nHide the \\\"Role visibility\\\" dropdown in the new rule form in serverless\n(#200727)\\n\\nFixes #199642\\r\\n\\r\\n## Summary\\r\\n\\r\\n~~This PR hides the\nrole visibility dropdown in the new rule form when\\r\\nin\nserverless.~~\\r\\n\\r\\nThis PR hides the role visibility dropdown in the\nnew rule form **when\\r\\nonly one consumer is available**.\\r\\n\\r\\n## How\nto test\\r\\n\\r\\n1. Run Kibana security serverless and confirm the rules\nin stack\\r\\nmanagement do not have the role visibility dropdown.\\r\\n2.\nPlease also make sure that the drop-down still shows\nwhen\\r\\nneeded(outside of\nserverless).\",\"sha\":\"7498ab00618baf5d5d30d32b989d4ba93da2803e\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.17\",\"8.x\",\"8.16\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/200727\",\"number\":200727,\"mergeCommit\":{\"message\":\"[ResponseOps][Rules]\nHide the \\\"Role visibility\\\" dropdown in the new rule form in serverless\n(#200727)\\n\\nFixes #199642\\r\\n\\r\\n## Summary\\r\\n\\r\\n~~This PR hides the\nrole visibility dropdown in the new rule form when\\r\\nin\nserverless.~~\\r\\n\\r\\nThis PR hides the role visibility dropdown in the\nnew rule form **when\\r\\nonly one consumer is available**.\\r\\n\\r\\n## How\nto test\\r\\n\\r\\n1. Run Kibana security serverless and confirm the rules\nin stack\\r\\nmanagement do not have the role visibility dropdown.\\r\\n2.\nPlease also make sure that the drop-down still shows\nwhen\\r\\nneeded(outside of\nserverless).\",\"sha\":\"7498ab00618baf5d5d30d32b989d4ba93da2803e\"}},{\"branch\":\"8.17\",\"label\":\"v8.17.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.x\",\"label\":\"v8.18.0\",\"branchLabelMappingKey\":\"^v8.18.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.2\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Antonio <antonio.coelho@elastic.co>"}},{"branch":"8.16","label":"v8.16.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
…01804) (#202924) # Backport This will backport the following commits from `main` to `8.16`: - [[Infra] Exclude frozen/cold data tiers from source queries (#201804)](#201804) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gonçalo Rica Pais da Silva","email":"goncalo.rica@elastic.co"},"sourceCommit":{"committedDate":"2024-12-03T18:23:13Z","message":"[Infra] Exclude frozen/cold data tiers from source queries (#201804)\n\nCloses #201568 \r\n\r\n## Summary\r\n\r\nAdds the exclude data tiers settings to the\r\n`/api/metrics/source/hasData` and `/api/metrics/source/{sourceId}`\r\nrequests. Also applies it to the `getIndexStatus` API call.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ac3b60ee907436aeee35fc59df7c30bcb9d66bc8","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","Team:obs-ux-management","v8.16.0"],"number":201804,"url":"https://github.com/elastic/kibana/pull/201804","mergeCommit":{"message":"[Infra] Exclude frozen/cold data tiers from source queries (#201804)\n\nCloses #201568 \r\n\r\n## Summary\r\n\r\nAdds the exclude data tiers settings to the\r\n`/api/metrics/source/hasData` and `/api/metrics/source/{sourceId}`\r\nrequests. Also applies it to the `getIndexStatus` API call.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ac3b60ee907436aeee35fc59df7c30bcb9d66bc8"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201804","number":201804,"mergeCommit":{"message":"[Infra] Exclude frozen/cold data tiers from source queries (#201804)\n\nCloses #201568 \r\n\r\n## Summary\r\n\r\nAdds the exclude data tiers settings to the\r\n`/api/metrics/source/hasData` and `/api/metrics/source/{sourceId}`\r\nrequests. Also applies it to the `getIndexStatus` API call.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ac3b60ee907436aeee35fc59df7c30bcb9d66bc8"}},{"branch":"8.16","label":"v8.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"url":"https://github.com/elastic/kibana/pull/202788","number":202788,"branch":"8.17","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/202789","number":202789,"branch":"8.x","state":"OPEN"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co>
# Backport This will backport the following commits from `main` to `8.16`: - [Upgrade axios 1.7.4 → 1.7.9 (#202774)](#202774) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jeramy Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2024-12-04T22:13:35Z","message":"Upgrade axios 1.7.4 → 1.7.9 (#202774)\n\n## Summary\r\n\r\nUpgrades `axios` from v1.7.4 to v1.7.9.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"52e021ff7fa289fcba42e090aa12e9de1f868ee0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Security","release_note:skip","v9.0.0","backport:all-open","v8.18.0"],"number":202774,"url":"https://github.com/elastic/kibana/pull/202774","mergeCommit":{"message":"Upgrade axios 1.7.4 → 1.7.9 (#202774)\n\n## Summary\r\n\r\nUpgrades `axios` from v1.7.4 to v1.7.9.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"52e021ff7fa289fcba42e090aa12e9de1f868ee0"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202774","number":202774,"mergeCommit":{"message":"Upgrade axios 1.7.4 → 1.7.9 (#202774)\n\n## Summary\r\n\r\nUpgrades `axios` from v1.7.4 to v1.7.9.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"52e021ff7fa289fcba42e090aa12e9de1f868ee0"}},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
…203174) # Backport This will backport the following commits from `main` to `8.16`: - [[Automatic Import] Restrict unsupported log formats (#202994)](#202994) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-05T19:18:08Z","message":"[Automatic Import] Restrict unsupported log formats (#202994)","sha":"178baa8468b3252bbebb6074baf0e59c9916d1a3","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport"],"title":"[Automatic Import] Restrict unsupported log formats","number":202994,"url":"https://github.com/elastic/kibana/pull/202994","mergeCommit":{"message":"[Automatic Import] Restrict unsupported log formats (#202994)","sha":"178baa8468b3252bbebb6074baf0e59c9916d1a3"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202994","number":202994,"mergeCommit":{"message":"[Automatic Import] Restrict unsupported log formats (#202994)","sha":"178baa8468b3252bbebb6074baf0e59c9916d1a3"}}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com>
…03217) # Backport This will backport the following commits from `main` to `8.16`: - [[Search][a11y] Fix table row screen reader error (#203136)](#203136) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Navarone Feekery","email":"13634519+navarone-feekery@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-06T09:10:26Z","message":"[Search][a11y] Fix table row screen reader error (#203136)\n\n## Closes https://github.com/elastic/kibana/issues/199113\r\n\r\nAllows errors in the table row to be read by screen readers.","sha":"1a9893bd6f7fd3fb94b08459e05921a00d86b8c5","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:prev-major"],"title":"[Search][a11y] Fix table row screen reader error","number":203136,"url":"https://github.com/elastic/kibana/pull/203136","mergeCommit":{"message":"[Search][a11y] Fix table row screen reader error (#203136)\n\n## Closes https://github.com/elastic/kibana/issues/199113\r\n\r\nAllows errors in the table row to be read by screen readers.","sha":"1a9893bd6f7fd3fb94b08459e05921a00d86b8c5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203136","number":203136,"mergeCommit":{"message":"[Search][a11y] Fix table row screen reader error (#203136)\n\n## Closes https://github.com/elastic/kibana/issues/199113\r\n\r\nAllows errors in the table row to be read by screen readers.","sha":"1a9893bd6f7fd3fb94b08459e05921a00d86b8c5"}}]}] BACKPORT--> Co-authored-by: Navarone Feekery <13634519+navarone-feekery@users.noreply.github.com>
…ces in Firehose flow (#201613) (#202892) # Backport This will backport the following commits from `main` to `8.16`: - [[Observability Onboarding] Prevent showing duplcated AWS services in Firehose flow (#201613)](#201613) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2024-12-04T10:49:47Z","message":"[Observability Onboarding] Prevent showing duplcated AWS services in Firehose flow (#201613)\n\nCloses #200931 \r\n\r\nSwitched to using AWS service list as a base to showing the detected\r\nservices in the UI instead of the list of populated indices as multiple\r\nindices can be related to a single service.\r\n\r\n### How to test\r\n\r\n1. Go to Firehose flow `/observabilityOnboarding/firehose`\r\n2. Open Kibana dev tools in another tab\r\n3. Ingest documents related into multiple data streams which related to\r\na single AWS service:\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```\r\n4. Make sure you see only one entry for the service appear in the\r\nFirehose flow","sha":"a2fb9b736cd8007a0ba04b9b1051d7988c690b5b","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","ci:project-deploy-observability"],"title":"[Observability Onboarding] Prevent showing duplcated AWS services in Firehose flow","number":201613,"url":"https://github.com/elastic/kibana/pull/201613","mergeCommit":{"message":"[Observability Onboarding] Prevent showing duplcated AWS services in Firehose flow (#201613)\n\nCloses #200931 \r\n\r\nSwitched to using AWS service list as a base to showing the detected\r\nservices in the UI instead of the list of populated indices as multiple\r\nindices can be related to a single service.\r\n\r\n### How to test\r\n\r\n1. Go to Firehose flow `/observabilityOnboarding/firehose`\r\n2. Open Kibana dev tools in another tab\r\n3. Ingest documents related into multiple data streams which related to\r\na single AWS service:\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```\r\n4. Make sure you see only one entry for the service appear in the\r\nFirehose flow","sha":"a2fb9b736cd8007a0ba04b9b1051d7988c690b5b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201613","number":201613,"mergeCommit":{"message":"[Observability Onboarding] Prevent showing duplcated AWS services in Firehose flow (#201613)\n\nCloses #200931 \r\n\r\nSwitched to using AWS service list as a base to showing the detected\r\nservices in the UI instead of the list of populated indices as multiple\r\nindices can be related to a single service.\r\n\r\n### How to test\r\n\r\n1. Go to Firehose flow `/observabilityOnboarding/firehose`\r\n2. Open Kibana dev tools in another tab\r\n3. Ingest documents related into multiple data streams which related to\r\na single AWS service:\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```\r\n4. Make sure you see only one entry for the service appear in the\r\nFirehose flow","sha":"a2fb9b736cd8007a0ba04b9b1051d7988c690b5b"}}]}] BACKPORT--> Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com>
# Backport This will backport the following commits from `main` to `8.16`: - [Upgrade webpack 5.91.0 → 5.96.1 (#202534)](#202534) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jeramy Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2024-12-04T20:28:12Z","message":"Upgrade webpack 5.91.0 → 5.96.1 (#202534)\n\n## Summary\r\n\r\nUpgrades references to webpack5 from v5.91.0 to v5.96.1\r\n\r\nA v4 to v5 upgrade is being explored here:\r\nhttps://github.com//pull/191106\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f8860e91cf5e6cc061b0f37e618ca58cfef88028","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","v9.0.0","backport:all-open","v8.18.0"],"number":202534,"url":"https://github.com/elastic/kibana/pull/202534","mergeCommit":{"message":"Upgrade webpack 5.91.0 → 5.96.1 (#202534)\n\n## Summary\r\n\r\nUpgrades references to webpack5 from v5.91.0 to v5.96.1\r\n\r\nA v4 to v5 upgrade is being explored here:\r\nhttps://github.com//pull/191106\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f8860e91cf5e6cc061b0f37e618ca58cfef88028"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202534","number":202534,"mergeCommit":{"message":"Upgrade webpack 5.91.0 → 5.96.1 (#202534)\n\n## Summary\r\n\r\nUpgrades references to webpack5 from v5.91.0 to v5.96.1\r\n\r\nA v4 to v5 upgrade is being explored here:\r\nhttps://github.com//pull/191106\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f8860e91cf5e6cc061b0f37e618ca58cfef88028"}},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/203016","number":203016,"state":"MERGED","mergeCommit":{"sha":"90cf032400a86f7d216fc7b202bb6c3b4f05645c","message":"[8.x] Upgrade webpack 5.91.0 → 5.96.1 (#202534) (#203016)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [Upgrade webpack 5.91.0 → 5.96.1\n(#202534)](https://github.com/elastic/kibana/pull/202534)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Jeramy\nSoucy\",\"email\":\"jeramy.soucy@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-12-04T20:28:12Z\",\"message\":\"Upgrade\nwebpack 5.91.0 → 5.96.1 (#202534)\\n\\n## Summary\\r\\n\\r\\nUpgrades\nreferences to webpack5 from v5.91.0 to v5.96.1\\r\\n\\r\\nA v4 to v5 upgrade\nis being explored\nhere:\\r\\nhttps://github.com//pull/191106\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nkibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"f8860e91cf5e6cc061b0f37e618ca58cfef88028\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"Team:Security\",\"release_note:skip\",\"v9.0.0\",\"backport:all-open\",\"v8.18.0\"],\"title\":\"Upgrade\nwebpack 5.91.0 →\n5.96.1\",\"number\":202534,\"url\":\"https://github.com/elastic/kibana/pull/202534\",\"mergeCommit\":{\"message\":\"Upgrade\nwebpack 5.91.0 → 5.96.1 (#202534)\\n\\n## Summary\\r\\n\\r\\nUpgrades\nreferences to webpack5 from v5.91.0 to v5.96.1\\r\\n\\r\\nA v4 to v5 upgrade\nis being explored\nhere:\\r\\nhttps://github.com//pull/191106\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nkibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"f8860e91cf5e6cc061b0f37e618ca58cfef88028\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.x\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/202534\",\"number\":202534,\"mergeCommit\":{\"message\":\"Upgrade\nwebpack 5.91.0 → 5.96.1 (#202534)\\n\\n## Summary\\r\\n\\r\\nUpgrades\nreferences to webpack5 from v5.91.0 to v5.96.1\\r\\n\\r\\nA v4 to v5 upgrade\nis being explored\nhere:\\r\\nhttps://github.com//pull/191106\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nkibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"f8860e91cf5e6cc061b0f37e618ca58cfef88028\"}},{\"branch\":\"8.x\",\"label\":\"v8.18.0\",\"branchLabelMappingKey\":\"^v8.18.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
…iguration (#203374) (#203393) # Backport This will backport the following commits from `main` to `8.16`: - [[Search][Connectors] Disable setup options after creating configuration (#203374)](#203374) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"José Luis González","email":"joseluisgj@gmail.com"},"sourceCommit":{"committedDate":"2024-12-09T11:15:54Z","message":"[Search][Connectors] Disable setup options after creating configuration (#203374)\n\n## Summary\r\n\r\nThis PR disables the _Elastic managed_ and _Self-managed_ setup options\r\nafter clicking the _Generate configuration_ button in order to avoid the\r\nerror described in this ticket\r\nhttps://github.com/elastic/search-team/issues/8665 when changing\r\ndeployment method after generating the config.\r\n\r\n","sha":"9b6af1c1887f83d821d6fc639715ad4be593fea7","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:version","v8.17.0","v8.18.0","v8.16.2","v8.16.3"],"title":"[Search][Connectors] Disable setup options after creating configuration","number":203374,"url":"https://github.com/elastic/kibana/pull/203374","mergeCommit":{"message":"[Search][Connectors] Disable setup options after creating configuration (#203374)\n\n## Summary\r\n\r\nThis PR disables the _Elastic managed_ and _Self-managed_ setup options\r\nafter clicking the _Generate configuration_ button in order to avoid the\r\nerror described in this ticket\r\nhttps://github.com/elastic/search-team/issues/8665 when changing\r\ndeployment method after generating the config.\r\n\r\n","sha":"9b6af1c1887f83d821d6fc639715ad4be593fea7"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203374","number":203374,"mergeCommit":{"message":"[Search][Connectors] Disable setup options after creating configuration (#203374)\n\n## Summary\r\n\r\nThis PR disables the _Elastic managed_ and _Self-managed_ setup options\r\nafter clicking the _Generate configuration_ button in order to avoid the\r\nerror described in this ticket\r\nhttps://github.com/elastic/search-team/issues/8665 when changing\r\ndeployment method after generating the config.\r\n\r\n","sha":"9b6af1c1887f83d821d6fc639715ad4be593fea7"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: José Luis González <joseluisgj@gmail.com>
… is invalid (#203096) (#203467) # Backport This will backport the following commits from `main` to `8.16`: - [[OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is invalid (#203096)](#203096) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Faisal Kanout","email":"faisal.kanout@elastic.co"},"sourceCommit":{"committedDate":"2024-12-05T16:07:58Z","message":"[OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is invalid (#203096)\n\n## Summary\r\n\r\nIt fixes #199273 by validating\r\nthe query before passing it to the preview chart","sha":"f1109cfccedfd386263a00207df81c766cfaf6e4","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","backport:prev-minor","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-infra_services","Team:obs-ux-management","v8.18.0"],"title":"[OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is invalid","number":203096,"url":"https://github.com/elastic/kibana/pull/203096","mergeCommit":{"message":"[OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is invalid (#203096)\n\n## Summary\r\n\r\nIt fixes #199273 by validating\r\nthe query before passing it to the preview chart","sha":"f1109cfccedfd386263a00207df81c766cfaf6e4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203096","number":203096,"mergeCommit":{"message":"[OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is invalid (#203096)\n\n## Summary\r\n\r\nIt fixes #199273 by validating\r\nthe query before passing it to the preview chart","sha":"f1109cfccedfd386263a00207df81c766cfaf6e4"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/203134","number":203134,"state":"MERGED","mergeCommit":{"sha":"a70bdf01cd8208c0f2358a98f5fcc5d10ac0a7d6","message":"[8.x] [OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is invalid (#203096) (#203134)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is\ninvalid (#203096)](https://github.com/elastic/kibana/pull/203096)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Faisal\nKanout\",\"email\":\"faisal.kanout@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-12-05T16:07:58Z\",\"message\":\"[OBX-UX-MGMT][ALERTING]\nFix APM rule error msg when KQL filter is invalid (#203096)\\n\\n##\nSummary\\r\\n\\r\\nIt fixes https://github.com/elastic/kibana/issues/199273\nby validating\\r\\nthe query before passing it to the preview\nchart\",\"sha\":\"f1109cfccedfd386263a00207df81c766cfaf6e4\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:fix\",\"v9.0.0\",\"backport:prev-minor\",\"ci:project-deploy-observability\",\"Team:obs-ux-infra_services\",\"Team:obs-ux-management\"],\"title\":\"[OBX-UX-MGMT][ALERTING]\nFix APM rule error msg when KQL filter is\ninvalid\",\"number\":203096,\"url\":\"https://github.com/elastic/kibana/pull/203096\",\"mergeCommit\":{\"message\":\"[OBX-UX-MGMT][ALERTING]\nFix APM rule error msg when KQL filter is invalid (#203096)\\n\\n##\nSummary\\r\\n\\r\\nIt fixes https://github.com/elastic/kibana/issues/199273\nby validating\\r\\nthe query before passing it to the preview\nchart\",\"sha\":\"f1109cfccedfd386263a00207df81c766cfaf6e4\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/203096\",\"number\":203096,\"mergeCommit\":{\"message\":\"[OBX-UX-MGMT][ALERTING]\nFix APM rule error msg when KQL filter is invalid (#203096)\\n\\n##\nSummary\\r\\n\\r\\nIt fixes https://github.com/elastic/kibana/issues/199273\nby validating\\r\\nthe query before passing it to the preview\nchart\",\"sha\":\"f1109cfccedfd386263a00207df81c766cfaf6e4\"}}]}] BACKPORT-->\n\nCo-authored-by: Faisal Kanout <faisal.kanout@elastic.co>"}}]}] BACKPORT--> Co-authored-by: Faisal Kanout <faisal.kanout@elastic.co>
…eck for scan test (#210748) (#210785) # Backport This will backport the following commits from `main` to `8.16`: - [[SecuritySolution][Endpoint] Remove hardcoded agent version check for scan test (#210748)](#210748) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ash","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T11:19:11Z","message":"[SecuritySolution][Endpoint] Remove hardcoded agent version check for scan test (#210748)\n\n## Summary\n\n> [!NOTE]\n> This PR is NOT unskipping the test to minimize conflicts during\nbackports.\n> Manual backports maybe needed as some auto backports may fail as\n`security_solution` folder has moved between `8.16` and `8.17`\n\nRemoves hardcoded agent version for test setup that was added before\n8.15 GA.\n\nrefs\nhttps://github.com//pull/189174#discussion_r1700257185\ncloses https://github.com/elastic/kibana/issues/210364\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"60918882ead47a8b94bff7716e79bdd6083a98a7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","OLM Sprint","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[SecuritySolution][Endpoint] Remove hardcoded agent version check for scan test","number":210748,"url":"https://github.com/elastic/kibana/pull/210748","mergeCommit":{"message":"[SecuritySolution][Endpoint] Remove hardcoded agent version check for scan test (#210748)\n\n## Summary\n\n> [!NOTE]\n> This PR is NOT unskipping the test to minimize conflicts during\nbackports.\n> Manual backports maybe needed as some auto backports may fail as\n`security_solution` folder has moved between `8.16` and `8.17`\n\nRemoves hardcoded agent version for test setup that was added before\n8.15 GA.\n\nrefs\nhttps://github.com//pull/189174#discussion_r1700257185\ncloses https://github.com/elastic/kibana/issues/210364\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"60918882ead47a8b94bff7716e79bdd6083a98a7"}},"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/210748","number":210748,"mergeCommit":{"message":"[SecuritySolution][Endpoint] Remove hardcoded agent version check for scan test (#210748)\n\n## Summary\n\n> [!NOTE]\n> This PR is NOT unskipping the test to minimize conflicts during\nbackports.\n> Manual backports maybe needed as some auto backports may fail as\n`security_solution` folder has moved between `8.16` and `8.17`\n\nRemoves hardcoded agent version for test setup that was added before\n8.15 GA.\n\nrefs\nhttps://github.com//pull/189174#discussion_r1700257185\ncloses https://github.com/elastic/kibana/issues/210364\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"60918882ead47a8b94bff7716e79bdd6083a98a7"}}]}] BACKPORT--> Co-authored-by: Ash <1849116+ashokaditya@users.noreply.github.com>
…ng error (#209973) (#210768) # Backport This will backport the following commits from `main` to `8.16`: - [[Response Ops][Cases] Cases with empty string assignees throwing error (#209973)](#209973) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julian Gernun","email":"17549662+jcger@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T06:06:44Z","message":"[Response Ops][Cases] Cases with empty string assignees throwing error (#209973)\n\n## Summary\nCloses https://github.com/elastic/kibana/issues/209950\n\nTesting steps in referenced issue\n\n## Release note\nFix error message in cases list if case assignee is an empty string","sha":"0897d0878622db9d9747e2bc1292d647c09ad996","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:ResponseOps","v9.0.0","Feature:Cases","backport:prev-major","v8.18.0","v8.16.4","v8.17.2","v9.1.0","v8.19.0"],"title":"[Response Ops][Cases] Cases with empty string assignees throwing error","number":209973,"url":"https://github.com/elastic/kibana/pull/209973","mergeCommit":{"message":"[Response Ops][Cases] Cases with empty string assignees throwing error (#209973)\n\n## Summary\nCloses https://github.com/elastic/kibana/issues/209950\n\nTesting steps in referenced issue\n\n## Release note\nFix error message in cases list if case assignee is an empty string","sha":"0897d0878622db9d9747e2bc1292d647c09ad996"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210733","number":210733,"state":"MERGED","mergeCommit":{"sha":"ee04349a417e47004062aeb796092f6813122192","message":"[9.0] [Response Ops][Cases] Cases with empty string assignees throwing error (#209973) (#210733)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Response Ops][Cases] Cases with empty string assignees throwing\nerror (#209973)](https://github.com/elastic/kibana/pull/209973)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Julian\nGernun\",\"email\":\"17549662+jcger@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-12T06:06:44Z\",\"message\":\"[Response\nOps][Cases] Cases with empty string assignees throwing error\n(#209973)\\n\\n## Summary\\nCloses\nhttps://github.com//issues/209950\\n\\nTesting steps in\nreferenced issue\\n\\n## Release note\\nFix error message in cases list if\ncase assignee is an empty\nstring\",\"sha\":\"0897d0878622db9d9747e2bc1292d647c09ad996\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:fix\",\"Team:ResponseOps\",\"v9.0.0\",\"Feature:Cases\",\"backport:prev-major\",\"v8.18.0\",\"v8.16.4\",\"v8.17.2\",\"v9.1.0\"],\"title\":\"[Response\nOps][Cases] Cases with empty string assignees throwing\nerror\",\"number\":209973,\"url\":\"https://github.com/elastic/kibana/pull/209973\",\"mergeCommit\":{\"message\":\"[Response\nOps][Cases] Cases with empty string assignees throwing error\n(#209973)\\n\\n## Summary\\nCloses\nhttps://github.com//issues/209950\\n\\nTesting steps in\nreferenced issue\\n\\n## Release note\\nFix error message in cases list if\ncase assignee is an empty\nstring\",\"sha\":\"0897d0878622db9d9747e2bc1292d647c09ad996\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\",\"8.18\",\"8.16\",\"8.17\"],\"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\":\"8.16\",\"label\":\"v8.16.4\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.17\",\"label\":\"v8.17.2\",\"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/209973\",\"number\":209973,\"mergeCommit\":{\"message\":\"[Response\nOps][Cases] Cases with empty string assignees throwing error\n(#209973)\\n\\n## Summary\\nCloses\nhttps://github.com//issues/209950\\n\\nTesting steps in\nreferenced issue\\n\\n## Release note\\nFix error message in cases list if\ncase assignee is an empty\nstring\",\"sha\":\"0897d0878622db9d9747e2bc1292d647c09ad996\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210731","number":210731,"state":"OPEN"},{"branch":"8.16","label":"v8.16.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210755","number":210755,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209973","number":209973,"mergeCommit":{"message":"[Response Ops][Cases] Cases with empty string assignees throwing error (#209973)\n\n## Summary\nCloses https://github.com/elastic/kibana/issues/209950\n\nTesting steps in referenced issue\n\n## Release note\nFix error message in cases list if case assignee is an empty string","sha":"0897d0878622db9d9747e2bc1292d647c09ad996"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210732","number":210732,"state":"MERGED","mergeCommit":{"sha":"8b98614e9dbdaaeaebac56d633cd2b7c35af01bd","message":"[8.x] [Response Ops][Cases] Cases with empty string assignees throwing error (#209973) (#210732)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Response Ops][Cases] Cases with empty string assignees throwing\nerror (#209973)](https://github.com/elastic/kibana/pull/209973)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Julian\nGernun\",\"email\":\"17549662+jcger@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-12T06:06:44Z\",\"message\":\"[Response\nOps][Cases] Cases with empty string assignees throwing error\n(#209973)\\n\\n## Summary\\nCloses\nhttps://github.com//issues/209950\\n\\nTesting steps in\nreferenced issue\\n\\n## Release note\\nFix error message in cases list if\ncase assignee is an empty\nstring\",\"sha\":\"0897d0878622db9d9747e2bc1292d647c09ad996\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:fix\",\"Team:ResponseOps\",\"v9.0.0\",\"Feature:Cases\",\"backport:prev-major\",\"v8.18.0\",\"v8.16.4\",\"v8.17.2\",\"v9.1.0\"],\"title\":\"[Response\nOps][Cases] Cases with empty string assignees throwing\nerror\",\"number\":209973,\"url\":\"https://github.com/elastic/kibana/pull/209973\",\"mergeCommit\":{\"message\":\"[Response\nOps][Cases] Cases with empty string assignees throwing error\n(#209973)\\n\\n## Summary\\nCloses\nhttps://github.com//issues/209950\\n\\nTesting steps in\nreferenced issue\\n\\n## Release note\\nFix error message in cases list if\ncase assignee is an empty\nstring\",\"sha\":\"0897d0878622db9d9747e2bc1292d647c09ad996\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\",\"8.18\",\"8.16\",\"8.17\"],\"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\":\"8.16\",\"label\":\"v8.16.4\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.17\",\"label\":\"v8.17.2\",\"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/209973\",\"number\":209973,\"mergeCommit\":{\"message\":\"[Response\nOps][Cases] Cases with empty string assignees throwing error\n(#209973)\\n\\n## Summary\\nCloses\nhttps://github.com//issues/209950\\n\\nTesting steps in\nreferenced issue\\n\\n## Release note\\nFix error message in cases list if\ncase assignee is an empty\nstring\",\"sha\":\"0897d0878622db9d9747e2bc1292d647c09ad996\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com>"}}]}] BACKPORT-->
…209110) (#210879) # Backport This will backport the following commits from `main` to `8.16`: - [[Lens] Restore dynamic colouring by value for Last value agg (#209110)](#209110) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-11T14:55:35Z","message":"[Lens] Restore dynamic colouring by value for Last value agg (#209110)\n\n## Summary\n\nFixes #208924\n\nThis PR improves the numeric check for the Last value agg within the\nMetric chart type avoiding completely to access the active data and\nrather rely on the datasource configuration.\nThe new utility function in fact won't rely any more on active data\nrather on the Lens configuration itself, which is more robust, faster\nand flexible.\n\n<img width=\"2552\" alt=\"Screenshot 2025-01-31 at 14 30 12\"\nsrc=\"https://github.com/user-attachments/assets/5f8792db-40ff-497b-8e2f-0737c2932f92\"\n/>\n\n\n### Notes for testing\n\nI've created a testing dashboard with all the possible combinations of\ncolouring for metric and tables.\n\n\n[last_value_dashboard.ndjson.txt](https://github.com/user-attachments/files/18618905/last_value_dashboard.ndjson.txt)\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\n\n## Release note\n\nThis fixes an issue where dynamic colouring has been disabled from Last\nvalue aggregation types.","sha":"abba6675e29b28b91daea1f46d2ff48363ab78ab","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","Feature:Lens","backport missing","backport:prev-major","v9.1.0"],"title":"[Lens] Restore dynamic colouring by value for Last value agg","number":209110,"url":"https://github.com/elastic/kibana/pull/209110","mergeCommit":{"message":"[Lens] Restore dynamic colouring by value for Last value agg (#209110)\n\n## Summary\n\nFixes #208924\n\nThis PR improves the numeric check for the Last value agg within the\nMetric chart type avoiding completely to access the active data and\nrather rely on the datasource configuration.\nThe new utility function in fact won't rely any more on active data\nrather on the Lens configuration itself, which is more robust, faster\nand flexible.\n\n<img width=\"2552\" alt=\"Screenshot 2025-01-31 at 14 30 12\"\nsrc=\"https://github.com/user-attachments/assets/5f8792db-40ff-497b-8e2f-0737c2932f92\"\n/>\n\n\n### Notes for testing\n\nI've created a testing dashboard with all the possible combinations of\ncolouring for metric and tables.\n\n\n[last_value_dashboard.ndjson.txt](https://github.com/user-attachments/files/18618905/last_value_dashboard.ndjson.txt)\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\n\n## Release note\n\nThis fixes an issue where dynamic colouring has been disabled from Last\nvalue aggregation types.","sha":"abba6675e29b28b91daea1f46d2ff48363ab78ab"}},"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/209110","number":209110,"mergeCommit":{"message":"[Lens] Restore dynamic colouring by value for Last value agg (#209110)\n\n## Summary\n\nFixes #208924\n\nThis PR improves the numeric check for the Last value agg within the\nMetric chart type avoiding completely to access the active data and\nrather rely on the datasource configuration.\nThe new utility function in fact won't rely any more on active data\nrather on the Lens configuration itself, which is more robust, faster\nand flexible.\n\n<img width=\"2552\" alt=\"Screenshot 2025-01-31 at 14 30 12\"\nsrc=\"https://github.com/user-attachments/assets/5f8792db-40ff-497b-8e2f-0737c2932f92\"\n/>\n\n\n### Notes for testing\n\nI've created a testing dashboard with all the possible combinations of\ncolouring for metric and tables.\n\n\n[last_value_dashboard.ndjson.txt](https://github.com/user-attachments/files/18618905/last_value_dashboard.ndjson.txt)\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\n\n## Release note\n\nThis fixes an issue where dynamic colouring has been disabled from Last\nvalue aggregation types.","sha":"abba6675e29b28b91daea1f46d2ff48363ab78ab"}}]}] BACKPORT--> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>
# Backport This will backport the following commits from `main` to `8.16`: - [Update dependency polished to v4 (main) (#206220)](#206220) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T17:33:46Z","message":"Update dependency polished to v4 (main) (#206220)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [polished](https://polished.js.org)\n([source](https://togithub.com/styled-components/polished)) |\ndependencies | major | [`^3.7.2` ->\n`^4.3.1`](https://renovatebot.com/diffs/npm/polished/3.7.2/4.3.1) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>styled-components/polished (polished)</summary>\n\n###\n[`v4.3.1`](https://togithub.com/styled-components/polished/releases/tag/v4.3.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.3.0...v4.3.1)\n\n### Bug Fixes & Improvements\n\n- Remove annotate-pure-calls plugin to address incompatibility with\nlater versions of rollup.\n- Update dependencies.\n\n###\n[`v4.3.0`](https://togithub.com/styled-components/polished/compare/v4.2.2...v4.3.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.2...v4.3.0)\n\n###\n[`v4.2.2`](https://togithub.com/styled-components/polished/releases/tag/v4.2.2)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.1...v4.2.2)\n\n### Bug Fixes\n\n- **Color Modules** - addresses an issue with longer floats in color\nvalues.\n([#​610](https://togithub.com/styled-components/polished/issues/610)\n- Thanks to [@​levymetal](https://togithub.com/levymetal))\n\n###\n[`v4.2.1`](https://togithub.com/styled-components/polished/releases/tag/v4.2.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.0...v4.2.1)\n\n### Bug Fixes\n\n- **`hls(a)`** - now properly parses percentages for opacity.\n- **`rgb(a)`** - now properly parses percentages for opacity.\n\n###\n[`v4.2.0`](https://togithub.com/styled-components/polished/releases/tag/v4.2.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.4...v4.2.0)\n\n### Improvements\n\n- **color Modules** - now support space-separated CSS color values for\nrgb(a) and hsl(a).\n([#​605](https://togithub.com/styled-components/polished/issues/605))\n- **`rgb`** - now accepts optional opacity value.\n- **`hsl`** - now accepts optional opacity value.\n\n###\n[`v4.1.4`](https://togithub.com/styled-components/polished/releases/tag/v4.1.4)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.3...v4.1.4)\n\n### Bug Fixes\n\n- **mix** - remove unnecessary division by 1\n([#​59](https://togithub.com/styled-components/polished/issues/59))\n\n###\n[`v4.1.3`](https://togithub.com/styled-components/polished/releases/tag/v4.1.3)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.2...v4.1.3)\n\n### Bug Fixes\n\n- Addressed several performance issues with regexes.\n\n###\n[`v4.1.2`](https://togithub.com/styled-components/polished/releases/tag/v4.1.2)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.1...v4.1.2)\n\n### Bug Fixes\n\n- **fluidRange** - updated return value to use an array to address\nunclear object property typing error in flow.\n\n###\n[`v4.1.1`](https://togithub.com/styled-components/polished/releases/tag/v4.1.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.0...v4.1.1)\n\n### Bug Fixes\n\n- **scarf** - removed scarf analytics package due to yarn\nincompatibilities and concerns over GDPR compliance.\n\n###\n[`v4.1.0`](https://togithub.com/styled-components/polished/releases/tag/v4.1.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.5...v4.1.0)\n\n### Introducing polished.js v4.1.0!\n\nWe're super stoked to announce that polished.js v4.1.0 is officially\nout! It is available via your package manager of choice. This will be\nthe final non-patch release before v5.\n\n`npm install polished`\n`yarn add polished`\n\n#### Release Highlights\n\n##### New Module\n\n- **`remToPx`**: We've introduced a new module to handle converting to\n`rem` values to `px` values.\n([#​376](https://togithub.com/styled-components/polished/issues/376))\n\n##### Analytics\n\n- We are now leveraging [Scarf](https://scarf.sh) to track package\nanalytics. You can opt-out of this functionality by following [these\ninstructions](https://docs.scarf.sh/package-analytics/#as-a-user-of-a-package-using-scarf-js-how-can-i-opt-out-of-analytics)\n\n###\n[`v4.0.5`](https://togithub.com/styled-components/polished/releases/tag/v4.0.5)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.4...v4.0.5)\n\n#### Documentation\n\n- `readableColor` - Update docs and function signature to be clearer\nabout the use of each parameter.\n\n###\n[`v4.0.4`](https://togithub.com/styled-components/polished/releases/tag/v4.0.4)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.3...v4.0.4)\n\n### Bug Fixes\n\n- **transparentize** - addressed an issue where we weren't handling\ncases where floats were greater than 2 decimals.\n([#​548](https://togithub.com/styled-components/polished/issues/548))\n- **npm** - addressed an issue where .yarn cache was bloating published\npackage size, along with some other ignore optimization.\n([#​553](https://togithub.com/styled-components/polished/issues/553)\nThanks [@​scttcper](https://togithub.com/scttcper))\n\n###\n[`v4.0.3`](https://togithub.com/styled-components/polished/releases/tag/v4.0.3)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.2...v4.0.3)\n\n### Bug Fix\n\n- Updated [@​babel/runtime](https://togithub.com/babel/runtime) to\naddress webpack v5 compatibility issue (Thanks\n[@​koba04](https://togithub.com/koba04) -\n[#​547](https://togithub.com/styled-components/polished/issues/547)\n)\n\n###\n[`v4.0.2`](https://togithub.com/styled-components/polished/releases/tag/v4.0.2)\n\n### Bug Fix\n\n- `ellipsis`: Fixes an issue where the `webkit` prefix was not properly\napplied with the multiline option. (Thanks\n[@​drakang4](https://togithub.com/drakang4) -\n[#​546](https://togithub.com/styled-components/polished/issues/546))\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- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://togithub.com/renovatebot/renovate).\n\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjUuMSIsInVwZGF0ZWRJblZlciI6IjM3LjQyNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJUZWFtOlNoYXJlZFVYIiwiYmFja3BvcnQ6YWxsLW9wZW4iLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==-->\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: jennypavlova <dzheni.pavlova@elastic.co>\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>","sha":"a402f4e584165b44d03b4773b1158b83e9b94551","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:SharedUX","backport:all-open","v9.1.0"],"title":"Update dependency polished to v4 (main)","number":206220,"url":"https://github.com/elastic/kibana/pull/206220","mergeCommit":{"message":"Update dependency polished to v4 (main) (#206220)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [polished](https://polished.js.org)\n([source](https://togithub.com/styled-components/polished)) |\ndependencies | major | [`^3.7.2` ->\n`^4.3.1`](https://renovatebot.com/diffs/npm/polished/3.7.2/4.3.1) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>styled-components/polished (polished)</summary>\n\n###\n[`v4.3.1`](https://togithub.com/styled-components/polished/releases/tag/v4.3.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.3.0...v4.3.1)\n\n### Bug Fixes & Improvements\n\n- Remove annotate-pure-calls plugin to address incompatibility with\nlater versions of rollup.\n- Update dependencies.\n\n###\n[`v4.3.0`](https://togithub.com/styled-components/polished/compare/v4.2.2...v4.3.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.2...v4.3.0)\n\n###\n[`v4.2.2`](https://togithub.com/styled-components/polished/releases/tag/v4.2.2)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.1...v4.2.2)\n\n### Bug Fixes\n\n- **Color Modules** - addresses an issue with longer floats in color\nvalues.\n([#​610](https://togithub.com/styled-components/polished/issues/610)\n- Thanks to [@​levymetal](https://togithub.com/levymetal))\n\n###\n[`v4.2.1`](https://togithub.com/styled-components/polished/releases/tag/v4.2.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.0...v4.2.1)\n\n### Bug Fixes\n\n- **`hls(a)`** - now properly parses percentages for opacity.\n- **`rgb(a)`** - now properly parses percentages for opacity.\n\n###\n[`v4.2.0`](https://togithub.com/styled-components/polished/releases/tag/v4.2.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.4...v4.2.0)\n\n### Improvements\n\n- **color Modules** - now support space-separated CSS color values for\nrgb(a) and hsl(a).\n([#​605](https://togithub.com/styled-components/polished/issues/605))\n- **`rgb`** - now accepts optional opacity value.\n- **`hsl`** - now accepts optional opacity value.\n\n###\n[`v4.1.4`](https://togithub.com/styled-components/polished/releases/tag/v4.1.4)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.3...v4.1.4)\n\n### Bug Fixes\n\n- **mix** - remove unnecessary division by 1\n([#​59](https://togithub.com/styled-components/polished/issues/59))\n\n###\n[`v4.1.3`](https://togithub.com/styled-components/polished/releases/tag/v4.1.3)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.2...v4.1.3)\n\n### Bug Fixes\n\n- Addressed several performance issues with regexes.\n\n###\n[`v4.1.2`](https://togithub.com/styled-components/polished/releases/tag/v4.1.2)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.1...v4.1.2)\n\n### Bug Fixes\n\n- **fluidRange** - updated return value to use an array to address\nunclear object property typing error in flow.\n\n###\n[`v4.1.1`](https://togithub.com/styled-components/polished/releases/tag/v4.1.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.0...v4.1.1)\n\n### Bug Fixes\n\n- **scarf** - removed scarf analytics package due to yarn\nincompatibilities and concerns over GDPR compliance.\n\n###\n[`v4.1.0`](https://togithub.com/styled-components/polished/releases/tag/v4.1.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.5...v4.1.0)\n\n### Introducing polished.js v4.1.0!\n\nWe're super stoked to announce that polished.js v4.1.0 is officially\nout! It is available via your package manager of choice. This will be\nthe final non-patch release before v5.\n\n`npm install polished`\n`yarn add polished`\n\n#### Release Highlights\n\n##### New Module\n\n- **`remToPx`**: We've introduced a new module to handle converting to\n`rem` values to `px` values.\n([#​376](https://togithub.com/styled-components/polished/issues/376))\n\n##### Analytics\n\n- We are now leveraging [Scarf](https://scarf.sh) to track package\nanalytics. You can opt-out of this functionality by following [these\ninstructions](https://docs.scarf.sh/package-analytics/#as-a-user-of-a-package-using-scarf-js-how-can-i-opt-out-of-analytics)\n\n###\n[`v4.0.5`](https://togithub.com/styled-components/polished/releases/tag/v4.0.5)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.4...v4.0.5)\n\n#### Documentation\n\n- `readableColor` - Update docs and function signature to be clearer\nabout the use of each parameter.\n\n###\n[`v4.0.4`](https://togithub.com/styled-components/polished/releases/tag/v4.0.4)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.3...v4.0.4)\n\n### Bug Fixes\n\n- **transparentize** - addressed an issue where we weren't handling\ncases where floats were greater than 2 decimals.\n([#​548](https://togithub.com/styled-components/polished/issues/548))\n- **npm** - addressed an issue where .yarn cache was bloating published\npackage size, along with some other ignore optimization.\n([#​553](https://togithub.com/styled-components/polished/issues/553)\nThanks [@​scttcper](https://togithub.com/scttcper))\n\n###\n[`v4.0.3`](https://togithub.com/styled-components/polished/releases/tag/v4.0.3)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.2...v4.0.3)\n\n### Bug Fix\n\n- Updated [@​babel/runtime](https://togithub.com/babel/runtime) to\naddress webpack v5 compatibility issue (Thanks\n[@​koba04](https://togithub.com/koba04) -\n[#​547](https://togithub.com/styled-components/polished/issues/547)\n)\n\n###\n[`v4.0.2`](https://togithub.com/styled-components/polished/releases/tag/v4.0.2)\n\n### Bug Fix\n\n- `ellipsis`: Fixes an issue where the `webkit` prefix was not properly\napplied with the multiline option. (Thanks\n[@​drakang4](https://togithub.com/drakang4) -\n[#​546](https://togithub.com/styled-components/polished/issues/546))\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- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://togithub.com/renovatebot/renovate).\n\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjUuMSIsInVwZGF0ZWRJblZlciI6IjM3LjQyNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJUZWFtOlNoYXJlZFVYIiwiYmFja3BvcnQ6YWxsLW9wZW4iLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==-->\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: jennypavlova <dzheni.pavlova@elastic.co>\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>","sha":"a402f4e584165b44d03b4773b1158b83e9b94551"}},"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/206220","number":206220,"mergeCommit":{"message":"Update dependency polished to v4 (main) (#206220)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [polished](https://polished.js.org)\n([source](https://togithub.com/styled-components/polished)) |\ndependencies | major | [`^3.7.2` ->\n`^4.3.1`](https://renovatebot.com/diffs/npm/polished/3.7.2/4.3.1) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>styled-components/polished (polished)</summary>\n\n###\n[`v4.3.1`](https://togithub.com/styled-components/polished/releases/tag/v4.3.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.3.0...v4.3.1)\n\n### Bug Fixes & Improvements\n\n- Remove annotate-pure-calls plugin to address incompatibility with\nlater versions of rollup.\n- Update dependencies.\n\n###\n[`v4.3.0`](https://togithub.com/styled-components/polished/compare/v4.2.2...v4.3.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.2...v4.3.0)\n\n###\n[`v4.2.2`](https://togithub.com/styled-components/polished/releases/tag/v4.2.2)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.1...v4.2.2)\n\n### Bug Fixes\n\n- **Color Modules** - addresses an issue with longer floats in color\nvalues.\n([#​610](https://togithub.com/styled-components/polished/issues/610)\n- Thanks to [@​levymetal](https://togithub.com/levymetal))\n\n###\n[`v4.2.1`](https://togithub.com/styled-components/polished/releases/tag/v4.2.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.0...v4.2.1)\n\n### Bug Fixes\n\n- **`hls(a)`** - now properly parses percentages for opacity.\n- **`rgb(a)`** - now properly parses percentages for opacity.\n\n###\n[`v4.2.0`](https://togithub.com/styled-components/polished/releases/tag/v4.2.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.4...v4.2.0)\n\n### Improvements\n\n- **color Modules** - now support space-separated CSS color values for\nrgb(a) and hsl(a).\n([#​605](https://togithub.com/styled-components/polished/issues/605))\n- **`rgb`** - now accepts optional opacity value.\n- **`hsl`** - now accepts optional opacity value.\n\n###\n[`v4.1.4`](https://togithub.com/styled-components/polished/releases/tag/v4.1.4)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.3...v4.1.4)\n\n### Bug Fixes\n\n- **mix** - remove unnecessary division by 1\n([#​59](https://togithub.com/styled-components/polished/issues/59))\n\n###\n[`v4.1.3`](https://togithub.com/styled-components/polished/releases/tag/v4.1.3)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.2...v4.1.3)\n\n### Bug Fixes\n\n- Addressed several performance issues with regexes.\n\n###\n[`v4.1.2`](https://togithub.com/styled-components/polished/releases/tag/v4.1.2)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.1...v4.1.2)\n\n### Bug Fixes\n\n- **fluidRange** - updated return value to use an array to address\nunclear object property typing error in flow.\n\n###\n[`v4.1.1`](https://togithub.com/styled-components/polished/releases/tag/v4.1.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.0...v4.1.1)\n\n### Bug Fixes\n\n- **scarf** - removed scarf analytics package due to yarn\nincompatibilities and concerns over GDPR compliance.\n\n###\n[`v4.1.0`](https://togithub.com/styled-components/polished/releases/tag/v4.1.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.5...v4.1.0)\n\n### Introducing polished.js v4.1.0!\n\nWe're super stoked to announce that polished.js v4.1.0 is officially\nout! It is available via your package manager of choice. This will be\nthe final non-patch release before v5.\n\n`npm install polished`\n`yarn add polished`\n\n#### Release Highlights\n\n##### New Module\n\n- **`remToPx`**: We've introduced a new module to handle converting to\n`rem` values to `px` values.\n([#​376](https://togithub.com/styled-components/polished/issues/376))\n\n##### Analytics\n\n- We are now leveraging [Scarf](https://scarf.sh) to track package\nanalytics. You can opt-out of this functionality by following [these\ninstructions](https://docs.scarf.sh/package-analytics/#as-a-user-of-a-package-using-scarf-js-how-can-i-opt-out-of-analytics)\n\n###\n[`v4.0.5`](https://togithub.com/styled-components/polished/releases/tag/v4.0.5)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.4...v4.0.5)\n\n#### Documentation\n\n- `readableColor` - Update docs and function signature to be clearer\nabout the use of each parameter.\n\n###\n[`v4.0.4`](https://togithub.com/styled-components/polished/releases/tag/v4.0.4)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.3...v4.0.4)\n\n### Bug Fixes\n\n- **transparentize** - addressed an issue where we weren't handling\ncases where floats were greater than 2 decimals.\n([#​548](https://togithub.com/styled-components/polished/issues/548))\n- **npm** - addressed an issue where .yarn cache was bloating published\npackage size, along with some other ignore optimization.\n([#​553](https://togithub.com/styled-components/polished/issues/553)\nThanks [@​scttcper](https://togithub.com/scttcper))\n\n###\n[`v4.0.3`](https://togithub.com/styled-components/polished/releases/tag/v4.0.3)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.2...v4.0.3)\n\n### Bug Fix\n\n- Updated [@​babel/runtime](https://togithub.com/babel/runtime) to\naddress webpack v5 compatibility issue (Thanks\n[@​koba04](https://togithub.com/koba04) -\n[#​547](https://togithub.com/styled-components/polished/issues/547)\n)\n\n###\n[`v4.0.2`](https://togithub.com/styled-components/polished/releases/tag/v4.0.2)\n\n### Bug Fix\n\n- `ellipsis`: Fixes an issue where the `webkit` prefix was not properly\napplied with the multiline option. (Thanks\n[@​drakang4](https://togithub.com/drakang4) -\n[#​546](https://togithub.com/styled-components/polished/issues/546))\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- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://togithub.com/renovatebot/renovate).\n\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjUuMSIsInVwZGF0ZWRJblZlciI6IjM3LjQyNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJUZWFtOlNoYXJlZFVYIiwiYmFja3BvcnQ6YWxsLW9wZW4iLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==-->\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: jennypavlova <dzheni.pavlova@elastic.co>\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>","sha":"a402f4e584165b44d03b4773b1158b83e9b94551"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
…0576) (#210903) # Backport This will backport the following commits from `main` to `8.16`: - [[Search] Increase search timeout toast lifetime to 1 week (#210576)](#210576) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ania Kowalska","email":"63072419+akowalska622@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T17:40:10Z","message":"[Search] Increase search timeout toast lifetime to 1 week (#210576)","sha":"7ed105d7151663966e2bb4c7b29fe3de92763a01","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:Search","enhancement","loe:small","impact:medium","Team:DataDiscovery","backport:prev-major","v9.1.0"],"title":"[Search] Increase search timeout toast lifetime to 1 week","number":210576,"url":"https://github.com/elastic/kibana/pull/210576","mergeCommit":{"message":"[Search] Increase search timeout toast lifetime to 1 week (#210576)","sha":"7ed105d7151663966e2bb4c7b29fe3de92763a01"}},"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/210576","number":210576,"mergeCommit":{"message":"[Search] Increase search timeout toast lifetime to 1 week (#210576)","sha":"7ed105d7151663966e2bb4c7b29fe3de92763a01"}}]}] BACKPORT--> Co-authored-by: Ania Kowalska <63072419+akowalska622@users.noreply.github.com>
…o d74b1fd (8.16) (#210725) This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `8df3ca6` -> `d74b1fd` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNiIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
# Backport This will backport the following commits from `main` to `8.16`: - [Fix notify_badge.tsx toggle not working (#208996)](#208996) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Eamonn-OL","email":"119305140+Eamonn-OL@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-14T09:56:43Z","message":"Fix notify_badge.tsx toggle not working (#208996)\n\n## Summary\n\nAt the moment, when you click on the notify badge in the \"rules\" page,\nthen click it again (expecting a toggle) it actually gets stuck on the\npage and only a refresh can fix it.\n\nThis change adds a toggle and implements it in place of the\n\"openPopover\" to correctly toggle the state of the popover.\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)\n\n\n\n## Release Notes\n\nFixes an issue where the popover in the rules page may get stuck when\nbeing clicked more than once.\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/2f092d63-ab69-41df-9047-1ba11481ea15\n\nAfter:\n\n\nhttps://github.com/user-attachments/assets/d1ef9abc-e0ee-44cb-ae75-0219047c4a67\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"995b851148fab19b0922f298a7c8b3607f00de9e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:ResponseOps","v9.0.0","Feature:Alerting/RulesManagement","backport:prev-major","v8.18.0","v9.1.0","v8.19.0","v8.17.3","v8.16.5"],"title":"Fix notify_badge.tsx toggle not working","number":208996,"url":"https://github.com/elastic/kibana/pull/208996","mergeCommit":{"message":"Fix notify_badge.tsx toggle not working (#208996)\n\n## Summary\n\nAt the moment, when you click on the notify badge in the \"rules\" page,\nthen click it again (expecting a toggle) it actually gets stuck on the\npage and only a refresh can fix it.\n\nThis change adds a toggle and implements it in place of the\n\"openPopover\" to correctly toggle the state of the popover.\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)\n\n\n\n## Release Notes\n\nFixes an issue where the popover in the rules page may get stuck when\nbeing clicked more than once.\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/2f092d63-ab69-41df-9047-1ba11481ea15\n\nAfter:\n\n\nhttps://github.com/user-attachments/assets/d1ef9abc-e0ee-44cb-ae75-0219047c4a67\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"995b851148fab19b0922f298a7c8b3607f00de9e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x","8.17","8.16"],"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/208996","number":208996,"mergeCommit":{"message":"Fix notify_badge.tsx toggle not working (#208996)\n\n## Summary\n\nAt the moment, when you click on the notify badge in the \"rules\" page,\nthen click it again (expecting a toggle) it actually gets stuck on the\npage and only a refresh can fix it.\n\nThis change adds a toggle and implements it in place of the\n\"openPopover\" to correctly toggle the state of the popover.\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)\n\n\n\n## Release Notes\n\nFixes an issue where the popover in the rules page may get stuck when\nbeing clicked more than once.\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/2f092d63-ab69-41df-9047-1ba11481ea15\n\nAfter:\n\n\nhttps://github.com/user-attachments/assets/d1ef9abc-e0ee-44cb-ae75-0219047c4a67\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"995b851148fab19b0922f298a7c8b3607f00de9e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Eamonn-OL <119305140+Eamonn-OL@users.noreply.github.com>
…reaks the chart panel (#210125) (#211057) # Backport This will backport the following commits from `main` to `8.16`: - [[visualize] fix Save to library action from a by value panel breaks the chart panel (#210125)](#210125) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T17:09:29Z","message":"[visualize] fix Save to library action from a by value panel breaks the chart panel (#210125)\n\nFixes https://github.com/elastic/kibana/issues/206921\r\n\r\n### Problem\r\nThe visualize embeddable is inconstant when passing runtime state to\r\n`buildEmbeddable`. Sometimes, only `{ savedObjectId }` is provided. The\r\nembeddable tried to work around this by calling `deserializeState` in\r\n`buildEmbeddable`.\r\n\r\nThere was a different bug with the `deserializeState` guard in\r\n`buildEmbeddable` where state like `{ savedObjectId, savedVis: {} }`\r\nwould not pass the guard. Dashboard adds runtime state so `savedVis` was\r\ngetting added to `initialState` and thus failing the guard\r\n\r\nThis resulted in the visualize embeddable trying to initialize with\r\nstate `{ savedObjectId }` instead of state in the shape `{\r\nsavedObjectId, serializedVis: {} }`. This resulted in error message like\r\n\"Could not read properties of undefined\" when the embeddable tried to\r\nread from `state.serializedVis.type`.\r\n\r\n### Solution\r\nThe solution is to ensure that `buildEmbeddable` is always passed\r\nruntime state containing `serializedVis`. This pattern is in line with\r\nthe lens embeddable.\r\n\r\n### Test instructions\r\n* install sample web logs\r\n* create agg based visualization\r\n* create new dashboard, add agg based visualization. Open context menu\r\nof vis and select \"Unlink from library\". (Side note, removing legacy\r\nvisualizations from add panel makes it hard to add by-value agg based\r\nvisualizations to a dashboard)\r\n* save dashboard\r\n* edit agg based vis\r\n* Click \"Save to library\" and fill out form\r\n* Verify visualization is rendered in dashboard.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"109dcce33864a4d8be2e5dc6ac088d8a9976afb5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","v9.0.0","project:embeddableRebuild","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.3","v8.16.5"],"title":"[visualize] fix Save to library action from a by value panel breaks the chart panel","number":210125,"url":"https://github.com/elastic/kibana/pull/210125","mergeCommit":{"message":"[visualize] fix Save to library action from a by value panel breaks the chart panel (#210125)\n\nFixes https://github.com/elastic/kibana/issues/206921\r\n\r\n### Problem\r\nThe visualize embeddable is inconstant when passing runtime state to\r\n`buildEmbeddable`. Sometimes, only `{ savedObjectId }` is provided. The\r\nembeddable tried to work around this by calling `deserializeState` in\r\n`buildEmbeddable`.\r\n\r\nThere was a different bug with the `deserializeState` guard in\r\n`buildEmbeddable` where state like `{ savedObjectId, savedVis: {} }`\r\nwould not pass the guard. Dashboard adds runtime state so `savedVis` was\r\ngetting added to `initialState` and thus failing the guard\r\n\r\nThis resulted in the visualize embeddable trying to initialize with\r\nstate `{ savedObjectId }` instead of state in the shape `{\r\nsavedObjectId, serializedVis: {} }`. This resulted in error message like\r\n\"Could not read properties of undefined\" when the embeddable tried to\r\nread from `state.serializedVis.type`.\r\n\r\n### Solution\r\nThe solution is to ensure that `buildEmbeddable` is always passed\r\nruntime state containing `serializedVis`. This pattern is in line with\r\nthe lens embeddable.\r\n\r\n### Test instructions\r\n* install sample web logs\r\n* create agg based visualization\r\n* create new dashboard, add agg based visualization. Open context menu\r\nof vis and select \"Unlink from library\". (Side note, removing legacy\r\nvisualizations from add panel makes it hard to add by-value agg based\r\nvisualizations to a dashboard)\r\n* save dashboard\r\n* edit agg based vis\r\n* Click \"Save to library\" and fill out form\r\n* Verify visualization is rendered in dashboard.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"109dcce33864a4d8be2e5dc6ac088d8a9976afb5"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.16"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211052","number":211052,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211050","number":211050,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210125","number":210125,"mergeCommit":{"message":"[visualize] fix Save to library action from a by value panel breaks the chart panel (#210125)\n\nFixes https://github.com/elastic/kibana/issues/206921\r\n\r\n### Problem\r\nThe visualize embeddable is inconstant when passing runtime state to\r\n`buildEmbeddable`. Sometimes, only `{ savedObjectId }` is provided. The\r\nembeddable tried to work around this by calling `deserializeState` in\r\n`buildEmbeddable`.\r\n\r\nThere was a different bug with the `deserializeState` guard in\r\n`buildEmbeddable` where state like `{ savedObjectId, savedVis: {} }`\r\nwould not pass the guard. Dashboard adds runtime state so `savedVis` was\r\ngetting added to `initialState` and thus failing the guard\r\n\r\nThis resulted in the visualize embeddable trying to initialize with\r\nstate `{ savedObjectId }` instead of state in the shape `{\r\nsavedObjectId, serializedVis: {} }`. This resulted in error message like\r\n\"Could not read properties of undefined\" when the embeddable tried to\r\nread from `state.serializedVis.type`.\r\n\r\n### Solution\r\nThe solution is to ensure that `buildEmbeddable` is always passed\r\nruntime state containing `serializedVis`. This pattern is in line with\r\nthe lens embeddable.\r\n\r\n### Test instructions\r\n* install sample web logs\r\n* create agg based visualization\r\n* create new dashboard, add agg based visualization. Open context menu\r\nof vis and select \"Unlink from library\". (Side note, removing legacy\r\nvisualizations from add panel makes it hard to add by-value agg based\r\nvisualizations to a dashboard)\r\n* save dashboard\r\n* edit agg based vis\r\n* Click \"Save to library\" and fill out form\r\n* Verify visualization is rendered in dashboard.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"109dcce33864a4d8be2e5dc6ac088d8a9976afb5"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211051","number":211051,"state":"OPEN"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
# Backport This will backport the following commits from `main` to `8.16`: - [Upgrade elliptic 6.5.7 → 6.6.1 (#211225)](#211225) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jeramy Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T17:29:24Z","message":"Upgrade elliptic 6.5.7 → 6.6.1 (#211225)\n\n## Summary\n\nUpgrades `elliptic` from v6.5.7 to v6.6.1","sha":"20aac5c9158fbfcfa4bd3284b169eaa192da53db","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","backport:all-open","v9.1.0"],"title":"Upgrade elliptic 6.5.7 → 6.6.1","number":211225,"url":"https://github.com/elastic/kibana/pull/211225","mergeCommit":{"message":"Upgrade elliptic 6.5.7 → 6.6.1 (#211225)\n\n## Summary\n\nUpgrades `elliptic` from v6.5.7 to v6.6.1","sha":"20aac5c9158fbfcfa4bd3284b169eaa192da53db"}},"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/211225","number":211225,"mergeCommit":{"message":"Upgrade elliptic 6.5.7 → 6.6.1 (#211225)\n\n## Summary\n\nUpgrades `elliptic` from v6.5.7 to v6.6.1","sha":"20aac5c9158fbfcfa4bd3284b169eaa192da53db"}}]}] BACKPORT--> Co-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2284 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
# Backport This will backport the following commits from `main` to `8.16`: - [Update dependency semver to ^7.7.1 (main) (#210557)](#210557) <!--- Backport version: 9.6.4 --> ### 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-02-12T12:16:24Z","message":"Update dependency semver to ^7.7.1 (main) (#210557)","sha":"bcfdd13c11871b37685a701eb781d9b9dbfa80e3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:all-open","v8.18.0","v9.1.0","v8.19.0"],"title":"Update dependency semver to ^7.7.1 (main)","number":210557,"url":"https://github.com/elastic/kibana/pull/210557","mergeCommit":{"message":"Update dependency semver to ^7.7.1 (main) (#210557)","sha":"bcfdd13c11871b37685a701eb781d9b9dbfa80e3"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210813","number":210813,"state":"MERGED","mergeCommit":{"sha":"ccb00f4d4b142cbd7cc7d840f46ecad075d62702","message":"[9.0] Update dependency semver to ^7.7.1 (main) (#210557) (#210813)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [Update dependency semver to ^7.7.1 (main)\n(#210557)](https://github.com/elastic/kibana/pull/210557)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT\n[{\"author\":{\"name\":\"elastic-renovate-prod[bot]\",\"email\":\"174716857+elastic-renovate-prod[bot]@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-12T12:16:24Z\",\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"Team:Core\",\"release_note:skip\",\"backport:all-open\",\"v9.1.0\"],\"title\":\"Update\ndependency semver to ^7.7.1\n(main)\",\"number\":210557,\"url\":\"https://github.com/elastic/kibana/pull/210557\",\"mergeCommit\":{\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\"}},\"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/210557\",\"number\":210557,\"mergeCommit\":{\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\"}}]}]\nBACKPORT-->\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210811","number":210811,"state":"MERGED","mergeCommit":{"sha":"c2d3c70ac99c80ed03381ecec7f91cf41910fbc0","message":"[8.18] Update dependency semver to ^7.7.1 (main) (#210557) (#210811)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [Update dependency semver to ^7.7.1 (main)\n(#210557)](https://github.com/elastic/kibana/pull/210557)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT\n[{\"author\":{\"name\":\"elastic-renovate-prod[bot]\",\"email\":\"174716857+elastic-renovate-prod[bot]@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-12T12:16:24Z\",\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"Team:Core\",\"release_note:skip\",\"backport:all-open\",\"v9.1.0\"],\"title\":\"Update\ndependency semver to ^7.7.1\n(main)\",\"number\":210557,\"url\":\"https://github.com/elastic/kibana/pull/210557\",\"mergeCommit\":{\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\"}},\"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/210557\",\"number\":210557,\"mergeCommit\":{\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\"}}]}]\nBACKPORT-->\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210557","number":210557,"mergeCommit":{"message":"Update dependency semver to ^7.7.1 (main) (#210557)","sha":"bcfdd13c11871b37685a701eb781d9b9dbfa80e3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210812","number":210812,"state":"MERGED","mergeCommit":{"sha":"5e9835c1d65b0b44999f3e23963d556b7d4d7b43","message":"[8.x] Update dependency semver to ^7.7.1 (main) (#210557) (#210812)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [Update dependency semver to ^7.7.1 (main)\n(#210557)](https://github.com/elastic/kibana/pull/210557)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT\n[{\"author\":{\"name\":\"elastic-renovate-prod[bot]\",\"email\":\"174716857+elastic-renovate-prod[bot]@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-12T12:16:24Z\",\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"Team:Core\",\"release_note:skip\",\"backport:all-open\",\"v9.1.0\"],\"title\":\"Update\ndependency semver to ^7.7.1\n(main)\",\"number\":210557,\"url\":\"https://github.com/elastic/kibana/pull/210557\",\"mergeCommit\":{\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\"}},\"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/210557\",\"number\":210557,\"mergeCommit\":{\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\"}}]}]\nBACKPORT-->\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>"}}]}] BACKPORT--> --------- Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
# Backport This will backport the following commits from `main` to `8.16`: - [Bump backport to v9.6.6 (#211424)](#211424) <!--- Backport version: 9.6.5 --> ### 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-02-17T16:08:53Z","message":"Bump backport to v9.6.6 (#211424)\n\nThis bumps backport to 9.6.6. Most notably fixes an issue with\nHandlebars templates and stripping markdown comments:\nhttps://github.com/sorenlouv/backport/compare/v9.6.4...v9.6.6\n\nAlso bumped here:\nhttps://github.com/elastic/kibana-github-actions/pull/55","sha":"a91e4fcd088dcdf93775bc9d9d9d77e3eec8ea59","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.1.0"],"title":"Bump backport to v9.6.6","number":211424,"url":"https://github.com/elastic/kibana/pull/211424","mergeCommit":{"message":"Bump backport to v9.6.6 (#211424)\n\nThis bumps backport to 9.6.6. Most notably fixes an issue with\nHandlebars templates and stripping markdown comments:\nhttps://github.com/sorenlouv/backport/compare/v9.6.4...v9.6.6\n\nAlso bumped here:\nhttps://github.com/elastic/kibana-github-actions/pull/55","sha":"a91e4fcd088dcdf93775bc9d9d9d77e3eec8ea59"}},"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/211424","number":211424,"mergeCommit":{"message":"Bump backport to v9.6.6 (#211424)\n\nThis bumps backport to 9.6.6. Most notably fixes an issue with\nHandlebars templates and stripping markdown comments:\nhttps://github.com/sorenlouv/backport/compare/v9.6.4...v9.6.6\n\nAlso bumped here:\nhttps://github.com/elastic/kibana-github-actions/pull/55","sha":"a91e4fcd088dcdf93775bc9d9d9d77e3eec8ea59"}}]}] BACKPORT--> Co-authored-by: Søren Louv-Jansen <soren.louv@elastic.co>
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2298 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
This PR contains the following updates: | Package | Type | Update | Change | Pending | |---|---|---|---|---| | [chromedriver](https://redirect.github.com/giggio/node-chromedriver) | devDependencies | major | [`^132.0.0` -> `^133.0.0`](https://renovatebot.com/diffs/npm/chromedriver/132.0.0/133.0.0) | `133.0.1` | --- ### Release Notes <details> <summary>giggio/node-chromedriver (chromedriver)</summary> ### [`v133.0.0`](https://redirect.github.com/giggio/node-chromedriver/compare/132.0.2...133.0.0) [Compare Source](https://redirect.github.com/giggio/node-chromedriver/compare/132.0.2...133.0.0) ### [`v132.0.2`](https://redirect.github.com/giggio/node-chromedriver/compare/132.0.1...132.0.2) [Compare Source](https://redirect.github.com/giggio/node-chromedriver/compare/132.0.1...132.0.2) ### [`v132.0.1`](https://redirect.github.com/giggio/node-chromedriver/compare/132.0.0...132.0.1) [Compare Source](https://redirect.github.com/giggio/node-chromedriver/compare/132.0.0...132.0.1) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjUuMSIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNiIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> --------- Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Jon <jon@elastic.co>
# Backport This will backport the following commits from `main` to `8.16`: - [[Links] Fix link settings not persisting (#211041)](#211041) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Hannah Mudge","email":"Heenawter@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-13T21:03:31Z","message":"[Links] Fix link settings not persisting (#211041)\n\nCloses https://github.com/elastic/kibana/issues/211022\r\n\r\n## Summary\r\n\r\nThis PR fixes a bug with persisting Link options where, because we\r\nweren't providing the \"initial\" state to the options editor, it was\r\nalways starting with the default state - therefore, editing something\r\n**other** than the options would reset the link options back to the\r\ndefault.\r\n\r\nI tested this in `8.14` and the bug was present there, too - based on\r\n[the file history / git\r\nblame](https://github.com/elastic/kibana/blame/main/src/platform/plugins/private/links/public/components/editor/link_editor.tsx#L60),\r\nthis bug has been around from the very beginning 🙈\r\n\r\n**Before:**\r\n\r\n\r\nhttps://github.com/user-attachments/assets/360af02e-ae0f-470c-91a3-a52fc9b3d8c6\r\n\r\n\r\n**After:**\r\n\r\n\r\nhttps://github.com/user-attachments/assets/d1e93bfa-566a-4506-99e3-47f92c922d49\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"c6e6a77c546450af30936fdedeef93221f83d291","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","loe:small","impact:low","backport:prev-major","Project:Dashboard Navigation","v9.1.0"],"title":"[Links] Fix link settings not persisting","number":211041,"url":"https://github.com/elastic/kibana/pull/211041","mergeCommit":{"message":"[Links] Fix link settings not persisting (#211041)\n\nCloses https://github.com/elastic/kibana/issues/211022\r\n\r\n## Summary\r\n\r\nThis PR fixes a bug with persisting Link options where, because we\r\nweren't providing the \"initial\" state to the options editor, it was\r\nalways starting with the default state - therefore, editing something\r\n**other** than the options would reset the link options back to the\r\ndefault.\r\n\r\nI tested this in `8.14` and the bug was present there, too - based on\r\n[the file history / git\r\nblame](https://github.com/elastic/kibana/blame/main/src/platform/plugins/private/links/public/components/editor/link_editor.tsx#L60),\r\nthis bug has been around from the very beginning 🙈\r\n\r\n**Before:**\r\n\r\n\r\nhttps://github.com/user-attachments/assets/360af02e-ae0f-470c-91a3-a52fc9b3d8c6\r\n\r\n\r\n**After:**\r\n\r\n\r\nhttps://github.com/user-attachments/assets/d1e93bfa-566a-4506-99e3-47f92c922d49\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"c6e6a77c546450af30936fdedeef93221f83d291"}},"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/211041","number":211041,"mergeCommit":{"message":"[Links] Fix link settings not persisting (#211041)\n\nCloses https://github.com/elastic/kibana/issues/211022\r\n\r\n## Summary\r\n\r\nThis PR fixes a bug with persisting Link options where, because we\r\nweren't providing the \"initial\" state to the options editor, it was\r\nalways starting with the default state - therefore, editing something\r\n**other** than the options would reset the link options back to the\r\ndefault.\r\n\r\nI tested this in `8.14` and the bug was present there, too - based on\r\n[the file history / git\r\nblame](https://github.com/elastic/kibana/blame/main/src/platform/plugins/private/links/public/components/editor/link_editor.tsx#L60),\r\nthis bug has been around from the very beginning 🙈\r\n\r\n**Before:**\r\n\r\n\r\nhttps://github.com/user-attachments/assets/360af02e-ae0f-470c-91a3-a52fc9b3d8c6\r\n\r\n\r\n**After:**\r\n\r\n\r\nhttps://github.com/user-attachments/assets/d1e93bfa-566a-4506-99e3-47f92c922d49\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"c6e6a77c546450af30936fdedeef93221f83d291"}},{"url":"https://github.com/elastic/kibana/pull/211103","number":211103,"branch":"8.18","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/211104","number":211104,"branch":"8.x","state":"OPEN"}]}] BACKPORT-->
…#211072) (#211606) # Backport This will backport the following commits from `8.17` to `8.16`: - [[dashboard] fix legacy embeddables do not render in print mode (#211072)](#211072) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-02-18T16:09:44Z","message":"[dashboard] fix legacy embeddables do not render in print mode (#211072)\n\nCloses https://github.com/elastic/kibana/issues/211070\r\n\r\nImmediately resolve `DashboardContainer.untilContainerInitialized` when\r\nin print mode since controlGroupApi will never become available.\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1829e15687e04ac00011695bcbcfecd1d3cbb7a5","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:skip","project:embeddableRebuild","backport:version","v8.17.3","v8.16.5"],"title":"[dashboard] fix legacy embeddables do not render in print mode","number":211072,"url":"https://github.com/elastic/kibana/pull/211072","mergeCommit":{"message":"[dashboard] fix legacy embeddables do not render in print mode (#211072)\n\nCloses https://github.com/elastic/kibana/issues/211070\r\n\r\nImmediately resolve `DashboardContainer.untilContainerInitialized` when\r\nin print mode since controlGroupApi will never become available.\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1829e15687e04ac00011695bcbcfecd1d3cbb7a5"}},"sourceBranch":"8.17","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211072","number":211072,"mergeCommit":{"message":"[dashboard] fix legacy embeddables do not render in print mode (#211072)\n\nCloses https://github.com/elastic/kibana/issues/211070\r\n\r\nImmediately resolve `DashboardContainer.untilContainerInitialized` when\r\nin print mode since controlGroupApi will never become available.\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1829e15687e04ac00011695bcbcfecd1d3cbb7a5"}},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
# Backport This will backport the following commits from `main` to `8.16`: - [chore(NA): upgrade to webpack 5 (#191106)](#191106) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tiago Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T03:01:36Z","message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](#190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","Team:Fleet","v9.0.0","backport:all-open","ci:build-webpack-bundle-analyzer","Team:obs-ux-infra_services","v9.1.0"],"title":"chore(NA): upgrade to webpack 5","number":191106,"url":"https://github.com/elastic/kibana/pull/191106","mergeCommit":{"message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](#190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211145","number":211145,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/191106","number":191106,"mergeCommit":{"message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](#190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1"}},{"url":"https://github.com/elastic/kibana/pull/211146","number":211146,"branch":"8.x","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/211147","number":211147,"branch":"8.18","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/211148","number":211148,"branch":"8.17","state":"OPEN"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
…cache plugin (#211231) (#211674) # Backport This will backport the following commits from `main` to `8.16`: - [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)](#211231) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tiago Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T17:07:41Z","message":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)\n\nThis PR solves an issue detected in the populate bundle cache plugin\nafter the webpack v5 migration. On the new version webpack v5 returns a\nlot of incomplete paths when we walk over file dependencies or internal\nmodules. The heuristic logic used previously was faulty so the fixes\nturns to use a cached filesystem api instead.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16a9136b93e2b9bc2e5d86ff7167a8ae0a563cdb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:prev-major","v8.18.0","v9.1.0","v8.19.0","v8.17.3"],"title":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin","number":211231,"url":"https://github.com/elastic/kibana/pull/211231","mergeCommit":{"message":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)\n\nThis PR solves an issue detected in the populate bundle cache plugin\nafter the webpack v5 migration. On the new version webpack v5 returns a\nlot of incomplete paths when we walk over file dependencies or internal\nmodules. The heuristic logic used previously was faulty so the fixes\nturns to use a cached filesystem api instead.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16a9136b93e2b9bc2e5d86ff7167a8ae0a563cdb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211284","number":211284,"state":"MERGED","mergeCommit":{"sha":"4bcd166b3aabbccbca03bd0a86110e29f0812171","message":"[8.18] fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231) (#211284)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache\nplugin (#211231)](https://github.com/elastic/kibana/pull/211231)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Tiago Costa <tiago.costa@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211231","number":211231,"mergeCommit":{"message":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)\n\nThis PR solves an issue detected in the populate bundle cache plugin\nafter the webpack v5 migration. On the new version webpack v5 returns a\nlot of incomplete paths when we walk over file dependencies or internal\nmodules. The heuristic logic used previously was faulty so the fixes\nturns to use a cached filesystem api instead.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16a9136b93e2b9bc2e5d86ff7167a8ae0a563cdb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211285","number":211285,"state":"MERGED","mergeCommit":{"sha":"73a5339547c64f9060465c4368e216744ce8d514","message":"[8.x] fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231) (#211285)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache\nplugin (#211231)](https://github.com/elastic/kibana/pull/211231)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Tiago Costa <tiago.costa@elastic.co>"}},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211672","number":211672,"state":"MERGED","mergeCommit":{"sha":"8f8369753beb6ed6ebd6ac705948b917d5abefc4","message":"[8.17] fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231) (#211672)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.17`:\n- [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache\nplugin (#211231)](https://github.com/elastic/kibana/pull/211231)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n"}}]}] BACKPORT-->
elastic-vault-github-plugin-prod
bot
requested a review
from kibanamachine
as a code owner
elastic-vault-github-plugin-prod
bot
added
release_note:skip
|
Pinging @elastic/fleet (Team:Fleet) |
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
auto-merge was automatically disabled
February 21, 2025 09:11
Pull request was closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2327