mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
82456 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
dd449b3158
|
[8.18] [ES|QL] Fixes the values control FT (#211159) (#211280)
# Backport This will backport the following commits from `main` to `8.18`: - [[ES|QL] Fixes the values control FT (#211159)](https://github.com/elastic/kibana/pull/211159) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T17:00:03Z","message":"[ES|QL] Fixes the values control FT (#211159)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/208454\n\nAttempt to make the value controls FR more stable","sha":"d3fd2ed7701b54f6048046d3f93e1bc8929dd686","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Presentation","Feature:ES|QL","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ES|QL] Fixes the values control FT","number":211159,"url":"https://github.com/elastic/kibana/pull/211159","mergeCommit":{"message":"[ES|QL] Fixes the values control FT (#211159)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/208454\n\nAttempt to make the value controls FR more stable","sha":"d3fd2ed7701b54f6048046d3f93e1bc8929dd686"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"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/211159","number":211159,"mergeCommit":{"message":"[ES|QL] Fixes the values control FT (#211159)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/208454\n\nAttempt to make the value controls FR more stable","sha":"d3fd2ed7701b54f6048046d3f93e1bc8929dd686"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co> |
||
Jean-Louis Leysens
|
d916369824
|
[8.18] [UA] Exclude enterprise search indices "Old index" deprecations (#210526) (#211162)
# Backport This will backport the following commits from `8.x` to `8.18`: - [[UA] Exclude enterprise search indices "Old index" deprecations (#210526)](https://github.com/elastic/kibana/pull/210526) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jean-Louis Leysens","email":"jeanlouis.leysens@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T18:23:43Z","message":"[UA] Exclude enterprise search indices \"Old index\" deprecations (#210526)\n\n## Summary\r\n\r\nExclude any \"Old data\" deprecations for `.ent-search-` indices. Note,\r\nother deprecations will still be present like frozen index deprecations:\r\n\r\n<img width=\"1219\" alt=\"Screenshot 2025-02-11 at 11 23 14\"\r\nsrc=\"https://github.com/user-attachments/assets/f896b919-f7e0-4a7e-b2ee-418db2bc1724\"\r\n/>","sha":"058845046e698cd8a57b7dce1ea2fe3397569ce9","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["blocked","Team:Core","release_note:skip","Feature:Upgrade Assistant","backport:version","v8.18.0","v8.19.0"],"title":"[UA] Exclude enterprise search indices \"Old index\" deprecations","number":210526,"url":"https://github.com/elastic/kibana/pull/210526","mergeCommit":{"message":"[UA] Exclude enterprise search indices \"Old index\" deprecations (#210526)\n\n## Summary\r\n\r\nExclude any \"Old data\" deprecations for `.ent-search-` indices. Note,\r\nother deprecations will still be present like frozen index deprecations:\r\n\r\n<img width=\"1219\" alt=\"Screenshot 2025-02-11 at 11 23 14\"\r\nsrc=\"https://github.com/user-attachments/assets/f896b919-f7e0-4a7e-b2ee-418db2bc1724\"\r\n/>","sha":"058845046e698cd8a57b7dce1ea2fe3397569ce9"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
4bcd166b3a
|
[8.18] fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231) (#211284)
# Backport This will backport the following commits from `main` to `8.18`: - [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)](https://github.com/elastic/kibana/pull/211231) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/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","v9.1.0"],"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":"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"}}]}] BACKPORT--> Co-authored-by: Tiago Costa <tiago.costa@elastic.co> |
||
Karen Grigoryan
|
ef85e7491b
|
[8.18] [Security Solution][Explore] Migrate from styled-components in shared (#210311) (#211226)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][Explore] Migrate from styled-components in shared (#210311)](https://github.com/elastic/kibana/pull/210311) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Karen Grigoryan","email":"karen.grigoryan@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T16:14:34Z","message":"[Security Solution][Explore] Migrate from styled-components in shared (#210311)\n\nAddresses #206436\r\n\r\n- Replace styled-components with @emotion/react and @emotion/styled\r\nacross multiple components\r\n- Remove `@kbn/ui-theme` instances\r\n- Update test cases to use @emotion/jest matchers for toHaveStyleRule to\r\nwork properly\r\n- Adjust styles to use `css` from `@emotion/react`\r\n- Remove unused imports and updated snapshots\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48b9ab41-23fd-4c00-ace9-c0cbe58c91f7","sha":"4b4c5ce491aa6539867c3de789ff604880a7fc2e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team:Threat Hunting:Explore","backport:version","v8.18.0","EUI Visual Refresh","v9.1.0","v8.19.0"],"title":"[Security Solution][Explore] Migrate from styled-components in shared","number":210311,"url":"https://github.com/elastic/kibana/pull/210311","mergeCommit":{"message":"[Security Solution][Explore] Migrate from styled-components in shared (#210311)\n\nAddresses #206436\r\n\r\n- Replace styled-components with @emotion/react and @emotion/styled\r\nacross multiple components\r\n- Remove `@kbn/ui-theme` instances\r\n- Update test cases to use @emotion/jest matchers for toHaveStyleRule to\r\nwork properly\r\n- Adjust styles to use `css` from `@emotion/react`\r\n- Remove unused imports and updated snapshots\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48b9ab41-23fd-4c00-ace9-c0cbe58c91f7","sha":"4b4c5ce491aa6539867c3de789ff604880a7fc2e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"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/210311","number":210311,"mergeCommit":{"message":"[Security Solution][Explore] Migrate from styled-components in shared (#210311)\n\nAddresses #206436\r\n\r\n- Replace styled-components with @emotion/react and @emotion/styled\r\nacross multiple components\r\n- Remove `@kbn/ui-theme` instances\r\n- Update test cases to use @emotion/jest matchers for toHaveStyleRule to\r\nwork properly\r\n- Adjust styles to use `css` from `@emotion/react`\r\n- Remove unused imports and updated snapshots\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48b9ab41-23fd-4c00-ace9-c0cbe58c91f7","sha":"4b4c5ce491aa6539867c3de789ff604880a7fc2e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
9944e1af97
|
[8.18] [Security Solution] Fix flakiness in `prebuilt_rules_preview.cy.ts` (#211034) (#211227)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Fix flakiness in `prebuilt_rules_preview.cy.ts` (#211034)](https://github.com/elastic/kibana/pull/211034) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T14:13:32Z","message":"[Security Solution] Fix flakiness in `prebuilt_rules_preview.cy.ts` (#211034)\n\n## Summary\r\n\r\nThis PR fixes Rule Management Prebuilt Rules preview Cypress tests flakiness. The flakiness was localized to `prebuilt_rules_preview.cy.ts`.\r\n\r\n## Problem details\r\n\r\nQuite recently Rule Management Prebuilt Cypress tests group started failing due to exceeding 1 hour execution limit. In normal conditions the group takes up to 45 minutes to run all the tests.\r\n\r\nInvestigation revealed the problem. It turned out the real prebuilt rules get installed while it's not expected. The absolute majority of the tests interact with a few prebuilt rule assets mocks to avoid heavy prebuilt rules package installation and installing more than 1K rules from the package. \r\n\r\n\r\nIn particular `/internal/detection_engine/prebuilt_rules/_bootstrap` endpoint is invoked upon loading any Security Solution plugin's page and leads to installing a prebuilt rules package. The Cypress test code was organized in way that first the Rule Management page is opened and then API calls interception is set up. Since page loading may vary sometimes real calls to `/internal/detection_engine/prebuilt_rules/_bootstrap` went through.\r\n\r\nTests set up prebuilt rule assets mocks but real prebuilt rules package installation wiped out the mocks leading to failing tests. Since Cypress reruns failed tests execution time increases and exceeds the limit.\r\n\r\n\r\n\r\n*`installPrebuiltRuleAssets()` sets up `/internal/detection_engine/prebuilt_rules/_bootstrap` calls interception.\r\n\r\n## Flaky test runs\r\n\r\n**Before:**\r\n\r\n- `prebuilt_rules_preview.cy.ts` was run in Flaky test runner with 100 iterations. The CI is green but it's easy to notice some jobs took approximately 1 hour to run.\r\n 🔴 https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7870\r\n\r\n**After:**\r\n\r\n- `prebuilt_rules_preview.cy.ts` with the fix was run in Flaky test runner with 100 iterations. Execution time approximately 15 minutes for each job.\r\n ✅ https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7873\r\n\r\n- Rule Management Prebuilt Cypress tests group was run with 100 iterations\r\n ✅ https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7875","sha":"67163cb80231ad78cab96f091203660d4da7559f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Fix flakiness in `prebuilt_rules_preview.cy.ts`","number":211034,"url":"https://github.com/elastic/kibana/pull/211034","mergeCommit":{"message":"[Security Solution] Fix flakiness in `prebuilt_rules_preview.cy.ts` (#211034)\n\n## Summary\r\n\r\nThis PR fixes Rule Management Prebuilt Rules preview Cypress tests flakiness. The flakiness was localized to `prebuilt_rules_preview.cy.ts`.\r\n\r\n## Problem details\r\n\r\nQuite recently Rule Management Prebuilt Cypress tests group started failing due to exceeding 1 hour execution limit. In normal conditions the group takes up to 45 minutes to run all the tests.\r\n\r\nInvestigation revealed the problem. It turned out the real prebuilt rules get installed while it's not expected. The absolute majority of the tests interact with a few prebuilt rule assets mocks to avoid heavy prebuilt rules package installation and installing more than 1K rules from the package. \r\n\r\n\r\nIn particular `/internal/detection_engine/prebuilt_rules/_bootstrap` endpoint is invoked upon loading any Security Solution plugin's page and leads to installing a prebuilt rules package. The Cypress test code was organized in way that first the Rule Management page is opened and then API calls interception is set up. Since page loading may vary sometimes real calls to `/internal/detection_engine/prebuilt_rules/_bootstrap` went through.\r\n\r\nTests set up prebuilt rule assets mocks but real prebuilt rules package installation wiped out the mocks leading to failing tests. Since Cypress reruns failed tests execution time increases and exceeds the limit.\r\n\r\n\r\n\r\n*`installPrebuiltRuleAssets()` sets up `/internal/detection_engine/prebuilt_rules/_bootstrap` calls interception.\r\n\r\n## Flaky test runs\r\n\r\n**Before:**\r\n\r\n- `prebuilt_rules_preview.cy.ts` was run in Flaky test runner with 100 iterations. The CI is green but it's easy to notice some jobs took approximately 1 hour to run.\r\n 🔴 https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7870\r\n\r\n**After:**\r\n\r\n- `prebuilt_rules_preview.cy.ts` with the fix was run in Flaky test runner with 100 iterations. Execution time approximately 15 minutes for each job.\r\n ✅ https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7873\r\n\r\n- Rule Management Prebuilt Cypress tests group was run with 100 iterations\r\n ✅ https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7875","sha":"67163cb80231ad78cab96f091203660d4da7559f"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"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/211034","number":211034,"mergeCommit":{"message":"[Security Solution] Fix flakiness in `prebuilt_rules_preview.cy.ts` (#211034)\n\n## Summary\r\n\r\nThis PR fixes Rule Management Prebuilt Rules preview Cypress tests flakiness. The flakiness was localized to `prebuilt_rules_preview.cy.ts`.\r\n\r\n## Problem details\r\n\r\nQuite recently Rule Management Prebuilt Cypress tests group started failing due to exceeding 1 hour execution limit. In normal conditions the group takes up to 45 minutes to run all the tests.\r\n\r\nInvestigation revealed the problem. It turned out the real prebuilt rules get installed while it's not expected. The absolute majority of the tests interact with a few prebuilt rule assets mocks to avoid heavy prebuilt rules package installation and installing more than 1K rules from the package. \r\n\r\n\r\nIn particular `/internal/detection_engine/prebuilt_rules/_bootstrap` endpoint is invoked upon loading any Security Solution plugin's page and leads to installing a prebuilt rules package. The Cypress test code was organized in way that first the Rule Management page is opened and then API calls interception is set up. Since page loading may vary sometimes real calls to `/internal/detection_engine/prebuilt_rules/_bootstrap` went through.\r\n\r\nTests set up prebuilt rule assets mocks but real prebuilt rules package installation wiped out the mocks leading to failing tests. Since Cypress reruns failed tests execution time increases and exceeds the limit.\r\n\r\n\r\n\r\n*`installPrebuiltRuleAssets()` sets up `/internal/detection_engine/prebuilt_rules/_bootstrap` calls interception.\r\n\r\n## Flaky test runs\r\n\r\n**Before:**\r\n\r\n- `prebuilt_rules_preview.cy.ts` was run in Flaky test runner with 100 iterations. The CI is green but it's easy to notice some jobs took approximately 1 hour to run.\r\n 🔴 https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7870\r\n\r\n**After:**\r\n\r\n- `prebuilt_rules_preview.cy.ts` with the fix was run in Flaky test runner with 100 iterations. Execution time approximately 15 minutes for each job.\r\n ✅ https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7873\r\n\r\n- Rule Management Prebuilt Cypress tests group was run with 100 iterations\r\n ✅ https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7875","sha":"67163cb80231ad78cab96f091203660d4da7559f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> |
||
|
Kibana Machine
|
d2a626f983
|
[8.18] [Security Solution] Test plan for upgrading prebuilt rules with preview (Rule Upgrade flyout) v1 (#205645) (#211249)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Test plan for upgrading prebuilt rules with preview (Rule Upgrade flyout) v1 (#205645)](https://github.com/elastic/kibana/pull/205645) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T15:21:09Z","message":"[Security Solution] Test plan for upgrading prebuilt rules with preview (Rule Upgrade flyout) v1 (#205645)\n\n**Epics:** https://github.com/elastic/security-team/issues/1974\r\n(internal), https://github.com/elastic/kibana/issues/174168\r\n**Addresses:** https://github.com/elastic/kibana/issues/202078\r\n\r\n## Summary\r\n\r\nThis PR adds a test plan for rule upgrade flyout.\r\n\r\n---------\r\n\r\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"ecd33168b152d0c268d4cec7881deedeb7628814","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Test plan for upgrading prebuilt rules with preview (Rule Upgrade flyout) v1","number":205645,"url":"https://github.com/elastic/kibana/pull/205645","mergeCommit":{"message":"[Security Solution] Test plan for upgrading prebuilt rules with preview (Rule Upgrade flyout) v1 (#205645)\n\n**Epics:** https://github.com/elastic/security-team/issues/1974\r\n(internal), https://github.com/elastic/kibana/issues/174168\r\n**Addresses:** https://github.com/elastic/kibana/issues/202078\r\n\r\n## Summary\r\n\r\nThis PR adds a test plan for rule upgrade flyout.\r\n\r\n---------\r\n\r\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"ecd33168b152d0c268d4cec7881deedeb7628814"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"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/205645","number":205645,"mergeCommit":{"message":"[Security Solution] Test plan for upgrading prebuilt rules with preview (Rule Upgrade flyout) v1 (#205645)\n\n**Epics:** https://github.com/elastic/security-team/issues/1974\r\n(internal), https://github.com/elastic/kibana/issues/174168\r\n**Addresses:** https://github.com/elastic/kibana/issues/202078\r\n\r\n## Summary\r\n\r\nThis PR adds a test plan for rule upgrade flyout.\r\n\r\n---------\r\n\r\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"ecd33168b152d0c268d4cec7881deedeb7628814"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> |
||
|
Kibana Machine
|
3f4fc859c8
|
[8.18] [Security Solution] Test plan for upgrading prebuilt rules without preview (Rule Updates table) v2 (#205922) (#211245)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Test plan for upgrading prebuilt rules without preview (Rule Updates table) v2 (#205922)](https://github.com/elastic/kibana/pull/205922) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T15:18:40Z","message":"[Security Solution] Test plan for upgrading prebuilt rules without preview (Rule Updates table) v2 (#205922)\n\n**Addresses:** https://github.com/elastic/kibana/issues/202078\r\n\r\n## Summary\r\n\r\nThis PR extends rule upgrade test plan with customizable and\r\nnon-customizable field examples. Rule upgrade workflow test plan\r\n(excluding Rule Upgrade flyout) was initially extended in\r\nhttps://github.com/elastic/kibana/pull/203331.\r\n\r\nhttps://github.com/elastic/kibana/pull/203331 adds the following rule\r\nupgrade workflow scenarios\r\n\r\n- Scenario: User can upgrade conflict-free prebuilt rules one by one\r\n- Scenario: User cannot upgrade prebuilt rules one by one from Rules\r\nUpdate table if they have conflicts\r\n- Scenario: User can upgrade multiple conflict-free prebuilt rules\r\nselected on the page\r\n- Scenario: User cannot upgrade selected prebuilt rules with conflicts\r\n- Scenario: User can upgrade all available conflict-free prebuilt rules\r\nat once*\r\n- Scenario: User cannot upgrade all prebuilt rules at once if they have\r\nupgrade conflicts\r\n- Scenario: User can upgrade only conflict-free rules when a mix of\r\nrules with and without conflicts are selected for upgrade\r\n- Scenario: User can upgrade only conflict-free rules when attempting to\r\nupgrade all rules\r\n- Scenario: User can upgrade rule with rule type change individually\r\n- Scenario: User can not bulk upgrade selected rules with rule type\r\nchanges\r\n- Scenario: User can not bulk upgrade all rules with rule type changes\r\n- Scenario: API does not upgrade prebuilt rules if they are up to date\r\n\r\n---------\r\n\r\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"e29033a726930c3d891aa77ea4f7ed990c7ee511","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Test plan for upgrading prebuilt rules without preview (Rule Updates table) v2","number":205922,"url":"https://github.com/elastic/kibana/pull/205922","mergeCommit":{"message":"[Security Solution] Test plan for upgrading prebuilt rules without preview (Rule Updates table) v2 (#205922)\n\n**Addresses:** https://github.com/elastic/kibana/issues/202078\r\n\r\n## Summary\r\n\r\nThis PR extends rule upgrade test plan with customizable and\r\nnon-customizable field examples. Rule upgrade workflow test plan\r\n(excluding Rule Upgrade flyout) was initially extended in\r\nhttps://github.com/elastic/kibana/pull/203331.\r\n\r\nhttps://github.com/elastic/kibana/pull/203331 adds the following rule\r\nupgrade workflow scenarios\r\n\r\n- Scenario: User can upgrade conflict-free prebuilt rules one by one\r\n- Scenario: User cannot upgrade prebuilt rules one by one from Rules\r\nUpdate table if they have conflicts\r\n- Scenario: User can upgrade multiple conflict-free prebuilt rules\r\nselected on the page\r\n- Scenario: User cannot upgrade selected prebuilt rules with conflicts\r\n- Scenario: User can upgrade all available conflict-free prebuilt rules\r\nat once*\r\n- Scenario: User cannot upgrade all prebuilt rules at once if they have\r\nupgrade conflicts\r\n- Scenario: User can upgrade only conflict-free rules when a mix of\r\nrules with and without conflicts are selected for upgrade\r\n- Scenario: User can upgrade only conflict-free rules when attempting to\r\nupgrade all rules\r\n- Scenario: User can upgrade rule with rule type change individually\r\n- Scenario: User can not bulk upgrade selected rules with rule type\r\nchanges\r\n- Scenario: User can not bulk upgrade all rules with rule type changes\r\n- Scenario: API does not upgrade prebuilt rules if they are up to date\r\n\r\n---------\r\n\r\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"e29033a726930c3d891aa77ea4f7ed990c7ee511"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"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/205922","number":205922,"mergeCommit":{"message":"[Security Solution] Test plan for upgrading prebuilt rules without preview (Rule Updates table) v2 (#205922)\n\n**Addresses:** https://github.com/elastic/kibana/issues/202078\r\n\r\n## Summary\r\n\r\nThis PR extends rule upgrade test plan with customizable and\r\nnon-customizable field examples. Rule upgrade workflow test plan\r\n(excluding Rule Upgrade flyout) was initially extended in\r\nhttps://github.com/elastic/kibana/pull/203331.\r\n\r\nhttps://github.com/elastic/kibana/pull/203331 adds the following rule\r\nupgrade workflow scenarios\r\n\r\n- Scenario: User can upgrade conflict-free prebuilt rules one by one\r\n- Scenario: User cannot upgrade prebuilt rules one by one from Rules\r\nUpdate table if they have conflicts\r\n- Scenario: User can upgrade multiple conflict-free prebuilt rules\r\nselected on the page\r\n- Scenario: User cannot upgrade selected prebuilt rules with conflicts\r\n- Scenario: User can upgrade all available conflict-free prebuilt rules\r\nat once*\r\n- Scenario: User cannot upgrade all prebuilt rules at once if they have\r\nupgrade conflicts\r\n- Scenario: User can upgrade only conflict-free rules when a mix of\r\nrules with and without conflicts are selected for upgrade\r\n- Scenario: User can upgrade only conflict-free rules when attempting to\r\nupgrade all rules\r\n- Scenario: User can upgrade rule with rule type change individually\r\n- Scenario: User can not bulk upgrade selected rules with rule type\r\nchanges\r\n- Scenario: User can not bulk upgrade all rules with rule type changes\r\n- Scenario: API does not upgrade prebuilt rules if they are up to date\r\n\r\n---------\r\n\r\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"e29033a726930c3d891aa77ea4f7ed990c7ee511"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> |
||
|
Jean-Louis Leysens
|
22a7481989
|
[8.18] [UA] Handle frozen indices deprecations (#208156) (#211165)
# Backport This will backport the following commits from `8.x` to `8.18`: - [[UA] Handle frozen indices deprecations (#208156)](https://github.com/elastic/kibana/pull/208156) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-01-30T22:36:28Z","message":"[UA] Handle frozen indices deprecations (#208156)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana-team/issues/1392\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cc358e3c46e5df2af834e341114f23aa1fd4f7d1","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:version","v8.18.0","v8.19.0"],"number":208156,"url":"https://github.com/elastic/kibana/pull/208156","mergeCommit":{"message":"[UA] Handle frozen indices deprecations (#208156)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana-team/issues/1392\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cc358e3c46e5df2af834e341114f23aa1fd4f7d1"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co> |
||
Alex Szabo
|
bd324526fc | skip failing suite (#206068) | ||
|
Alex Szabo
|
f7a5e7dc7f | skip failing suite (#205987) | ||
|
Alex Szabo
|
e9e744dc95 | skip failing suite (#206368) | ||
Angela Chuang
|
92e54c4d69
|
[8.18][SecuritySolution] Update severity colors for Borealis theme (#206276) (#211021)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution]Update severity colors for Borealis theme (#206276)](https://github.com/elastic/kibana/pull/206276) |
||
Tiago Costa
|
c7f893aebd
|
[8.18] chore(NA): upgrade to webpack 5 (#191106) (#211147)
# Backport This will backport the following commits from `main` to `8.18`: - [chore(NA): upgrade to webpack 5 (#191106)](https://github.com/elastic/kibana/pull/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](https://github.com/elastic/kibana/issues/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](https://github.com/elastic/kibana/issues/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](https://github.com/elastic/kibana/issues/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"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
a163691e0f
|
[8.18] Fix notify_badge.tsx toggle not working (#208996) (#211186)
# Backport This will backport the following commits from `main` to `8.18`: - [Fix notify_badge.tsx toggle not working (#208996)](https://github.com/elastic/kibana/pull/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\n |
||
|
Kibana Machine
|
6db8685223
|
[8.18] [Lens][Embeddable] Fix memory leak on ES|QL variables subscription (#210826) (#211170)
# Backport This will backport the following commits from `main` to `8.18`: - [[Lens][Embeddable] Fix memory leak on ES|QL variables subscription (#210826)](https://github.com/elastic/kibana/pull/210826) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marco Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-14T09:18:55Z","message":"[Lens][Embeddable] Fix memory leak on ES|QL variables subscription (#210826)\n\n## Summary\n\nThis PR fixes a bug due to multiple subscription created by the ESQL\nvariables logic in the embeddable to never been cancelled.\nThe fix was to move the subscription in the loader module and make it\ncleanup correctly together with other subscription.\n\nUnit tests have been added to check the correct re-render behaviour.\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"34baecba3e11a14f5aaf3badc053056084945b33","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","backport:prev-major","v9.1.0"],"title":"[Lens][Embeddable] Fix memory leak on ES|QL variables subscription","number":210826,"url":"https://github.com/elastic/kibana/pull/210826","mergeCommit":{"message":"[Lens][Embeddable] Fix memory leak on ES|QL variables subscription (#210826)\n\n## Summary\n\nThis PR fixes a bug due to multiple subscription created by the ESQL\nvariables logic in the embeddable to never been cancelled.\nThe fix was to move the subscription in the loader module and make it\ncleanup correctly together with other subscription.\n\nUnit tests have been added to check the correct re-render behaviour.\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"34baecba3e11a14f5aaf3badc053056084945b33"}},"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/210826","number":210826,"mergeCommit":{"message":"[Lens][Embeddable] Fix memory leak on ES|QL variables subscription (#210826)\n\n## Summary\n\nThis PR fixes a bug due to multiple subscription created by the ESQL\nvariables logic in the embeddable to never been cancelled.\nThe fix was to move the subscription in the loader module and make it\ncleanup correctly together with other subscription.\n\nUnit tests have been added to check the correct re-render behaviour.\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"34baecba3e11a14f5aaf3badc053056084945b33"}}]}] BACKPORT--> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com> |
||
Bharat Pasupula
|
d7f4eddcf4
|
[8.18] [Automatic Import] Fix generated name for integration title (#210916) (#211150)
# Backport This will backport the following commits from `main` to `8.18`: - [[Automatic Import] Fix generated name for integration title (#210916)](https://github.com/elastic/kibana/pull/210916) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-13T16:02:03Z","message":"[Automatic Import] Fix generated name for integration title (#210916)\n\n## Summary\r\n\r\nA bug was introduced with #210770 and this PR fixes that. The Package\r\nname generated is validated.","sha":"cf0f338d8749c90024b2409fbb7b036469bfab6e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-minor","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport","v9.1.0"],"title":"[Automatic Import] Fix generated name for integration title","number":210916,"url":"https://github.com/elastic/kibana/pull/210916","mergeCommit":{"message":"[Automatic Import] Fix generated name for integration title (#210916)\n\n## Summary\r\n\r\nA bug was introduced with #210770 and this PR fixes that. The Package\r\nname generated is validated.","sha":"cf0f338d8749c90024b2409fbb7b036469bfab6e"}},"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/211037","number":211037,"state":"MERGED","mergeCommit":{"sha":"badb523efc6e567dc33136f84bae6c240de7ab4c","message":"[9.0] [Automatic Import] Fix generated name for integration title (#210916) (#211037)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Automatic Import] Fix generated name for integration title\n(#210916)](https://github.com/elastic/kibana/pull/210916)\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\":\"Bharat\nPasupula\",\"email\":\"123897612+bhapas@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-13T16:02:03Z\",\"message\":\"[Automatic\nImport] Fix generated name for integration title (#210916)\\n\\n##\nSummary\\r\\n\\r\\nA bug was introduced with #210770 and this PR fixes that.\nThe Package\\r\\nname generated is\nvalidated.\",\"sha\":\"cf0f338d8749c90024b2409fbb7b036469bfab6e\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"backport:prev-minor\",\"Team:Security-Scalability\",\"Feature:AutomaticImport\",\"v9.1.0\"],\"title\":\"[Automatic\nImport] Fix generated name for integration\ntitle\",\"number\":210916,\"url\":\"https://github.com/elastic/kibana/pull/210916\",\"mergeCommit\":{\"message\":\"[Automatic\nImport] Fix generated name for integration title (#210916)\\n\\n##\nSummary\\r\\n\\r\\nA bug was introduced with #210770 and this PR fixes that.\nThe Package\\r\\nname generated is\nvalidated.\",\"sha\":\"cf0f338d8749c90024b2409fbb7b036469bfab6e\"}},\"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/210916\",\"number\":210916,\"mergeCommit\":{\"message\":\"[Automatic\nImport] Fix generated name for integration title (#210916)\\n\\n##\nSummary\\r\\n\\r\\nA bug was introduced with #210770 and this PR fixes that.\nThe Package\\r\\nname generated is\nvalidated.\",\"sha\":\"cf0f338d8749c90024b2409fbb7b036469bfab6e\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Bharat Pasupula <123897612+bhapas@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/210916","number":210916,"mergeCommit":{"message":"[Automatic Import] Fix generated name for integration title (#210916)\n\n## Summary\r\n\r\nA bug was introduced with #210770 and this PR fixes that. The Package\r\nname generated is validated.","sha":"cf0f338d8749c90024b2409fbb7b036469bfab6e"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
0f548e8040
|
[8.18] [Fleet] Make sure null checks are included for agentless next steps tile (#211068) (#211143)
# Backport This will backport the following commits from `main` to `8.18`: - [[Fleet] Make sure null checks are included for agentless next steps tile (#211068)](https://github.com/elastic/kibana/pull/211068) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kyle Pollich","email":"kyle.pollich@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T21:53:37Z","message":"[Fleet] Make sure null checks are included for agentless next steps tile (#211068)\n\n## Summary\n\nCloses https://github.com/elastic/security-team/issues/11870\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co>","sha":"11211cfb273a49f5341db5da80bf401d577e57b4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor","backport:prev-major","v9.1.0","backport:8.18"],"title":"[Fleet] Make sure null checks are included for agentless next steps tile","number":211068,"url":"https://github.com/elastic/kibana/pull/211068","mergeCommit":{"message":"[Fleet] Make sure null checks are included for agentless next steps tile (#211068)\n\n## Summary\n\nCloses https://github.com/elastic/security-team/issues/11870\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co>","sha":"11211cfb273a49f5341db5da80bf401d577e57b4"}},"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/211120","number":211120,"state":"MERGED","mergeCommit":{"sha":"8fa37fdc98cf9d482c2f3e32640be3fd9aad43bd","message":"[9.0] [Fleet] Make sure null checks are included for agentless next steps tile (#211068) (#211120)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Fleet] Make sure null checks are included for agentless next steps\ntile (#211068)](https://github.com/elastic/kibana/pull/211068)\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\":\"Kyle\nPollich\",\"email\":\"kyle.pollich@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-13T21:53:37Z\",\"message\":\"[Fleet]\nMake sure null checks are included for agentless next steps tile\n(#211068)\\n\\n## Summary\\n\\nCloses\nhttps://github.com/elastic/security-team/issues/11870\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n- [ ] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common scenarios\\n- [ ] The PR\ndescription includes the appropriate Release Notes section,\\nand the\ncorrect `release_note:*` label is applied per\nthe\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\n\\n---------\\n\\nCo-authored-by:\nNicolas Chaulet\n<nicolas.chaulet@elastic.co>\",\"sha\":\"11211cfb273a49f5341db5da80bf401d577e57b4\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"Team:Fleet\",\"backport:prev-minor\",\"v9.1.0\",\"backport:8.18\"],\"title\":\"[Fleet]\nMake sure null checks are included for agentless next steps\ntile\",\"number\":211068,\"url\":\"https://github.com/elastic/kibana/pull/211068\",\"mergeCommit\":{\"message\":\"[Fleet]\nMake sure null checks are included for agentless next steps tile\n(#211068)\\n\\n## Summary\\n\\nCloses\nhttps://github.com/elastic/security-team/issues/11870\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n- [ ] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common scenarios\\n- [ ] The PR\ndescription includes the appropriate Release Notes section,\\nand the\ncorrect `release_note:*` label is applied per\nthe\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\n\\n---------\\n\\nCo-authored-by:\nNicolas Chaulet\n<nicolas.chaulet@elastic.co>\",\"sha\":\"11211cfb273a49f5341db5da80bf401d577e57b4\"}},\"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/211068\",\"number\":211068,\"mergeCommit\":{\"message\":\"[Fleet]\nMake sure null checks are included for agentless next steps tile\n(#211068)\\n\\n## Summary\\n\\nCloses\nhttps://github.com/elastic/security-team/issues/11870\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n- [ ] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common scenarios\\n- [ ] The PR\ndescription includes the appropriate Release Notes section,\\nand the\ncorrect `release_note:*` label is applied per\nthe\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\n\\n---------\\n\\nCo-authored-by:\nNicolas Chaulet\n<nicolas.chaulet@elastic.co>\",\"sha\":\"11211cfb273a49f5341db5da80bf401d577e57b4\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Kyle Pollich <kyle.pollich@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211068","number":211068,"mergeCommit":{"message":"[Fleet] Make sure null checks are included for agentless next steps tile (#211068)\n\n## Summary\n\nCloses https://github.com/elastic/security-team/issues/11870\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co>","sha":"11211cfb273a49f5341db5da80bf401d577e57b4"}}]}] BACKPORT--> Co-authored-by: Kyle Pollich <kyle.pollich@elastic.co> |
||
|
Kibana Machine
|
74f6bcef63
|
[8.18] [Navigation] Add stack monitoring to Elasticsearch sidebar (#210139) (#211137)
# Backport This will backport the following commits from `main` to `8.18`: - [[Navigation] Add stack monitoring to Elasticsearch sidebar (#210139)](https://github.com/elastic/kibana/pull/210139) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Krzysztof Kowalczyk","email":"krzysztof.kowalczyk@elastic.co"},"sourceCommit":{"committedDate":"2025-02-10T16:22:49Z","message":"[Navigation] Add stack monitoring to Elasticsearch sidebar (#210139)\n\n## Summary\r\n\r\nThis PR adds `Stack Monitoring` to the side navigation. \r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"9dc67bfd8836e8d3a2f0480d997b11d9e7e9106f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","release_note:skip","v9.0.0","Team:Search","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Navigation] Add stack monitoring to Elasticsearch sidebar","number":210139,"url":"https://github.com/elastic/kibana/pull/210139","mergeCommit":{"message":"[Navigation] Add stack monitoring to Elasticsearch sidebar (#210139)\n\n## Summary\r\n\r\nThis PR adds `Stack Monitoring` to the side navigation. \r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"9dc67bfd8836e8d3a2f0480d997b11d9e7e9106f"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"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/210139","number":210139,"mergeCommit":{"message":"[Navigation] Add stack monitoring to Elasticsearch sidebar (#210139)\n\n## Summary\r\n\r\nThis PR adds `Stack Monitoring` to the side navigation. \r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"9dc67bfd8836e8d3a2f0480d997b11d9e7e9106f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Krzysztof Kowalczyk <krzysztof.kowalczyk@elastic.co> |
||
|
Kibana Machine
|
3af4fe9a68
|
[8.18] [Navigation] Add stack monitoring to Security sidebar (#210203) (#211128)
# Backport This will backport the following commits from `main` to `8.18`: - [[Navigation] Add stack monitoring to Security sidebar (#210203)](https://github.com/elastic/kibana/pull/210203) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Krzysztof Kowalczyk","email":"krzysztof.kowalczyk@elastic.co"},"sourceCommit":{"committedDate":"2025-02-10T14:28:17Z","message":"[Navigation] Add stack monitoring to Security sidebar (#210203)\n\n## Summary\r\nThis PR adds Stack Monitoring to the side navigation.\r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"96381335e41d177f9851cc66eb9c5f7ec7d19d99","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","release_note:skip","v9.0.0","Team:Threat Hunting","Team: SecuritySolution","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Navigation] Add stack monitoring to Security sidebar","number":210203,"url":"https://github.com/elastic/kibana/pull/210203","mergeCommit":{"message":"[Navigation] Add stack monitoring to Security sidebar (#210203)\n\n## Summary\r\nThis PR adds Stack Monitoring to the side navigation.\r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"96381335e41d177f9851cc66eb9c5f7ec7d19d99"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"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/210203","number":210203,"mergeCommit":{"message":"[Navigation] Add stack monitoring to Security sidebar (#210203)\n\n## Summary\r\nThis PR adds Stack Monitoring to the side navigation.\r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"96381335e41d177f9851cc66eb9c5f7ec7d19d99"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Krzysztof Kowalczyk <krzysztof.kowalczyk@elastic.co> |
||
|
Kibana Machine
|
3c729096e4
|
[8.18] [Navigation] Add stack monitoring to Observability sidebar (#210140) (#211133)
# Backport This will backport the following commits from `main` to `8.18`: - [[Navigation] Add stack monitoring to Observability sidebar (#210140)](https://github.com/elastic/kibana/pull/210140) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Krzysztof Kowalczyk","email":"krzysztof.kowalczyk@elastic.co"},"sourceCommit":{"committedDate":"2025-02-10T14:29:27Z","message":"[Navigation] Add stack monitoring to Observability sidebar (#210140)\n\n## Summary\r\n\r\nThis PR adds `Stack Monitoring` to the side navigation. \r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"72265c026b875dd6dcefb07481784afd19f9347d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","release_note:skip","v9.0.0","Team:obs-ux-management","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Navigation] Add stack monitoring to Observability sidebar","number":210140,"url":"https://github.com/elastic/kibana/pull/210140","mergeCommit":{"message":"[Navigation] Add stack monitoring to Observability sidebar (#210140)\n\n## Summary\r\n\r\nThis PR adds `Stack Monitoring` to the side navigation. \r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"72265c026b875dd6dcefb07481784afd19f9347d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"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/210140","number":210140,"mergeCommit":{"message":"[Navigation] Add stack monitoring to Observability sidebar (#210140)\n\n## Summary\r\n\r\nThis PR adds `Stack Monitoring` to the side navigation. \r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"72265c026b875dd6dcefb07481784afd19f9347d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Krzysztof Kowalczyk <krzysztof.kowalczyk@elastic.co> |
||
|
Kibana Machine
|
d2a5735822
|
[8.18] [Inference] Updating link text for model_id (#211087) (#211110)
# Backport This will backport the following commits from `main` to `8.18`: - [[Inference] Updating link text for model_id (#211087)](https://github.com/elastic/kibana/pull/211087) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Samiul Monir","email":"150824886+Samiul-TheSoccerFan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-13T22:05:42Z","message":"[Inference] Updating link text for model_id (#211087)\n\n## Summary\r\n\r\nUpdating link text for `model_field` field to have `Learn more.` when\r\nthe provider is Elasticsearch.\r\n\r\n### screenshots:\r\n\r\n#### Elasticsearch provider\r\n\r\n\r\n#### Other providers\r\n\r\n\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- [X] 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/src/platform/packages/shared/kbn-i18n/README.md)\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":"84fdbcba62206dd010086ae1ec590d6d0f5d16e5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Inference] Updating link text for model_id","number":211087,"url":"https://github.com/elastic/kibana/pull/211087","mergeCommit":{"message":"[Inference] Updating link text for model_id (#211087)\n\n## Summary\r\n\r\nUpdating link text for `model_field` field to have `Learn more.` when\r\nthe provider is Elasticsearch.\r\n\r\n### screenshots:\r\n\r\n#### Elasticsearch provider\r\n\r\n\r\n#### Other providers\r\n\r\n\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- [X] 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/src/platform/packages/shared/kbn-i18n/README.md)\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":"84fdbcba62206dd010086ae1ec590d6d0f5d16e5"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"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/211087","number":211087,"mergeCommit":{"message":"[Inference] Updating link text for model_id (#211087)\n\n## Summary\r\n\r\nUpdating link text for `model_field` field to have `Learn more.` when\r\nthe provider is Elasticsearch.\r\n\r\n### screenshots:\r\n\r\n#### Elasticsearch provider\r\n\r\n\r\n#### Other providers\r\n\r\n\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- [X] 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/src/platform/packages/shared/kbn-i18n/README.md)\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":"84fdbcba62206dd010086ae1ec590d6d0f5d16e5"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Samiul Monir <150824886+Samiul-TheSoccerFan@users.noreply.github.com> |
||
seanrathier
|
fbd05120da
|
[8.18] [Cloud Security] fix setupTechnology GCP credential type swapping (#210668) (#211089)
# Backport This will backport the following commits from `main` to `8.18`: - [[Cloud Security] fix setupTechnology GCP credential type swapping (#210668)](https://github.com/elastic/kibana/pull/210668) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"seanrathier","email":"sean.rathier@gmail.com"},"sourceCommit":{"committedDate":"2025-02-13T19:06:37Z","message":"[Cloud Security] fix setupTechnology GCP credential type swapping (#210668)","sha":"4fe72b62b114d9b12f581ac4938e133eb869529f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Cloud Security","backport:prev-minor","v9.1.0"],"title":"[Cloud Security] fix setupTechnology GCP credential type swapping","number":210668,"url":"https://github.com/elastic/kibana/pull/210668","mergeCommit":{"message":"[Cloud Security] fix setupTechnology GCP credential type swapping (#210668)","sha":"4fe72b62b114d9b12f581ac4938e133eb869529f"}},"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/210668","number":210668,"mergeCommit":{"message":"[Cloud Security] fix setupTechnology GCP credential type swapping (#210668)","sha":"4fe72b62b114d9b12f581ac4938e133eb869529f"}},{"url":"https://github.com/elastic/kibana/pull/211082","number":211082,"branch":"9.0","state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
4d64ea4130
|
[8.18] [Links] Fix link settings not persisting (#211041) (#211103)
# Backport This will backport the following commits from `main` to `8.18`: - [[Links] Fix link settings not persisting (#211041)](https://github.com/elastic/kibana/pull/211041) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/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\n |
||
|
Kibana Machine
|
51b5251f7b
|
[8.18] [Security Solution][Network details] add ability to show full network flyout from preview (#211065) (#211099)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][Network details] add ability to show full network flyout from preview (#211065)](https://github.com/elastic/kibana/pull/211065) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T20:54:34Z","message":"[Security Solution][Network details] add ability to show full network flyout from preview (#211065)\n\n## Summary\r\n\r\nThis PR is a follow up of [this\r\nPR](https://github.com/elastic/kibana/pull/187870) that replaced the old\r\nnetwork/ip flyout with a new panel for the expandable flyout. Since then\r\nwe improved the UI or preview and added the ability to jump to a full\r\nflyout from its preview.\r\n\r\nThis PR fixes the issues where users could not navigate to the full\r\ndetails network/ip flyout from a preview. This functionality already\r\nexists for the alert, event, host and user flyouts. The PR adds a new\r\nfooter to the network/ip flyout - only shown in preview mode - that\r\nallows users to navigate to the full detail network/ip flyout.\r\n\r\n| Old behavior | New behavior |\r\n| ------------- | ------------- |\r\n| \r\n| \r\n|\r\n\r\nThe user has the ability to navigate to the full detail flyout:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/4c809e5d-0b59-4498-9966-0133d139233b\r\n\r\n### Checklist\r\n\r\n- [x] 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/src/platform/packages/shared/kbn-i18n/README.md)\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":"96b4f8442e29f3e2aca919e9552c479ea0811393","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","backport:version","v8.18.0","v9.1.0"],"title":"[Security Solution][Network details] add ability to show full network flyout from preview","number":211065,"url":"https://github.com/elastic/kibana/pull/211065","mergeCommit":{"message":"[Security Solution][Network details] add ability to show full network flyout from preview (#211065)\n\n## Summary\r\n\r\nThis PR is a follow up of [this\r\nPR](https://github.com/elastic/kibana/pull/187870) that replaced the old\r\nnetwork/ip flyout with a new panel for the expandable flyout. Since then\r\nwe improved the UI or preview and added the ability to jump to a full\r\nflyout from its preview.\r\n\r\nThis PR fixes the issues where users could not navigate to the full\r\ndetails network/ip flyout from a preview. This functionality already\r\nexists for the alert, event, host and user flyouts. The PR adds a new\r\nfooter to the network/ip flyout - only shown in preview mode - that\r\nallows users to navigate to the full detail network/ip flyout.\r\n\r\n| Old behavior | New behavior |\r\n| ------------- | ------------- |\r\n| \r\n| \r\n|\r\n\r\nThe user has the ability to navigate to the full detail flyout:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/4c809e5d-0b59-4498-9966-0133d139233b\r\n\r\n### Checklist\r\n\r\n- [x] 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/src/platform/packages/shared/kbn-i18n/README.md)\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":"96b4f8442e29f3e2aca919e9552c479ea0811393"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"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/211065","number":211065,"mergeCommit":{"message":"[Security Solution][Network details] add ability to show full network flyout from preview (#211065)\n\n## Summary\r\n\r\nThis PR is a follow up of [this\r\nPR](https://github.com/elastic/kibana/pull/187870) that replaced the old\r\nnetwork/ip flyout with a new panel for the expandable flyout. Since then\r\nwe improved the UI or preview and added the ability to jump to a full\r\nflyout from its preview.\r\n\r\nThis PR fixes the issues where users could not navigate to the full\r\ndetails network/ip flyout from a preview. This functionality already\r\nexists for the alert, event, host and user flyouts. The PR adds a new\r\nfooter to the network/ip flyout - only shown in preview mode - that\r\nallows users to navigate to the full detail network/ip flyout.\r\n\r\n| Old behavior | New behavior |\r\n| ------------- | ------------- |\r\n| \r\n| \r\n|\r\n\r\nThe user has the ability to navigate to the full detail flyout:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/4c809e5d-0b59-4498-9966-0133d139233b\r\n\r\n### Checklist\r\n\r\n- [x] 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/src/platform/packages/shared/kbn-i18n/README.md)\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":"96b4f8442e29f3e2aca919e9552c479ea0811393"}}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co> |
||
|
Kibana Machine
|
13b3983116
|
[8.18] [Rules migration][Integration test] Create migration API (#11232) (#210999) (#211083)
# Backport This will backport the following commits from `main` to `8.18`: - [[Rules migration][Integration test] Create migration API (#11232) (#210999)](https://github.com/elastic/kibana/pull/210999) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T19:20:06Z","message":"[Rules migration][Integration test] Create migration API (#11232) (#210999)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations CREATE API (route:\r\n`/internal/siem_migrations/rules/{migration_id?}`) integration test:\r\n* Create migration with provided ID\r\n* Create migration without provided ID\r\n* Create migration with rules that have resources\r\n* Error handling (\"no content\") when no rules provided\r\n\r\nAlso, as part of this PR, I addressed this comment to my previous\r\nchanges\r\nhttps://github.com/elastic/kibana/pull/210867#discussion_r1954344990","sha":"44fdf81bbec5c053ebccfbdbb062d39de0d7358c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team: SecuritySolution","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Rules migration][Integration test] Create migration API (#11232)","number":210999,"url":"https://github.com/elastic/kibana/pull/210999","mergeCommit":{"message":"[Rules migration][Integration test] Create migration API (#11232) (#210999)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations CREATE API (route:\r\n`/internal/siem_migrations/rules/{migration_id?}`) integration test:\r\n* Create migration with provided ID\r\n* Create migration without provided ID\r\n* Create migration with rules that have resources\r\n* Error handling (\"no content\") when no rules provided\r\n\r\nAlso, as part of this PR, I addressed this comment to my previous\r\nchanges\r\nhttps://github.com/elastic/kibana/pull/210867#discussion_r1954344990","sha":"44fdf81bbec5c053ebccfbdbb062d39de0d7358c"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"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/210999","number":210999,"mergeCommit":{"message":"[Rules migration][Integration test] Create migration API (#11232) (#210999)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations CREATE API (route:\r\n`/internal/siem_migrations/rules/{migration_id?}`) integration test:\r\n* Create migration with provided ID\r\n* Create migration without provided ID\r\n* Create migration with rules that have resources\r\n* Error handling (\"no content\") when no rules provided\r\n\r\nAlso, as part of this PR, I addressed this comment to my previous\r\nchanges\r\nhttps://github.com/elastic/kibana/pull/210867#discussion_r1954344990","sha":"44fdf81bbec5c053ebccfbdbb062d39de0d7358c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
f34b73a969
|
[8.18] [SecuritySolution] Network page crashes after interacting with map (#206773) (#211078)
# Backport This will backport the following commits from `main` to `8.18`: - [[SecuritySolution] Network page crashes after interacting with map (#206773)](https://github.com/elastic/kibana/pull/206773) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Angela Chuang","email":"6295984+angorayc@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-13T18:57:07Z","message":"[SecuritySolution] Network page crashes after interacting with map (#206773)\n\n## Summary\r\n\r\nIssues and steps to reproduce:\r\n |
||
Mark J. Hoy
|
6953738701
|
[8.18] [8.x] Add Pre-8.x Enterprise Search Index Incompatibility Deprecations (#210688) (#211077)
# Backport This will backport the following commits from `8.x` to `8.18`: - [[8.x] Add Pre-8.x Enterprise Search Index Incompatibility Deprecations (#210688)](https://github.com/elastic/kibana/pull/210688) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mark J. Hoy","email":"mark.hoy@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T18:21:48Z","message":"[8.x] Add Pre-8.x Enterprise Search Index Incompatibility Deprecations (#210688)\n\n## Summary\r\n\r\nAdds deprecations for the Kibana Upgrade Assistant if Enterprise Search\r\nindices from pre version 8.x are found. These indices are not compatible\r\nto upgrade to 9.x, so they must be set to read only or deleted.\r\n\r\nThe deprecations call out the specific indices, and offers a \"quick\r\nresolve\" button to set the affected indices to read only.\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- [x] 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/src/platform/packages/shared/kbn-i18n/README.md)\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] 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- [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)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"271e40e9753417bb083748017aa7fa528fc34510","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Upgrade Assistant","Team:EnterpriseSearch","v8.18.0","v8.19.0","backport:8.18"],"title":"[8.x] Add Pre-8.x Enterprise Search Index Incompatibility Deprecations","number":210688,"url":"https://github.com/elastic/kibana/pull/210688","mergeCommit":{"message":"[8.x] Add Pre-8.x Enterprise Search Index Incompatibility Deprecations (#210688)\n\n## Summary\r\n\r\nAdds deprecations for the Kibana Upgrade Assistant if Enterprise Search\r\nindices from pre version 8.x are found. These indices are not compatible\r\nto upgrade to 9.x, so they must be set to read only or deleted.\r\n\r\nThe deprecations call out the specific indices, and offers a \"quick\r\nresolve\" button to set the affected indices to read only.\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- [x] 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/src/platform/packages/shared/kbn-i18n/README.md)\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] 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- [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)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"271e40e9753417bb083748017aa7fa528fc34510"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
d02a02dff0
|
[8.18] [Security Solution][SIEM migrations] Use cloud onboarding config (#210921) (#211074)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][SIEM migrations] Use cloud onboarding config (#210921)](https://github.com/elastic/kibana/pull/210921) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sergi Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T18:28:22Z","message":"[Security Solution][SIEM migrations] Use cloud onboarding config (#210921)\n\n## Summary\r\n\r\nThis PR retrieves the Cloud onboarding data to pre-select the SIEM\r\nmigration topic in the onboarding hub when necessary.\r\nThe Cloud logic was implemented\r\n[here](https://github.com/elastic/kibana/pull/204129)\r\n\r\n<img width=\"1364\" alt=\"Captura de pantalla 2025-02-13 a les 11 50 31\"\r\nsrc=\"https://github.com/user-attachments/assets/28707314-da9b-439a-baa9-f6fb53c170fa\"\r\n/>","sha":"789986ce4846f8a32e40c00d52268a1beaa6231e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution][SIEM migrations] Use cloud onboarding config","number":210921,"url":"https://github.com/elastic/kibana/pull/210921","mergeCommit":{"message":"[Security Solution][SIEM migrations] Use cloud onboarding config (#210921)\n\n## Summary\r\n\r\nThis PR retrieves the Cloud onboarding data to pre-select the SIEM\r\nmigration topic in the onboarding hub when necessary.\r\nThe Cloud logic was implemented\r\n[here](https://github.com/elastic/kibana/pull/204129)\r\n\r\n<img width=\"1364\" alt=\"Captura de pantalla 2025-02-13 a les 11 50 31\"\r\nsrc=\"https://github.com/user-attachments/assets/28707314-da9b-439a-baa9-f6fb53c170fa\"\r\n/>","sha":"789986ce4846f8a32e40c00d52268a1beaa6231e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"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/210921","number":210921,"mergeCommit":{"message":"[Security Solution][SIEM migrations] Use cloud onboarding config (#210921)\n\n## Summary\r\n\r\nThis PR retrieves the Cloud onboarding data to pre-select the SIEM\r\nmigration topic in the onboarding hub when necessary.\r\nThe Cloud logic was implemented\r\n[here](https://github.com/elastic/kibana/pull/204129)\r\n\r\n<img width=\"1364\" alt=\"Captura de pantalla 2025-02-13 a les 11 50 31\"\r\nsrc=\"https://github.com/user-attachments/assets/28707314-da9b-439a-baa9-f6fb53c170fa\"\r\n/>","sha":"789986ce4846f8a32e40c00d52268a1beaa6231e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co> |
||
|
Kibana Machine
|
78bf483e60
|
[8.18] [Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922) (#211008)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922)](https://github.com/elastic/kibana/pull/210922) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Devin W. Hurley","email":"devin.hurley@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T13:37:37Z","message":"[Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922)\n\n## Summary\n\nDisables sorting ip range values in a value list until this bug is\nfixed in elasticsearch.\n\nrelated: https://github.com/elastic/elasticsearch/issues/122358","sha":"18ef744a9c3bf5b5eff585cbddcc4cb34eab9b8f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","review","release_note:fix","v9.0.0","sdh-linked","Team:Detection Engine","backport:version","v8.18.0","v9.1.0","v8.17.3"],"title":"[Security Solution] [Detections] Disables sorting ip ranges in value list modal","number":210922,"url":"https://github.com/elastic/kibana/pull/210922","mergeCommit":{"message":"[Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922)\n\n## Summary\n\nDisables sorting ip range values in a value list until this bug is\nfixed in elasticsearch.\n\nrelated: https://github.com/elastic/elasticsearch/issues/122358","sha":"18ef744a9c3bf5b5eff585cbddcc4cb34eab9b8f"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","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":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210922","number":210922,"mergeCommit":{"message":"[Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922)\n\n## Summary\n\nDisables sorting ip range values in a value list until this bug is\nfixed in elasticsearch.\n\nrelated: https://github.com/elastic/elasticsearch/issues/122358","sha":"18ef744a9c3bf5b5eff585cbddcc4cb34eab9b8f"}},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Devin W. Hurley <devin.hurley@elastic.co> |
||
|
Kibana Machine
|
469d8d68c8
|
[8.18] [Security Solution] Update entity store copies (#210991) (#211032)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Update entity store copies (#210991)](https://github.com/elastic/kibana/pull/210991) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T15:42:09Z","message":"[Security Solution] Update entity store copies (#210991)\n\n## Summary\n\n* Update `Initializing entity store` to `Configuring Entity Store`\n* Update `Your entity store is currently empty. Add information...` to\n`Add information...`\n\n<img width=\"400\"\nsrc=\"https://github.com/user-attachments/assets/f64bf5de-bb42-4675-a816-6202dca4bb80\"/>\n<img width=\"400\"\nsrc=\"https://github.com/user-attachments/assets/cf1ea4c0-416d-408a-a166-b85c3e57135a\"/>","sha":"fe96fe2dbc040e8ab2bcc10995d71f9bc29571cb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team: SecuritySolution","Theme: entity_analytics","Feature:Entity Analytics","Team:Entity Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Update entity store copies","number":210991,"url":"https://github.com/elastic/kibana/pull/210991","mergeCommit":{"message":"[Security Solution] Update entity store copies (#210991)\n\n## Summary\n\n* Update `Initializing entity store` to `Configuring Entity Store`\n* Update `Your entity store is currently empty. Add information...` to\n`Add information...`\n\n<img width=\"400\"\nsrc=\"https://github.com/user-attachments/assets/f64bf5de-bb42-4675-a816-6202dca4bb80\"/>\n<img width=\"400\"\nsrc=\"https://github.com/user-attachments/assets/cf1ea4c0-416d-408a-a166-b85c3e57135a\"/>","sha":"fe96fe2dbc040e8ab2bcc10995d71f9bc29571cb"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"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/210991","number":210991,"mergeCommit":{"message":"[Security Solution] Update entity store copies (#210991)\n\n## Summary\n\n* Update `Initializing entity store` to `Configuring Entity Store`\n* Update `Your entity store is currently empty. Add information...` to\n`Add information...`\n\n<img width=\"400\"\nsrc=\"https://github.com/user-attachments/assets/f64bf5de-bb42-4675-a816-6202dca4bb80\"/>\n<img width=\"400\"\nsrc=\"https://github.com/user-attachments/assets/cf1ea4c0-416d-408a-a166-b85c3e57135a\"/>","sha":"fe96fe2dbc040e8ab2bcc10995d71f9bc29571cb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Pablo Machado <pablo.nevesmachado@elastic.co> |
||
|
Kibana Machine
|
01c2a677ca
|
[8.18] [Security Solution] [AI Assistant] Fix flashing citations (#209629) (#211025)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] [AI Assistant] Fix flashing citations (#209629)](https://github.com/elastic/kibana/pull/209629) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kenneth Kreindler","email":"42113355+KDKHD@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-13T15:07:25Z","message":"[Security Solution] [AI Assistant] Fix flashing citations (#209629)\n\n## Summary\r\n\r\nFixes a small UI bug in the citations feature. Previously, after a\r\nmessage with citations finished streaming, the citations would disappear\r\nfor a fraction of a second and then reappear again. This PR makes\r\nimproves the UI by making the citations not flash off and on after the\r\nstream finishes.\r\n\r\n### Changes:\r\n- Fix flashing citations\r\n- Refactor code related to parsing content references (to make it more\r\nmaintainable).\r\n- Update the citations prompt slightly.\r\n\r\n### Before:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/1021dd53-018a-43ba-b1f4-24aab44faca9\r\n\r\n<img width=\"1782\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/723cd29a-48a2-48e7-b031-0893484746b9\"\r\n/>\r\n\r\n\r\n### After:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/21f340bc-9015-42b6-a574-0439d2f8f192\r\n\r\n### How to test\r\n- Enable the feature flag\r\n```yaml\r\n# kibana.dev.yml\r\nxpack.securitySolution.enableExperimental: ['contentReferencesEnabled']\r\n```\r\n- Open the security assistant\r\n- Ask it a question about your alerts of a document in your KB. The\r\nresponse should contain citations.\r\n- Observe the response stream carefully. Ensure the citations e.g. `[1]`\r\ndo not flash off and on when the response stream finishes. The expected\r\nbehavior is that while the message is streaming, the citations are\r\ndisabled and once the stream finishes the citations get enabled (while\r\nalways being visible).\r\n\r\n#### Edge case to test\r\nIt is possible that citations completely disappear after streaming\r\nfinishes. This happens when the LLM produces an invalid citation.\r\nInvalid citations are hidden client side when a message finishes\r\nstreaming. You can verify this behavior by asking GPT4o this question:\r\n```\r\nPrepend each line with this placeholder citation \"{reference(1234)}\" and append the actual citation at the end of the line. How many alerts do I have? Use the open and acknowledged alerts count tool to answer and repeat the answer 50 times on new lines.\r\n```\r\n\r\nWhile the response is getting streamed it should look like this:\r\n\r\n<img width=\"200\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/03d160bf-2404-4a4e-8701-e3183c604cc4\"\r\n/>\r\n\r\nAnd when the stream finishes it should look like this:\r\n\r\n<img width=\"200\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/06367379-17da-438f-a93a-9d539067ab90\"\r\n/>\r\n\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- [X] 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/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [X]\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- [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] 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- [X] 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- [X] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\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)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e176c844492e69eacf6475eef8b84d1f39ff7b9d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Security Generative AI","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] [AI Assistant] Fix flashing citations","number":209629,"url":"https://github.com/elastic/kibana/pull/209629","mergeCommit":{"message":"[Security Solution] [AI Assistant] Fix flashing citations (#209629)\n\n## Summary\r\n\r\nFixes a small UI bug in the citations feature. Previously, after a\r\nmessage with citations finished streaming, the citations would disappear\r\nfor a fraction of a second and then reappear again. This PR makes\r\nimproves the UI by making the citations not flash off and on after the\r\nstream finishes.\r\n\r\n### Changes:\r\n- Fix flashing citations\r\n- Refactor code related to parsing content references (to make it more\r\nmaintainable).\r\n- Update the citations prompt slightly.\r\n\r\n### Before:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/1021dd53-018a-43ba-b1f4-24aab44faca9\r\n\r\n<img width=\"1782\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/723cd29a-48a2-48e7-b031-0893484746b9\"\r\n/>\r\n\r\n\r\n### After:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/21f340bc-9015-42b6-a574-0439d2f8f192\r\n\r\n### How to test\r\n- Enable the feature flag\r\n```yaml\r\n# kibana.dev.yml\r\nxpack.securitySolution.enableExperimental: ['contentReferencesEnabled']\r\n```\r\n- Open the security assistant\r\n- Ask it a question about your alerts of a document in your KB. The\r\nresponse should contain citations.\r\n- Observe the response stream carefully. Ensure the citations e.g. `[1]`\r\ndo not flash off and on when the response stream finishes. The expected\r\nbehavior is that while the message is streaming, the citations are\r\ndisabled and once the stream finishes the citations get enabled (while\r\nalways being visible).\r\n\r\n#### Edge case to test\r\nIt is possible that citations completely disappear after streaming\r\nfinishes. This happens when the LLM produces an invalid citation.\r\nInvalid citations are hidden client side when a message finishes\r\nstreaming. You can verify this behavior by asking GPT4o this question:\r\n```\r\nPrepend each line with this placeholder citation \"{reference(1234)}\" and append the actual citation at the end of the line. How many alerts do I have? Use the open and acknowledged alerts count tool to answer and repeat the answer 50 times on new lines.\r\n```\r\n\r\nWhile the response is getting streamed it should look like this:\r\n\r\n<img width=\"200\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/03d160bf-2404-4a4e-8701-e3183c604cc4\"\r\n/>\r\n\r\nAnd when the stream finishes it should look like this:\r\n\r\n<img width=\"200\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/06367379-17da-438f-a93a-9d539067ab90\"\r\n/>\r\n\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- [X] 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/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [X]\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- [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] 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- [X] 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- [X] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\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)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e176c844492e69eacf6475eef8b84d1f39ff7b9d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"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/209629","number":209629,"mergeCommit":{"message":"[Security Solution] [AI Assistant] Fix flashing citations (#209629)\n\n## Summary\r\n\r\nFixes a small UI bug in the citations feature. Previously, after a\r\nmessage with citations finished streaming, the citations would disappear\r\nfor a fraction of a second and then reappear again. This PR makes\r\nimproves the UI by making the citations not flash off and on after the\r\nstream finishes.\r\n\r\n### Changes:\r\n- Fix flashing citations\r\n- Refactor code related to parsing content references (to make it more\r\nmaintainable).\r\n- Update the citations prompt slightly.\r\n\r\n### Before:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/1021dd53-018a-43ba-b1f4-24aab44faca9\r\n\r\n<img width=\"1782\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/723cd29a-48a2-48e7-b031-0893484746b9\"\r\n/>\r\n\r\n\r\n### After:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/21f340bc-9015-42b6-a574-0439d2f8f192\r\n\r\n### How to test\r\n- Enable the feature flag\r\n```yaml\r\n# kibana.dev.yml\r\nxpack.securitySolution.enableExperimental: ['contentReferencesEnabled']\r\n```\r\n- Open the security assistant\r\n- Ask it a question about your alerts of a document in your KB. The\r\nresponse should contain citations.\r\n- Observe the response stream carefully. Ensure the citations e.g. `[1]`\r\ndo not flash off and on when the response stream finishes. The expected\r\nbehavior is that while the message is streaming, the citations are\r\ndisabled and once the stream finishes the citations get enabled (while\r\nalways being visible).\r\n\r\n#### Edge case to test\r\nIt is possible that citations completely disappear after streaming\r\nfinishes. This happens when the LLM produces an invalid citation.\r\nInvalid citations are hidden client side when a message finishes\r\nstreaming. You can verify this behavior by asking GPT4o this question:\r\n```\r\nPrepend each line with this placeholder citation \"{reference(1234)}\" and append the actual citation at the end of the line. How many alerts do I have? Use the open and acknowledged alerts count tool to answer and repeat the answer 50 times on new lines.\r\n```\r\n\r\nWhile the response is getting streamed it should look like this:\r\n\r\n<img width=\"200\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/03d160bf-2404-4a4e-8701-e3183c604cc4\"\r\n/>\r\n\r\nAnd when the stream finishes it should look like this:\r\n\r\n<img width=\"200\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/06367379-17da-438f-a93a-9d539067ab90\"\r\n/>\r\n\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- [X] 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/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [X]\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- [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] 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- [X] 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- [X] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\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)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e176c844492e69eacf6475eef8b84d1f39ff7b9d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Kenneth Kreindler <42113355+KDKHD@users.noreply.github.com> |
||
|
Bharat Pasupula
|
340281df74
|
[8.18] [Automatic Import] Fix package name validation (#210770) (#210809)
# Backport This will backport the following commits from `main` to `8.18`: - [[Automatic Import] Fix package name validation (#210770)](https://github.com/elastic/kibana/pull/210770) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T11:48:20Z","message":"[Automatic Import] Fix package name validation (#210770)\n\n## Release Note\r\n\r\nFix package name validation on Datastream page.\r\n\r\n## Summary\r\n\r\nCloses - #199893\r\n\r\nIf the package name starts with a number [ Only number , alphabet ,\r\nunderscore are allowed ] then some of the script processors in the\r\npipeline fail with dot annotation since the fields are formed like\r\n`ctx.123_abc.something` which fails with `Illegal Argument Exception` in\r\nscript processor.\r\n\r\nHence the package name has additional validation on Data stream page to\r\nrestrict it to start with an alphabet or underscore instead.\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- [x] 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/src/platform/packages/shared/kbn-i18n/README.md)\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":"9c87ded7d1e1f5c9fe8b3accce1beda01268d5cf","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport","v9.1.0"],"title":"[Automatic Import] Fix package name validation","number":210770,"url":"https://github.com/elastic/kibana/pull/210770","mergeCommit":{"message":"[Automatic Import] Fix package name validation (#210770)\n\n## Release Note\r\n\r\nFix package name validation on Datastream page.\r\n\r\n## Summary\r\n\r\nCloses - #199893\r\n\r\nIf the package name starts with a number [ Only number , alphabet ,\r\nunderscore are allowed ] then some of the script processors in the\r\npipeline fail with dot annotation since the fields are formed like\r\n`ctx.123_abc.something` which fails with `Illegal Argument Exception` in\r\nscript processor.\r\n\r\nHence the package name has additional validation on Data stream page to\r\nrestrict it to start with an alphabet or underscore instead.\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- [x] 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/src/platform/packages/shared/kbn-i18n/README.md)\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":"9c87ded7d1e1f5c9fe8b3accce1beda01268d5cf"}},"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/210770","number":210770,"mergeCommit":{"message":"[Automatic Import] Fix package name validation (#210770)\n\n## Release Note\r\n\r\nFix package name validation on Datastream page.\r\n\r\n## Summary\r\n\r\nCloses - #199893\r\n\r\nIf the package name starts with a number [ Only number , alphabet ,\r\nunderscore are allowed ] then some of the script processors in the\r\npipeline fail with dot annotation since the fields are formed like\r\n`ctx.123_abc.something` which fails with `Illegal Argument Exception` in\r\nscript processor.\r\n\r\nHence the package name has additional validation on Data stream page to\r\nrestrict it to start with an alphabet or underscore instead.\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- [x] 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/src/platform/packages/shared/kbn-i18n/README.md)\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":"9c87ded7d1e1f5c9fe8b3accce1beda01268d5cf"}},{"url":"https://github.com/elastic/kibana/pull/210801","number":210801,"branch":"9.0","state":"OPEN"}]}] BACKPORT--> |
||
Dima Arnautov
|
a1c53e2a2c
|
[8.18] [ES|QL] Fix WHERE autocomplete with MATCH before LIMIT (#210607) (#211001)
# Backport This will backport the following commits from `main` to `8.18`: - [[ES|QL] Fix WHERE autocomplete with MATCH before LIMIT (#210607)](https://github.com/elastic/kibana/pull/210607) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2025-02-12T17:38:45Z","message":"[ES|QL] Fix WHERE autocomplete with MATCH before LIMIT (#210607)\n\n## Summary\r\n\r\nRelated PR https://github.com/elastic/kibana/pull/199032\r\n\r\n\r\nFixes `WHERE` autocomplete with `MATCH` before `LIMIT`.\r\n\r\nThe previous check was filtering suggestions based on all present\r\ncommands, not just the previous one.\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":"1ccb6db350425f8cdfbacd6341a3e4defaba1bcb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Feature:ES|QL","Team:ESQL","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ES|QL] Fix WHERE autocomplete with MATCH before LIMIT","number":210607,"url":"https://github.com/elastic/kibana/pull/210607","mergeCommit":{"message":"[ES|QL] Fix WHERE autocomplete with MATCH before LIMIT (#210607)\n\n## Summary\r\n\r\nRelated PR https://github.com/elastic/kibana/pull/199032\r\n\r\n\r\nFixes `WHERE` autocomplete with `MATCH` before `LIMIT`.\r\n\r\nThe previous check was filtering suggestions based on all present\r\ncommands, not just the previous one.\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":"1ccb6db350425f8cdfbacd6341a3e4defaba1bcb"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"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/210607","number":210607,"mergeCommit":{"message":"[ES|QL] Fix WHERE autocomplete with MATCH before LIMIT (#210607)\n\n## Summary\r\n\r\nRelated PR https://github.com/elastic/kibana/pull/199032\r\n\r\n\r\nFixes `WHERE` autocomplete with `MATCH` before `LIMIT`.\r\n\r\nThe previous check was filtering suggestions based on all present\r\ncommands, not just the previous one.\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":"1ccb6db350425f8cdfbacd6341a3e4defaba1bcb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210901","number":210901,"state":"MERGED","mergeCommit":{"sha":"5eb5c66aa66fde123a14bc67368fb3259cdb3dfb","message":"[8.x] [ES|QL] Fix WHERE autocomplete with MATCH before LIMIT (#210607) (#210901)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[ES|QL] Fix WHERE autocomplete with MATCH before LIMIT\n(#210607)](https://github.com/elastic/kibana/pull/210607)\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\":\"Dima\nArnautov\",\"email\":\"dmitrii.arnautov@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-12T17:38:45Z\",\"message\":\"[ES|QL]\nFix WHERE autocomplete with MATCH before LIMIT (#210607)\\n\\n##\nSummary\\r\\n\\r\\nRelated PR\nhttps://github.com/elastic/kibana/pull/199032\\r\\n\\r\\n\\r\\nFixes `WHERE`\nautocomplete with `MATCH` before `LIMIT`.\\r\\n\\r\\nThe previous check was\nfiltering suggestions based on all present\\r\\ncommands, not just the\nprevious one.\\r\\n\\r\\n### Checklist\\r\\n\\r\\n- [x] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common\nscenarios\",\"sha\":\"1ccb6db350425f8cdfbacd6341a3e4defaba1bcb\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"v9.0.0\",\"Feature:ES|QL\",\"Team:ESQL\",\"backport:version\",\"v9.1.0\",\"v8.19.0\"],\"title\":\"[ES|QL]\nFix WHERE autocomplete with MATCH before\nLIMIT\",\"number\":210607,\"url\":\"https://github.com/elastic/kibana/pull/210607\",\"mergeCommit\":{\"message\":\"[ES|QL]\nFix WHERE autocomplete with MATCH before LIMIT (#210607)\\n\\n##\nSummary\\r\\n\\r\\nRelated PR\nhttps://github.com/elastic/kibana/pull/199032\\r\\n\\r\\n\\r\\nFixes `WHERE`\nautocomplete with `MATCH` before `LIMIT`.\\r\\n\\r\\nThe previous check was\nfiltering suggestions based on all present\\r\\ncommands, not just the\nprevious one.\\r\\n\\r\\n### Checklist\\r\\n\\r\\n- [x] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common\nscenarios\",\"sha\":\"1ccb6db350425f8cdfbacd6341a3e4defaba1bcb\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\",\"8.x\"],\"targetPullRequestStates\":[{\"branch\":\"9.0\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/210607\",\"number\":210607,\"mergeCommit\":{\"message\":\"[ES|QL]\nFix WHERE autocomplete with MATCH before LIMIT (#210607)\\n\\n##\nSummary\\r\\n\\r\\nRelated PR\nhttps://github.com/elastic/kibana/pull/199032\\r\\n\\r\\n\\r\\nFixes `WHERE`\nautocomplete with `MATCH` before `LIMIT`.\\r\\n\\r\\nThe previous check was\nfiltering suggestions based on all present\\r\\ncommands, not just the\nprevious one.\\r\\n\\r\\n### Checklist\\r\\n\\r\\n- [x] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common\nscenarios\",\"sha\":\"1ccb6db350425f8cdfbacd6341a3e4defaba1bcb\"}},{\"branch\":\"8.x\",\"label\":\"v8.19.0\",\"branchLabelMappingKey\":\"^v8.19.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co>"}}]}] BACKPORT--> |
||
Yan Savitski
|
bd8318dcea
|
[8.18] [Search] Fix error page for workplace search (#211011)
## Summary Fix error page for workplace search **Before:** <img width="817" alt="image" src="https://github.com/user-attachments/assets/123e2fa2-0bc8-457f-9b00-43bb9686389d" /> **After:** <img width="2553" alt="image" src="https://github.com/user-attachments/assets/032d6198-feb6-43e4-a646-683c5e80603f" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) |
||
|
Karen Grigoryan
|
39b493c84f
|
[8.18] [Security Solution] [EUI Refresh] styled component migration Dashboards (#208731) (#210983)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] [EUI Refresh] styled component migration Dashboards (#208731)](https://github.com/elastic/kibana/pull/208731) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Agustina Nahir Ruidiaz","email":"61565784+agusruidiazgd@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T15:05:27Z","message":"[Security Solution] [EUI Refresh] styled component migration Dashboards (#208731)\n\n## Summary\r\n\r\nAddresses https://github.com/elastic/kibana/issues/206439\r\nThis PR migrates explore page from styled-components to @emotion/styled.\r\nIn the process I also convert the kbn/ui-theme json tokens to euiTheme\r\ncounterparts.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/6cdfbf15-9a77-488c-a0b9-42acc3fe1768\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"f92e50a4a1d9bdea781d1e0fb45b4f8560a27ab5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Explore","ci:cloud-deploy","backport:version","v8.18.0","EUI Visual Refresh","v9.1.0","v8.19.0"],"title":"[Security Solution] [EUI Refresh] styled component migration Dashboards","number":208731,"url":"https://github.com/elastic/kibana/pull/208731","mergeCommit":{"message":"[Security Solution] [EUI Refresh] styled component migration Dashboards (#208731)\n\n## Summary\r\n\r\nAddresses https://github.com/elastic/kibana/issues/206439\r\nThis PR migrates explore page from styled-components to @emotion/styled.\r\nIn the process I also convert the kbn/ui-theme json tokens to euiTheme\r\ncounterparts.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/6cdfbf15-9a77-488c-a0b9-42acc3fe1768\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"f92e50a4a1d9bdea781d1e0fb45b4f8560a27ab5"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210886","number":210886,"state":"OPEN"},{"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/208731","number":208731,"mergeCommit":{"message":"[Security Solution] [EUI Refresh] styled component migration Dashboards (#208731)\n\n## Summary\r\n\r\nAddresses https://github.com/elastic/kibana/issues/206439\r\nThis PR migrates explore page from styled-components to @emotion/styled.\r\nIn the process I also convert the kbn/ui-theme json tokens to euiTheme\r\ncounterparts.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/6cdfbf15-9a77-488c-a0b9-42acc3fe1768\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"f92e50a4a1d9bdea781d1e0fb45b4f8560a27ab5"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210967","number":210967,"state":"OPEN"}]}] BACKPORT--> Co-authored-by: Agustina Nahir Ruidiaz <61565784+agusruidiazgd@users.noreply.github.com> |
||
|
Angela Chuang
|
d756ddb2b8
|
[8.18] [SecuritySolution] Apply different color tokens for themes (#206254) (#210994)
# Backport This will backport the following commits from `main` to `8.18`: - [[SecuritySolution] Apply different color tokens for themes (#206254)](https://github.com/elastic/kibana/pull/206254) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Angela Chuang","email":"6295984+angorayc@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-10T18:54:47Z","message":"[SecuritySolution] Apply different color tokens for themes (#206254)\n\n## Summary\r\n\r\nPrevious changes applied same tokens for Borealis and Amsterdam:\r\nhttps://github.com/elastic/kibana/pull/204631#issuecomment-2573415425\r\n\r\nPR above causes color changes to the current theme, after discussing\r\nwith UX, we decide to maintain different color tokens until Borealis is\r\nlaunched. This PR should revert the color changed on Amsterdam by the\r\nprevious PR and only apply the new color for Borealis.\r\n\r\n| Current and Amsterdam | Borealis |\r\n|-------------------------|----------|\r\n|Source: Hard coded: `#d36186`|Source: `euiColorVis4` - `#EE72A6` |\r\n|Dest: Hard coded: `#9170b8` |Dest: `euiColorVis2` - `#61A2FF`|\r\n\r\n### Host IPs:\r\n\r\n| Current and Amsterdam | Borealis |\r\n|-------------------------|----------|\r\n|<img width=\"2560\" alt=\"host_IPs\"\r\nsrc=\"https://github.com/user-attachments/assets/c0f9f317-fb02-4c96-8422-c1d2484f4636\"\r\n/>|<img width=\"2560\" alt=\"host_bor_light\"\r\nsrc=\"https://github.com/user-attachments/assets/451d6604-1d7c-4a2e-82c3-74b2499852d2\"\r\n/>|\r\n|<img width=\"2558\" alt=\"host_IPs_dark\"\r\nsrc=\"https://github.com/user-attachments/assets/ac45a3ac-ecaf-46b6-91d9-68704d8639ee\"\r\n/>|<img width=\"2553\" alt=\"host_bor_dark\"\r\nsrc=\"https://github.com/user-attachments/assets/e34e56fd-8202-4a3c-80c1-996718320fd8\"\r\n/>|\r\n\r\n### Network IPs:\r\n\r\n| Current and Amsterdam | Borealis |\r\n|-------------------------|----------|\r\n|<img width=\"2557\" alt=\"network_IPs\"\r\nsrc=\"https://github.com/user-attachments/assets/0e0b33d9-55b7-41a5-8910-11b80e539398\"\r\n/>|<img width=\"2559\" alt=\"network_bor_light\"\r\nsrc=\"https://github.com/user-attachments/assets/f616b3ab-5032-4e69-b67e-cde39b88ea5f\"\r\n/>|\r\n|<img width=\"2558\" alt=\"host_IPs_dark\"\r\nsrc=\"https://github.com/user-attachments/assets/9613a49f-f0c6-4b63-aa56-c960fac175fc\"\r\n/>|<img width=\"2560\" alt=\"network_bor_dark\"\r\nsrc=\"https://github.com/user-attachments/assets/911f0509-43ea-428a-94d6-9ce01f5425ac\"\r\n/>|\r\n\r\n\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\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":"4ca57799b751e48d7657604ab04b50887e5b624c","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","v9.0.0","EUI Visual Refresh"],"number":206254,"url":"https://github.com/elastic/kibana/pull/206254","mergeCommit":{"message":"[SecuritySolution] Apply different color tokens for themes (#206254)\n\n## Summary\r\n\r\nPrevious changes applied same tokens for Borealis and Amsterdam:\r\nhttps://github.com/elastic/kibana/pull/204631#issuecomment-2573415425\r\n\r\nPR above causes color changes to the current theme, after discussing\r\nwith UX, we decide to maintain different color tokens until Borealis is\r\nlaunched. This PR should revert the color changed on Amsterdam by the\r\nprevious PR and only apply the new color for Borealis.\r\n\r\n| Current and Amsterdam | Borealis |\r\n|-------------------------|----------|\r\n|Source: Hard coded: `#d36186`|Source: `euiColorVis4` - `#EE72A6` |\r\n|Dest: Hard coded: `#9170b8` |Dest: `euiColorVis2` - `#61A2FF`|\r\n\r\n### Host IPs:\r\n\r\n| Current and Amsterdam | Borealis |\r\n|-------------------------|----------|\r\n|<img width=\"2560\" alt=\"host_IPs\"\r\nsrc=\"https://github.com/user-attachments/assets/c0f9f317-fb02-4c96-8422-c1d2484f4636\"\r\n/>|<img width=\"2560\" alt=\"host_bor_light\"\r\nsrc=\"https://github.com/user-attachments/assets/451d6604-1d7c-4a2e-82c3-74b2499852d2\"\r\n/>|\r\n|<img width=\"2558\" alt=\"host_IPs_dark\"\r\nsrc=\"https://github.com/user-attachments/assets/ac45a3ac-ecaf-46b6-91d9-68704d8639ee\"\r\n/>|<img width=\"2553\" alt=\"host_bor_dark\"\r\nsrc=\"https://github.com/user-attachments/assets/e34e56fd-8202-4a3c-80c1-996718320fd8\"\r\n/>|\r\n\r\n### Network IPs:\r\n\r\n| Current and Amsterdam | Borealis |\r\n|-------------------------|----------|\r\n|<img width=\"2557\" alt=\"network_IPs\"\r\nsrc=\"https://github.com/user-attachments/assets/0e0b33d9-55b7-41a5-8910-11b80e539398\"\r\n/>|<img width=\"2559\" alt=\"network_bor_light\"\r\nsrc=\"https://github.com/user-attachments/assets/f616b3ab-5032-4e69-b67e-cde39b88ea5f\"\r\n/>|\r\n|<img width=\"2558\" alt=\"host_IPs_dark\"\r\nsrc=\"https://github.com/user-attachments/assets/9613a49f-f0c6-4b63-aa56-c960fac175fc\"\r\n/>|<img width=\"2560\" alt=\"network_bor_dark\"\r\nsrc=\"https://github.com/user-attachments/assets/911f0509-43ea-428a-94d6-9ce01f5425ac\"\r\n/>|\r\n\r\n\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\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":"4ca57799b751e48d7657604ab04b50887e5b624c"}},"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/206254","number":206254,"mergeCommit":{"message":"[SecuritySolution] Apply different color tokens for themes (#206254)\n\n## Summary\r\n\r\nPrevious changes applied same tokens for Borealis and Amsterdam:\r\nhttps://github.com/elastic/kibana/pull/204631#issuecomment-2573415425\r\n\r\nPR above causes color changes to the current theme, after discussing\r\nwith UX, we decide to maintain different color tokens until Borealis is\r\nlaunched. This PR should revert the color changed on Amsterdam by the\r\nprevious PR and only apply the new color for Borealis.\r\n\r\n| Current and Amsterdam | Borealis |\r\n|-------------------------|----------|\r\n|Source: Hard coded: `#d36186`|Source: `euiColorVis4` - `#EE72A6` |\r\n|Dest: Hard coded: `#9170b8` |Dest: `euiColorVis2` - `#61A2FF`|\r\n\r\n### Host IPs:\r\n\r\n| Current and Amsterdam | Borealis |\r\n|-------------------------|----------|\r\n|<img width=\"2560\" alt=\"host_IPs\"\r\nsrc=\"https://github.com/user-attachments/assets/c0f9f317-fb02-4c96-8422-c1d2484f4636\"\r\n/>|<img width=\"2560\" alt=\"host_bor_light\"\r\nsrc=\"https://github.com/user-attachments/assets/451d6604-1d7c-4a2e-82c3-74b2499852d2\"\r\n/>|\r\n|<img width=\"2558\" alt=\"host_IPs_dark\"\r\nsrc=\"https://github.com/user-attachments/assets/ac45a3ac-ecaf-46b6-91d9-68704d8639ee\"\r\n/>|<img width=\"2553\" alt=\"host_bor_dark\"\r\nsrc=\"https://github.com/user-attachments/assets/e34e56fd-8202-4a3c-80c1-996718320fd8\"\r\n/>|\r\n\r\n### Network IPs:\r\n\r\n| Current and Amsterdam | Borealis |\r\n|-------------------------|----------|\r\n|<img width=\"2557\" alt=\"network_IPs\"\r\nsrc=\"https://github.com/user-attachments/assets/0e0b33d9-55b7-41a5-8910-11b80e539398\"\r\n/>|<img width=\"2559\" alt=\"network_bor_light\"\r\nsrc=\"https://github.com/user-attachments/assets/f616b3ab-5032-4e69-b67e-cde39b88ea5f\"\r\n/>|\r\n|<img width=\"2558\" alt=\"host_IPs_dark\"\r\nsrc=\"https://github.com/user-attachments/assets/9613a49f-f0c6-4b63-aa56-c960fac175fc\"\r\n/>|<img width=\"2560\" alt=\"network_bor_dark\"\r\nsrc=\"https://github.com/user-attachments/assets/911f0509-43ea-428a-94d6-9ce01f5425ac\"\r\n/>|\r\n\r\n\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\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":"4ca57799b751e48d7657604ab04b50887e5b624c"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
788df3671f
|
[8.18] [Rules migration][Integration test] Get migration rules API (#11232) (#210867) (#210996)
# Backport This will backport the following commits from `main` to `8.18`: - [[Rules migration][Integration test] Get migration rules API (#11232) (#210867)](https://github.com/elastic/kibana/pull/210867) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T12:44:08Z","message":"[Rules migration][Integration test] Get migration rules API (#11232) (#210867)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations GET API (route:\r\n`/internal/siem_migrations/rules/{migration_id}`) integration test:\r\n* Basic calls\r\n* Filtering\r\n* Sorting\r\n* Pagination","sha":"526ff0516e701ee1e1db8a248fe8f7c86587d257","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team: SecuritySolution","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Rules migration][Integration test] Get migration rules API (#11232)","number":210867,"url":"https://github.com/elastic/kibana/pull/210867","mergeCommit":{"message":"[Rules migration][Integration test] Get migration rules API (#11232) (#210867)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations GET API (route:\r\n`/internal/siem_migrations/rules/{migration_id}`) integration test:\r\n* Basic calls\r\n* Filtering\r\n* Sorting\r\n* Pagination","sha":"526ff0516e701ee1e1db8a248fe8f7c86587d257"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"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/210867","number":210867,"mergeCommit":{"message":"[Rules migration][Integration test] Get migration rules API (#11232) (#210867)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations GET API (route:\r\n`/internal/siem_migrations/rules/{migration_id}`) integration test:\r\n* Basic calls\r\n* Filtering\r\n* Sorting\r\n* Pagination","sha":"526ff0516e701ee1e1db8a248fe8f7c86587d257"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
Abhishek Bhatia
|
24253c7785
|
[8.18] [Entity Analytics][UI] UI changes for Risk Engine to include closed alerts for risk score calculation (#201909) (#210747)
# Backport This will backport the following commits from `main` to `8.18`: - [[Entity Analytics][UI] UI changes for Risk Engine to include closed alerts for risk score calculation (#201909)](https://github.com/elastic/kibana/pull/201909) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Abhishek Bhatia","email":"117628830+abhishekbhatia1710@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-13T06:41:12Z","message":"[Entity Analytics][UI] UI changes for Risk Engine to include closed alerts for risk score calculation (#201909)\n\n## Summary\n\nWe are introducing a new feature that allows users to include \"closed\"\nalerts in risk score calculations.\n\nUsers can toggle a button to include closed alerts in the risk score\ncalculation and specify a date/time range for the calculation.\nAdditionally, they can preview the data before finalising and saving\nthese changes for the next engine run.\n\n\n\n\n### **Note : This PR is an extension to the following PRs.**\n\n- [API] : https://github.com/elastic/kibana/pull/201344\n- [API] : https://github.com/elastic/kibana/pull/201397\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- [x]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a95ec61444470b4a50fe6c7313bd89b8a1801deb","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","v9.0.0","ci:project-deploy-security","Team:Entity Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Entity Analytics][UI] UI changes for Risk Engine to include closed alerts for risk score calculation","number":201909,"url":"https://github.com/elastic/kibana/pull/201909","mergeCommit":{"message":"[Entity Analytics][UI] UI changes for Risk Engine to include closed alerts for risk score calculation (#201909)\n\n## Summary\n\nWe are introducing a new feature that allows users to include \"closed\"\nalerts in risk score calculations.\n\nUsers can toggle a button to include closed alerts in the risk score\ncalculation and specify a date/time range for the calculation.\nAdditionally, they can preview the data before finalising and saving\nthese changes for the next engine run.\n\n\n\n\n### **Note : This PR is an extension to the following PRs.**\n\n- [API] : https://github.com/elastic/kibana/pull/201344\n- [API] : https://github.com/elastic/kibana/pull/201397\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- [x]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a95ec61444470b4a50fe6c7313bd89b8a1801deb"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201909","number":201909,"mergeCommit":{"message":"[Entity Analytics][UI] UI changes for Risk Engine to include closed alerts for risk score calculation (#201909)\n\n## Summary\n\nWe are introducing a new feature that allows users to include \"closed\"\nalerts in risk score calculations.\n\nUsers can toggle a button to include closed alerts in the risk score\ncalculation and specify a date/time range for the calculation.\nAdditionally, they can preview the data before finalising and saving\nthese changes for the next engine run.\n\n\n\n\n### **Note : This PR is an extension to the following PRs.**\n\n- [API] : https://github.com/elastic/kibana/pull/201344\n- [API] : https://github.com/elastic/kibana/pull/201397\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- [x]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a95ec61444470b4a50fe6c7313bd89b8a1801deb"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210707","number":210707,"state":"OPEN"},{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Angela Chuang
|
81eb63af8c
|
[8.18][Security Solution][threat hunting explore] EUI refresh: Rename color variables (#210849)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][threat hunting explore] EUI refresh: Rename color variables (#204908)](https://github.com/elastic/kibana/pull/204908) |
||
|
Angela Chuang
|
224f94591c
|
[8.18] [Security Solution][threat hunting explore] EUI refresh: Remove custom color hex (#204631) (#210566)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][threat hunting explore] EUI refresh: Remove custom color hex (#204631)](https://github.com/elastic/kibana/pull/204631) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Angela Chuang","email":"6295984+angorayc@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-09T12:46:55Z","message":"[Security Solution][threat hunting explore] EUI refresh: Remove custom color hex (#204631)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/issues/202498\r\nhttps://github.com/elastic/kibana/issues/202503\r\n\r\n1. This PR does **Not** include the severity color change. It will be\r\nimplemented in a follow up PR once color tokens have been decided.\r\n2. This PR updates the type `GetLensAttributes` to accept `euiTheme`, so\r\nall the functions in this type are updated accordingly.\r\n\r\nhttps://github.com/elastic/kibana/pull/204631/files#diff-abe20658865cad59eadcff945552b40832d96da0264ed89ddd5ab25ded1420a3R30\r\n\r\n----\r\n\r\n## To test:\r\n\r\nPlease verify if visualizations are displayed properly.\r\n\r\n### Running Kibana with the Borealis theme\r\nIn order to run Kibana with `Borealis`, you'll need to do the following:\r\n\r\n1. Set the following in kibana.dev.yml:\r\n`uiSettings.experimental.themeSwitcherEnabled: true`\r\n4. Run Kibana with the following environment variable set: \r\n```KBN_OPTIMIZER_THEMES=\"borealislight,borealisdark,v8light,v8dark\" yarn start```\r\n\r\n5. This will expose a toggle under Stack Management > Advanced Settings > Theme version, which you can use to toggle between Amsterdam and Borealis.\r\n\r\n\r\n\r\n\r\n----\r\n\r\n\r\n### Explore\r\n\r\n\r\n<img width=\"2557\" alt=\"host_after\" src=\"https://github.com/user-attachments/assets/f69b6e2a-58f6-4ed4-9f38-dcdbcf9919ed\" />\r\n<img width=\"1281\" alt=\"users_after\" src=\"https://github.com/user-attachments/assets/0eec8e9c-e678-4a66-83ee-4b8d11380b8e\" />\r\n<img width=\"2552\" alt=\"network_dns\" src=\"https://github.com/user-attachments/assets/19f06d2a-6e51-419b-9f89-233bfa5727ba\" />\r\n<img width=\"2557\" alt=\"network_after\" src=\"https://github.com/user-attachments/assets/3b90c5e2-23a1-4f15-a2d0-f9290a39af30\" />\r\n\r\n----\r\n\r\n### Dashboards\r\n\r\n<img width=\"2557\" alt=\"dashboard_overview\" src=\"https://github.com/user-attachments/assets/c1873359-fee9-42c6-addd-fe2bc1c98aee\" />\r\n<img width=\"2558\" alt=\"dashboard_detection_response_2\" src=\"https://github.com/user-attachments/assets/f6853710-0938-402b-b326-fa00d586b5d6\" />\r\n<img width=\"2559\" alt=\"dashboard_detection_response_1\" src=\"https://github.com/user-attachments/assets/4eb75526-9a57-46e9-b090-b53353956ea1\" />\r\n\r\n----\r\n\r\n\r\n### Alerts\r\n<img width=\"2555\" alt=\"alerts_chart_collapsed\" src=\"https://github.com/user-attachments/assets/6ecf5dd5-a785-4701-900b-0454f024b36d\" />\r\n<img width=\"2554\" alt=\"summary\" src=\"https://github.com/user-attachments/assets/1731a6ea-ef2b-4d7d-bf21-4041e59f0ad4\" />\r\n<img width=\"2559\" alt=\"trend\" src=\"https://github.com/user-attachments/assets/b9a741d1-a359-4273-9555-850cdcbc8932\" />\r\n<img width=\"2557\" alt=\"counts\" src=\"https://github.com/user-attachments/assets/a6193ccc-86b8-4974-ad9f-9417e200e859\" />\r\n<img width=\"1281\" alt=\"treemap\" src=\"https://github.com/user-attachments/assets/7b6e163a-a660-4bb1-a6de-88e21934b98a\" />\r\n\r\n----\r\n\r\n### Rules preview\r\n<img width=\"2556\" alt=\"Screenshot 2024-12-18 at 13 45 33\" src=\"https://github.com/user-attachments/assets/47099c18-86ee-455a-a5af-ebd6a29904a5\" />\r\n\r\n\r\n----\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"78dfe5f81e8307aea2233a109401489828840b85","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","v9.0.0","ci:cloud-deploy","EUI Visual Refresh"],"title":"[Security Solution][threat hunting explore] EUI refresh: Remove custom color hex","number":204631,"url":"https://github.com/elastic/kibana/pull/204631","mergeCommit":{"message":"[Security Solution][threat hunting explore] EUI refresh: Remove custom color hex (#204631)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/issues/202498\r\nhttps://github.com/elastic/kibana/issues/202503\r\n\r\n1. This PR does **Not** include the severity color change. It will be\r\nimplemented in a follow up PR once color tokens have been decided.\r\n2. This PR updates the type `GetLensAttributes` to accept `euiTheme`, so\r\nall the functions in this type are updated accordingly.\r\n\r\nhttps://github.com/elastic/kibana/pull/204631/files#diff-abe20658865cad59eadcff945552b40832d96da0264ed89ddd5ab25ded1420a3R30\r\n\r\n----\r\n\r\n## To test:\r\n\r\nPlease verify if visualizations are displayed properly.\r\n\r\n### Running Kibana with the Borealis theme\r\nIn order to run Kibana with `Borealis`, you'll need to do the following:\r\n\r\n1. Set the following in kibana.dev.yml:\r\n`uiSettings.experimental.themeSwitcherEnabled: true`\r\n4. Run Kibana with the following environment variable set: \r\n```KBN_OPTIMIZER_THEMES=\"borealislight,borealisdark,v8light,v8dark\" yarn start```\r\n\r\n5. This will expose a toggle under Stack Management > Advanced Settings > Theme version, which you can use to toggle between Amsterdam and Borealis.\r\n\r\n\r\n\r\n\r\n----\r\n\r\n\r\n### Explore\r\n\r\n\r\n<img width=\"2557\" alt=\"host_after\" src=\"https://github.com/user-attachments/assets/f69b6e2a-58f6-4ed4-9f38-dcdbcf9919ed\" />\r\n<img width=\"1281\" alt=\"users_after\" src=\"https://github.com/user-attachments/assets/0eec8e9c-e678-4a66-83ee-4b8d11380b8e\" />\r\n<img width=\"2552\" alt=\"network_dns\" src=\"https://github.com/user-attachments/assets/19f06d2a-6e51-419b-9f89-233bfa5727ba\" />\r\n<img width=\"2557\" alt=\"network_after\" src=\"https://github.com/user-attachments/assets/3b90c5e2-23a1-4f15-a2d0-f9290a39af30\" />\r\n\r\n----\r\n\r\n### Dashboards\r\n\r\n<img width=\"2557\" alt=\"dashboard_overview\" src=\"https://github.com/user-attachments/assets/c1873359-fee9-42c6-addd-fe2bc1c98aee\" />\r\n<img width=\"2558\" alt=\"dashboard_detection_response_2\" src=\"https://github.com/user-attachments/assets/f6853710-0938-402b-b326-fa00d586b5d6\" />\r\n<img width=\"2559\" alt=\"dashboard_detection_response_1\" src=\"https://github.com/user-attachments/assets/4eb75526-9a57-46e9-b090-b53353956ea1\" />\r\n\r\n----\r\n\r\n\r\n### Alerts\r\n<img width=\"2555\" alt=\"alerts_chart_collapsed\" src=\"https://github.com/user-attachments/assets/6ecf5dd5-a785-4701-900b-0454f024b36d\" />\r\n<img width=\"2554\" alt=\"summary\" src=\"https://github.com/user-attachments/assets/1731a6ea-ef2b-4d7d-bf21-4041e59f0ad4\" />\r\n<img width=\"2559\" alt=\"trend\" src=\"https://github.com/user-attachments/assets/b9a741d1-a359-4273-9555-850cdcbc8932\" />\r\n<img width=\"2557\" alt=\"counts\" src=\"https://github.com/user-attachments/assets/a6193ccc-86b8-4974-ad9f-9417e200e859\" />\r\n<img width=\"1281\" alt=\"treemap\" src=\"https://github.com/user-attachments/assets/7b6e163a-a660-4bb1-a6de-88e21934b98a\" />\r\n\r\n----\r\n\r\n### Rules preview\r\n<img width=\"2556\" alt=\"Screenshot 2024-12-18 at 13 45 33\" src=\"https://github.com/user-attachments/assets/47099c18-86ee-455a-a5af-ebd6a29904a5\" />\r\n\r\n\r\n----\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"78dfe5f81e8307aea2233a109401489828840b85"}},"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/204631","number":204631,"mergeCommit":{"message":"[Security Solution][threat hunting explore] EUI refresh: Remove custom color hex (#204631)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/issues/202498\r\nhttps://github.com/elastic/kibana/issues/202503\r\n\r\n1. This PR does **Not** include the severity color change. It will be\r\nimplemented in a follow up PR once color tokens have been decided.\r\n2. This PR updates the type `GetLensAttributes` to accept `euiTheme`, so\r\nall the functions in this type are updated accordingly.\r\n\r\nhttps://github.com/elastic/kibana/pull/204631/files#diff-abe20658865cad59eadcff945552b40832d96da0264ed89ddd5ab25ded1420a3R30\r\n\r\n----\r\n\r\n## To test:\r\n\r\nPlease verify if visualizations are displayed properly.\r\n\r\n### Running Kibana with the Borealis theme\r\nIn order to run Kibana with `Borealis`, you'll need to do the following:\r\n\r\n1. Set the following in kibana.dev.yml:\r\n`uiSettings.experimental.themeSwitcherEnabled: true`\r\n4. Run Kibana with the following environment variable set: \r\n```KBN_OPTIMIZER_THEMES=\"borealislight,borealisdark,v8light,v8dark\" yarn start```\r\n\r\n5. This will expose a toggle under Stack Management > Advanced Settings > Theme version, which you can use to toggle between Amsterdam and Borealis.\r\n\r\n\r\n\r\n\r\n----\r\n\r\n\r\n### Explore\r\n\r\n\r\n<img width=\"2557\" alt=\"host_after\" src=\"https://github.com/user-attachments/assets/f69b6e2a-58f6-4ed4-9f38-dcdbcf9919ed\" />\r\n<img width=\"1281\" alt=\"users_after\" src=\"https://github.com/user-attachments/assets/0eec8e9c-e678-4a66-83ee-4b8d11380b8e\" />\r\n<img width=\"2552\" alt=\"network_dns\" src=\"https://github.com/user-attachments/assets/19f06d2a-6e51-419b-9f89-233bfa5727ba\" />\r\n<img width=\"2557\" alt=\"network_after\" src=\"https://github.com/user-attachments/assets/3b90c5e2-23a1-4f15-a2d0-f9290a39af30\" />\r\n\r\n----\r\n\r\n### Dashboards\r\n\r\n<img width=\"2557\" alt=\"dashboard_overview\" src=\"https://github.com/user-attachments/assets/c1873359-fee9-42c6-addd-fe2bc1c98aee\" />\r\n<img width=\"2558\" alt=\"dashboard_detection_response_2\" src=\"https://github.com/user-attachments/assets/f6853710-0938-402b-b326-fa00d586b5d6\" />\r\n<img width=\"2559\" alt=\"dashboard_detection_response_1\" src=\"https://github.com/user-attachments/assets/4eb75526-9a57-46e9-b090-b53353956ea1\" />\r\n\r\n----\r\n\r\n\r\n### Alerts\r\n<img width=\"2555\" alt=\"alerts_chart_collapsed\" src=\"https://github.com/user-attachments/assets/6ecf5dd5-a785-4701-900b-0454f024b36d\" />\r\n<img width=\"2554\" alt=\"summary\" src=\"https://github.com/user-attachments/assets/1731a6ea-ef2b-4d7d-bf21-4041e59f0ad4\" />\r\n<img width=\"2559\" alt=\"trend\" src=\"https://github.com/user-attachments/assets/b9a741d1-a359-4273-9555-850cdcbc8932\" />\r\n<img width=\"2557\" alt=\"counts\" src=\"https://github.com/user-attachments/assets/a6193ccc-86b8-4974-ad9f-9417e200e859\" />\r\n<img width=\"1281\" alt=\"treemap\" src=\"https://github.com/user-attachments/assets/7b6e163a-a660-4bb1-a6de-88e21934b98a\" />\r\n\r\n----\r\n\r\n### Rules preview\r\n<img width=\"2556\" alt=\"Screenshot 2024-12-18 at 13 45 33\" src=\"https://github.com/user-attachments/assets/47099c18-86ee-455a-a5af-ebd6a29904a5\" />\r\n\r\n\r\n----\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"78dfe5f81e8307aea2233a109401489828840b85"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
47fc4387a7
|
[8.18] Delete 'critical services' count from Entity Analytics Dashboard header (#210827) (#210969)
# Backport This will backport the following commits from `main` to `8.18`: - [Delete 'critical services' count from Entity Analytics Dashboard header (#210827)](https://github.com/elastic/kibana/pull/210827) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T10:14:55Z","message":"Delete 'critical services' count from Entity Analytics Dashboard header (#210827)\n\n## Summary\n\nThis PR deletes the \"Critical Services\" component from the Entity\nAnalytics Dashboard header.\n \n\n\n\nThe component was included with the service entity store, but Product\nand QA consider it confusing and not very valuable to our users.\n\n\n### How to test it?\n* Start Kibana with security data\n* Go to the security solution/entity analytics dashboard\n* The component shouldn't be there","sha":"c241772ecb204e3dbd0943315d476273b7db87a4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team: SecuritySolution","Theme: entity_analytics","Feature:Entity Analytics","Team:Entity Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"Delete 'critical services' count from Entity Analytics Dashboard header","number":210827,"url":"https://github.com/elastic/kibana/pull/210827","mergeCommit":{"message":"Delete 'critical services' count from Entity Analytics Dashboard header (#210827)\n\n## Summary\n\nThis PR deletes the \"Critical Services\" component from the Entity\nAnalytics Dashboard header.\n \n\n\n\nThe component was included with the service entity store, but Product\nand QA consider it confusing and not very valuable to our users.\n\n\n### How to test it?\n* Start Kibana with security data\n* Go to the security solution/entity analytics dashboard\n* The component shouldn't be there","sha":"c241772ecb204e3dbd0943315d476273b7db87a4"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"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/210827","number":210827,"mergeCommit":{"message":"Delete 'critical services' count from Entity Analytics Dashboard header (#210827)\n\n## Summary\n\nThis PR deletes the \"Critical Services\" component from the Entity\nAnalytics Dashboard header.\n \n\n\n\nThe component was included with the service entity store, but Product\nand QA consider it confusing and not very valuable to our users.\n\n\n### How to test it?\n* Start Kibana with security data\n* Go to the security solution/entity analytics dashboard\n* The component shouldn't be there","sha":"c241772ecb204e3dbd0943315d476273b7db87a4"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Pablo Machado <pablo.nevesmachado@elastic.co> |
||
Jared Burgett
|
930465848e
|
[8.18] [Entity Analytics] Consider Closed alerts for Risk Scoring (#193667) (#210941)
# Backport This will backport the following commits from `main` to `8.18`: - [[Entity Analytics] Consider Closed alerts for Risk Scoring (#193667)](https://github.com/elastic/kibana/pull/193667) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Abhishek Bhatia","email":"117628830+abhishekbhatia1710@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-08T07:28:54Z","message":"[Entity Analytics] Consider Closed alerts for Risk Scoring (#193667)\n\n## Summary\r\n\r\n- The changes included in this PR allows the alerts in closed state to\r\nbe included in risk score calculation.\r\n- It also includes the changes to backfill existing data with the\r\nrequired key so that older alerts could also be considered for risk\r\nscore calculation if need be.\r\n- Unit tests and integration tests are also included for the\r\nchanges.Tests for backfill changes are not included in this PR\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](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":"93f03e5939c897c620b36595e5fcc67e74340e38","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","backport","v9.0.0","Feature:Entity Analytics","Team:Entity Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Entity Analytics] Consider Closed alerts for Risk Scoring","number":193667,"url":"https://github.com/elastic/kibana/pull/193667","mergeCommit":{"message":"[Entity Analytics] Consider Closed alerts for Risk Scoring (#193667)\n\n## Summary\r\n\r\n- The changes included in this PR allows the alerts in closed state to\r\nbe included in risk score calculation.\r\n- It also includes the changes to backfill existing data with the\r\nrequired key so that older alerts could also be considered for risk\r\nscore calculation if need be.\r\n- Unit tests and integration tests are also included for the\r\nchanges.Tests for backfill changes are not included in this PR\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](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":"93f03e5939c897c620b36595e5fcc67e74340e38"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/193667","number":193667,"mergeCommit":{"message":"[Entity Analytics] Consider Closed alerts for Risk Scoring (#193667)\n\n## Summary\r\n\r\n- The changes included in this PR allows the alerts in closed state to\r\nbe included in risk score calculation.\r\n- It also includes the changes to backfill existing data with the\r\nrequired key so that older alerts could also be considered for risk\r\nscore calculation if need be.\r\n- Unit tests and integration tests are also included for the\r\nchanges.Tests for backfill changes are not included in this PR\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](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":"93f03e5939c897c620b36595e5fcc67e74340e38"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Abhishek Bhatia <117628830+abhishekbhatia1710@users.noreply.github.com> |
||
elastic-renovate-prod[bot]
|
6a55095236
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to d74b1fd (8.18) (#210723)
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:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xOCIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Karen Grigoryan
|
3b8a5370b4
|
[8.18] Eui Refresh (#204007) (#210915)
# Backport This will backport the following commits from `main` to `8.18`: - [Eui Refresh (#204007)](https://github.com/elastic/kibana/pull/204007) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Charlotte Alexandra Wilson","email":"CAWilson94@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-27T11:43:30Z","message":"Eui Refresh (#204007)\n\n## Summary\r\n\r\nThis PR covers required updates for EUI refresh:\r\n[#11228](https://github.com/elastic/security-team/issues/11228)\r\nThe updates should only cover Entity Owned components. \r\n\r\n### Severity Colors Blocked\r\nSeverity colors are on hold until the security severity color palette is\r\nfinalised. Once agreed, a shared hook will be updated across all of\r\nsecurity, replacing the current RISK_SEVERITY_COLOUR mapping. The\r\nprevious severity colors hook was reverted in preparation for this\r\nchange. Updates for EA will be tracked accordingly.\r\n\r\nSee https://elastic.slack.com/archives/C0851RDCWPP/p1736954935896329 for\r\nmore details\r\n\r\nhttps://github.com/elastic/security-team/issues/11516 \r\nhttps://github.com/elastic/kibana/pull/206276\r\n\r\n---\r\n\r\n### Testing \r\n\r\nRunning Kibana with the Borealis theme\r\nIn order to run Kibana with Borealis, you'll need to do the following:\r\n\r\n1. Set the following in kibana.dev.yml:\r\nu`iSettings.experimental.themeSwitcherEnabled: true`\r\n\r\n2. Run Kibana with the following environment variable set:\r\n`KBN_OPTIMIZER_THEMES=\"borealislight,borealisdark,v8light,v8dark\" yarn\r\nstart`\r\n\r\n3. This will expose a toggle under **Stack Management > Advanced\r\nSettings > Theme version**, which you can use to toggle\r\nbetween Amsterdam and Borealis.\r\n\r\n---\r\n\r\nMore details about each section\r\nhttps://github.com/elastic/kibana/issues/199715\r\n\r\n#### Borealis Updates Light & Dark Theme \r\n\r\n### Screenshots \r\nGoogle Docs for easy read - same screenshots below\r\n\r\nhttps://docs.google.com/document/d/1tKPoqCPbccX94cqgPyHKBdr9_K3kmqveQGkcGo_Q8k4/edit?usp=sharing\r\n\r\n---\r\n## Light Theme\r\n\r\n### Entity Store \r\n\r\n\r\n (#210911)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Remove non-errors and user errors from console logs (#206973)](https://github.com/elastic/kibana/pull/206973) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marshall Main","email":"55718608+marshallmain@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T18:22:31Z","message":"[Security Solution] Remove non-errors and user errors from console logs (#206973)\n\n## Summary\r\n\r\nThis PR will drastically reduce the number of console logs from the\r\nDetection Engine in the overview cluster. If your team is depending on\r\nthe `INFO`, `WARNING`, or `verification_exception` or `ml job missing`\r\n`ERROR` logs in that cluster, please raise your concerns here.\r\n\r\nAddresses https://github.com/elastic/kibana-team/issues/1395,\r\nhttps://github.com/elastic/kibana-team/issues/1333\r\n\r\nHistorically Detection Rules have written an enormous amount of data to\r\nthe console logs. This was helpful in debugging years ago before we had\r\nthe event log, but now we generally don't use them much. The console\r\nlogs all still get scooped up and sent to the overview cluster though.\r\nEvery rule execution writes two or more status changes (first to\r\n'running', then to the final status later on) and these go to the\r\nconsole, the event log, and the rule SO. The end result is 76% of all\r\nlogs are coming from detection rules changing status, mostly successful\r\nstatuses. These provide little value on their own.\r\n\r\nThis PR restricts console logging from detection rules to only non-user\r\nerrors. User errors and execution statuses below the error level will be\r\nlogged in the console at the `debug` level. \"Unexpected\" errors like\r\nsearch exceptions, timeouts, etc will still appear as errors in the\r\nconsole logs. The general idea is that the logs from detection rules in\r\nthe console should represent some kind of unexpected system failure.\r\n\r\nTo implement this change, I updated the console logging logic in both\r\nthe security rule execution logger. User errors reported to the\r\nframework will still create console error logs since they're logged at\r\nthe framework level.\r\n\r\n## Testing\r\nCreate rules that run and generate warnings (e.g. missing index), user\r\nerrors (EQL verification exceptions), and non-user errors. An easy way\r\nto create a non-user error at the moment is running a threshold rule\r\nwhen at least one index searched maps `@timestamp` as a `keyword`\r\ninstead of `date`. The non user errors still show up in console logs as\r\nerrors. User errors and warnings only show up as debug logs and with\r\ndebug logging enabled in the Kibana config.","sha":"9cad58719b3772b745877f4082674e94239a7974","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:cloud-deploy","v8.18.0","v9.1.0","backport:8.18"],"title":"[Security Solution] Remove non-errors and user errors from console logs","number":206973,"url":"https://github.com/elastic/kibana/pull/206973","mergeCommit":{"message":"[Security Solution] Remove non-errors and user errors from console logs (#206973)\n\n## Summary\r\n\r\nThis PR will drastically reduce the number of console logs from the\r\nDetection Engine in the overview cluster. If your team is depending on\r\nthe `INFO`, `WARNING`, or `verification_exception` or `ml job missing`\r\n`ERROR` logs in that cluster, please raise your concerns here.\r\n\r\nAddresses https://github.com/elastic/kibana-team/issues/1395,\r\nhttps://github.com/elastic/kibana-team/issues/1333\r\n\r\nHistorically Detection Rules have written an enormous amount of data to\r\nthe console logs. This was helpful in debugging years ago before we had\r\nthe event log, but now we generally don't use them much. The console\r\nlogs all still get scooped up and sent to the overview cluster though.\r\nEvery rule execution writes two or more status changes (first to\r\n'running', then to the final status later on) and these go to the\r\nconsole, the event log, and the rule SO. The end result is 76% of all\r\nlogs are coming from detection rules changing status, mostly successful\r\nstatuses. These provide little value on their own.\r\n\r\nThis PR restricts console logging from detection rules to only non-user\r\nerrors. User errors and execution statuses below the error level will be\r\nlogged in the console at the `debug` level. \"Unexpected\" errors like\r\nsearch exceptions, timeouts, etc will still appear as errors in the\r\nconsole logs. The general idea is that the logs from detection rules in\r\nthe console should represent some kind of unexpected system failure.\r\n\r\nTo implement this change, I updated the console logging logic in both\r\nthe security rule execution logger. User errors reported to the\r\nframework will still create console error logs since they're logged at\r\nthe framework level.\r\n\r\n## Testing\r\nCreate rules that run and generate warnings (e.g. missing index), user\r\nerrors (EQL verification exceptions), and non-user errors. An easy way\r\nto create a non-user error at the moment is running a threshold rule\r\nwhen at least one index searched maps `@timestamp` as a `keyword`\r\ninstead of `date`. The non user errors still show up in console logs as\r\nerrors. User errors and warnings only show up as debug logs and with\r\ndebug logging enabled in the Kibana config.","sha":"9cad58719b3772b745877f4082674e94239a7974"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"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/206973","number":206973,"mergeCommit":{"message":"[Security Solution] Remove non-errors and user errors from console logs (#206973)\n\n## Summary\r\n\r\nThis PR will drastically reduce the number of console logs from the\r\nDetection Engine in the overview cluster. If your team is depending on\r\nthe `INFO`, `WARNING`, or `verification_exception` or `ml job missing`\r\n`ERROR` logs in that cluster, please raise your concerns here.\r\n\r\nAddresses https://github.com/elastic/kibana-team/issues/1395,\r\nhttps://github.com/elastic/kibana-team/issues/1333\r\n\r\nHistorically Detection Rules have written an enormous amount of data to\r\nthe console logs. This was helpful in debugging years ago before we had\r\nthe event log, but now we generally don't use them much. The console\r\nlogs all still get scooped up and sent to the overview cluster though.\r\nEvery rule execution writes two or more status changes (first to\r\n'running', then to the final status later on) and these go to the\r\nconsole, the event log, and the rule SO. The end result is 76% of all\r\nlogs are coming from detection rules changing status, mostly successful\r\nstatuses. These provide little value on their own.\r\n\r\nThis PR restricts console logging from detection rules to only non-user\r\nerrors. User errors and execution statuses below the error level will be\r\nlogged in the console at the `debug` level. \"Unexpected\" errors like\r\nsearch exceptions, timeouts, etc will still appear as errors in the\r\nconsole logs. The general idea is that the logs from detection rules in\r\nthe console should represent some kind of unexpected system failure.\r\n\r\nTo implement this change, I updated the console logging logic in both\r\nthe security rule execution logger. User errors reported to the\r\nframework will still create console error logs since they're logged at\r\nthe framework level.\r\n\r\n## Testing\r\nCreate rules that run and generate warnings (e.g. missing index), user\r\nerrors (EQL verification exceptions), and non-user errors. An easy way\r\nto create a non-user error at the moment is running a threshold rule\r\nwhen at least one index searched maps `@timestamp` as a `keyword`\r\ninstead of `date`. The non user errors still show up in console logs as\r\nerrors. User errors and warnings only show up as debug logs and with\r\ndebug logging enabled in the Kibana config.","sha":"9cad58719b3772b745877f4082674e94239a7974"}}]}] BACKPORT--> Co-authored-by: Marshall Main <55718608+marshallmain@users.noreply.github.com> |
||
|
Kibana Machine
|
3f4e9c2ed9
|
[8.18] [Search] Increase search timeout toast lifetime to 1 week (#210576) (#210905)
# Backport This will backport the following commits from `main` to `8.18`: - [[Search] Increase search timeout toast lifetime to 1 week (#210576)](https://github.com/elastic/kibana/pull/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> |
||
Alex Prozorov
|
a5891a14a8
|
[8.18] [Cloud Security] skip flaky tests (#197143) (#190967) (#210743)
# Backport This will skip the following tests in version `8.18`: - (https://github.com/elastic/kibana/issues/197143) - https://github.com/elastic/kibana/issues/190967 ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) |
||
|
Kibana Machine
|
6de24bdccd
|
[8.18] Update dependency polished to v4 (main) (#206220) (#210898)
# Backport This will backport the following commits from `main` to `8.18`: - [Update dependency polished to v4 (main) (#206220)](https://github.com/elastic/kibana/pull/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> |
||
|
Kibana Machine
|
daf2be3efe
|
[8.18] [Discover Session] Fix "Untitled" export title when exporting CSV on a dashboard (#210143) (#210882)
# Backport This will backport the following commits from `main` to `8.18`: - [[Discover Session] Fix "Untitled" export title when exporting CSV on a dashboard (#210143)](https://github.com/elastic/kibana/pull/210143) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Matthias Wilhelm","email":"matthias.wilhelm@elastic.co"},"sourceCommit":{"committedDate":"2025-02-12T16:24:43Z","message":"[Discover Session] Fix \"Untitled\" export title when exporting CSV on a dashboard (#210143)\n\n- Fixes \"Untitled\" CSV exports when an export of a Discover session CSV is triggered on a Dashboard\n- Switches to make use of the embeddable title when exporting CSV of Discover session embeddables on a Dashboard.","sha":"7a72b14fd5a032f6bcf5ad5d68f84d7e092a23c8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","Team:DataDiscovery","backport:prev-major","v9.1.0"],"title":"[Discover Session] Fix \"Untitled\" export title when exporting CSV on a dashboard","number":210143,"url":"https://github.com/elastic/kibana/pull/210143","mergeCommit":{"message":"[Discover Session] Fix \"Untitled\" export title when exporting CSV on a dashboard (#210143)\n\n- Fixes \"Untitled\" CSV exports when an export of a Discover session CSV is triggered on a Dashboard\n- Switches to make use of the embeddable title when exporting CSV of Discover session embeddables on a Dashboard.","sha":"7a72b14fd5a032f6bcf5ad5d68f84d7e092a23c8"}},"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/210143","number":210143,"mergeCommit":{"message":"[Discover Session] Fix \"Untitled\" export title when exporting CSV on a dashboard (#210143)\n\n- Fixes \"Untitled\" CSV exports when an export of a Discover session CSV is triggered on a Dashboard\n- Switches to make use of the embeddable title when exporting CSV of Discover session embeddables on a Dashboard.","sha":"7a72b14fd5a032f6bcf5ad5d68f84d7e092a23c8"}}]}] BACKPORT--> Co-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co> |
||
|
Kibana Machine
|
236d660292
|
[8.18] [SecuritySolution] Make entity store description more generic (#209130) (#210889)
# Backport This will backport the following commits from `main` to `8.18`: - [[SecuritySolution] Make entity store description more generic (#209130)](https://github.com/elastic/kibana/pull/209130) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2025-02-12T16:47:26Z","message":"[SecuritySolution] Make entity store description more generic (#209130)\n\n## Summary\n\nMake entity store description more generic.\nBefore:\n\"Store host and user entities observed in events.\"\n\"Monitor user and host risk scores, and track anomalies.\"\n\n\nAfter:\n\"Store entities data observed in events.\"\n\"Monitor entities' risk scores, and track anomalies.\"\n\n\n\n\n\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] 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":"78a596b05ff079cab6a6c162bb3e2b33a442dc8d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team: SecuritySolution","Theme: entity_analytics","Feature:Entity Analytics","ci:build-serverless-image","Team:Entity Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[SecuritySolution] Make entity store description more generic","number":209130,"url":"https://github.com/elastic/kibana/pull/209130","mergeCommit":{"message":"[SecuritySolution] Make entity store description more generic (#209130)\n\n## Summary\n\nMake entity store description more generic.\nBefore:\n\"Store host and user entities observed in events.\"\n\"Monitor user and host risk scores, and track anomalies.\"\n\n\nAfter:\n\"Store entities data observed in events.\"\n\"Monitor entities' risk scores, and track anomalies.\"\n\n\n\n\n\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] 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":"78a596b05ff079cab6a6c162bb3e2b33a442dc8d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"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/209130","number":209130,"mergeCommit":{"message":"[SecuritySolution] Make entity store description more generic (#209130)\n\n## Summary\n\nMake entity store description more generic.\nBefore:\n\"Store host and user entities observed in events.\"\n\"Monitor user and host risk scores, and track anomalies.\"\n\n\nAfter:\n\"Store entities data observed in events.\"\n\"Monitor entities' risk scores, and track anomalies.\"\n\n\n\n\n\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] 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":"78a596b05ff079cab6a6c162bb3e2b33a442dc8d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Pablo Machado <pablo.nevesmachado@elastic.co> |