mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
80175 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
natasha-moore-elastic
|
a646c34ebe
|
[8.16] [DOCS] Deletes asciidoc Osquery API docs (#216269) (#216433)
{defaultPrDescription}
<!--BACKPORT {commits} BACKPORT-->
|
||
Kibana Machine
|
4deefffb00
|
[8.16] [APM][OTel] Service inventory icons should be visible if the agentName is returned (#216220) (#216464)
# Backport This will backport the following commits from `main` to `8.16`: - [[APM][OTel] Service inventory icons should be visible if the `agentName` is returned (#216220)](https://github.com/elastic/kibana/pull/216220) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-31T13:07:17Z","message":"[APM][OTel] Service inventory icons should be visible if the `agentName` is returned (#216220)\n\nCloses #214562 \n\n## Summary\n\nThis PR fixes the issue with the service icons overridden by the merge\nof the service stats\n\n## Testing\nAs this is a bit tricky to test - it needs a bit of refreshing /\nchanging the time range, etc. to reproduce\nThe way to verify the fix is to check the service overview - every\nservice that has an icon there should have an icon in the service\ninventory:\n\n\nhttps://github.com/user-attachments/assets/e401554b-6a39-440b-a52b-a126e42eacd5","sha":"cd8f18eed82722bfee3c27829ba233b381aea0cc","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:obs-ux-infra_services","v9.1.0"],"title":"[APM][OTel] Service inventory icons should be visible if the `agentName` is returned","number":216220,"url":"https://github.com/elastic/kibana/pull/216220","mergeCommit":{"message":"[APM][OTel] Service inventory icons should be visible if the `agentName` is returned (#216220)\n\nCloses #214562 \n\n## Summary\n\nThis PR fixes the issue with the service icons overridden by the merge\nof the service stats\n\n## Testing\nAs this is a bit tricky to test - it needs a bit of refreshing /\nchanging the time range, etc. to reproduce\nThe way to verify the fix is to check the service overview - every\nservice that has an icon there should have an icon in the service\ninventory:\n\n\nhttps://github.com/user-attachments/assets/e401554b-6a39-440b-a52b-a126e42eacd5","sha":"cd8f18eed82722bfee3c27829ba233b381aea0cc"}},"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/216220","number":216220,"mergeCommit":{"message":"[APM][OTel] Service inventory icons should be visible if the `agentName` is returned (#216220)\n\nCloses #214562 \n\n## Summary\n\nThis PR fixes the issue with the service icons overridden by the merge\nof the service stats\n\n## Testing\nAs this is a bit tricky to test - it needs a bit of refreshing /\nchanging the time range, etc. to reproduce\nThe way to verify the fix is to check the service overview - every\nservice that has an icon there should have an icon in the service\ninventory:\n\n\nhttps://github.com/user-attachments/assets/e401554b-6a39-440b-a52b-a126e42eacd5","sha":"cd8f18eed82722bfee3c27829ba233b381aea0cc"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co> |
||
|
Kibana Machine
|
91f571069c
|
[8.16] Fixes Failing test: X-Pack Alerting API Integration Tests - Alerting - group3.x-pack/test/alerting_api_integration/spaces_only/tests/alerting/group3/builtin_alert_types/es_query/rule·ts - Alerting builtin alertTypes es_query rule runs correctly: threshold on ungrouped hit count < > for esQuery search type (#215604) (#216368)
# Backport This will backport the following commits from `main` to `8.16`: - [Fixes Failing test: X-Pack Alerting API Integration Tests - Alerting - group3.x-pack/test/alerting_api_integration/spaces_only/tests/alerting/group3/builtin_alert_types/es_query/rule·ts - Alerting builtin alertTypes es_query rule runs correctly: threshold on ungrouped hit count < > for esQuery search type (#215604)](https://github.com/elastic/kibana/pull/215604) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ying Mao","email":"ying.mao@elastic.co"},"sourceCommit":{"committedDate":"2025-03-28T18:40:18Z","message":"Fixes Failing test: X-Pack Alerting API Integration Tests - Alerting - group3.x-pack/test/alerting_api_integration/spaces_only/tests/alerting/group3/builtin_alert_types/es_query/rule·ts - Alerting builtin alertTypes es_query rule runs correctly: threshold on ungrouped hit count < > for esQuery search type (#215604)\n\nResolves https://github.com/elastic/kibana/issues/194701\n\n## Summary\n\nThe rule conditions are testing that the doc count > -1 but we're\ntesting that the evaluated value is > 0. Because an evaluated value of 0\nwill also match the rule condition, occasionally this expect would fail.\nUpdated the test to match what is allowed by the rule condition.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"df728ab823e2fb007a816d98f99faf1fef558b4c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","v8.16.0","backport:version","v9.1.0","v8.19.0"],"title":"Fixes Failing test: X-Pack Alerting API Integration Tests - Alerting - group3.x-pack/test/alerting_api_integration/spaces_only/tests/alerting/group3/builtin_alert_types/es_query/rule·ts - Alerting builtin alertTypes es_query rule runs correctly: threshold on ungrouped hit count < > for esQuery search type","number":215604,"url":"https://github.com/elastic/kibana/pull/215604","mergeCommit":{"message":"Fixes Failing test: X-Pack Alerting API Integration Tests - Alerting - group3.x-pack/test/alerting_api_integration/spaces_only/tests/alerting/group3/builtin_alert_types/es_query/rule·ts - Alerting builtin alertTypes es_query rule runs correctly: threshold on ungrouped hit count < > for esQuery search type (#215604)\n\nResolves https://github.com/elastic/kibana/issues/194701\n\n## Summary\n\nThe rule conditions are testing that the doc count > -1 but we're\ntesting that the evaluated value is > 0. Because an evaluated value of 0\nwill also match the rule condition, occasionally this expect would fail.\nUpdated the test to match what is allowed by the rule condition.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"df728ab823e2fb007a816d98f99faf1fef558b4c"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"8.16","label":"v8.16.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/215604","number":215604,"mergeCommit":{"message":"Fixes Failing test: X-Pack Alerting API Integration Tests - Alerting - group3.x-pack/test/alerting_api_integration/spaces_only/tests/alerting/group3/builtin_alert_types/es_query/rule·ts - Alerting builtin alertTypes es_query rule runs correctly: threshold on ungrouped hit count < > for esQuery search type (#215604)\n\nResolves https://github.com/elastic/kibana/issues/194701\n\n## Summary\n\nThe rule conditions are testing that the doc count > -1 but we're\ntesting that the evaluated value is > 0. Because an evaluated value of 0\nwill also match the rule condition, occasionally this expect would fail.\nUpdated the test to match what is allowed by the rule condition.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"df728ab823e2fb007a816d98f99faf1fef558b4c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ying Mao <ying.mao@elastic.co> |
||
|
Kibana Machine
|
a96987c38c
|
[8.16] [Fleet] disable unenroll action on agentless agents (#216299) (#216331)
# Backport This will backport the following commits from `main` to `8.16`: - [[Fleet] disable unenroll action on agentless agents (#216299)](https://github.com/elastic/kibana/pull/216299) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-28T15:51:02Z","message":"[Fleet] disable unenroll action on agentless agents (#216299)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/209173\n\nDisable Unenroll agent action on agentless agents\n\n<img width=\"1124\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/6603bac5-b0b1-4a20-8b16-f121bd69e969\"\n/>\n<img width=\"1126\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e41bca5b-f73d-44bc-b095-9970a25f6322\"\n/>","sha":"6914495033b75d80af64a247768223547f501234","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","backport:prev-major","v9.1.0"],"title":"[Fleet] disable unenroll action on agentless agents","number":216299,"url":"https://github.com/elastic/kibana/pull/216299","mergeCommit":{"message":"[Fleet] disable unenroll action on agentless agents (#216299)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/209173\n\nDisable Unenroll agent action on agentless agents\n\n<img width=\"1124\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/6603bac5-b0b1-4a20-8b16-f121bd69e969\"\n/>\n<img width=\"1126\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e41bca5b-f73d-44bc-b095-9970a25f6322\"\n/>","sha":"6914495033b75d80af64a247768223547f501234"}},"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/216299","number":216299,"mergeCommit":{"message":"[Fleet] disable unenroll action on agentless agents (#216299)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/209173\n\nDisable Unenroll agent action on agentless agents\n\n<img width=\"1124\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/6603bac5-b0b1-4a20-8b16-f121bd69e969\"\n/>\n<img width=\"1126\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e41bca5b-f73d-44bc-b095-9970a25f6322\"\n/>","sha":"6914495033b75d80af64a247768223547f501234"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
89257878bd
|
[8.16] fix: [Analytics:Maps page]Duplication of elements announcement (#215684) (#216182)
# Backport This will backport the following commits from `main` to `8.16`: - [fix: [Analytics:Maps page]Duplication of elements announcement (#215684)](https://github.com/elastic/kibana/pull/215684) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-03-27T14:13:56Z","message":"fix: [Analytics:Maps page]Duplication of elements announcement (#215684)\n\nPart of: #215647\n\n## Summary\n\nIt is enough for user to hear the same information once upon reaching\nelement.\nEspecially for the users using assistive technology.\n\n### Changes made: \n\n1. Partially fix #215647. Only list page related part! Text for\n'aria-label' attribute were updated\n\n### Screen:\n\n<img width=\"1408\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/be4f6166-238e-484e-bbc2-cbb6bf5de162\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ef5a2c9adba43f849eda3a3134371461fee7c846","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix: [Analytics:Maps page]Duplication of elements announcement","number":215684,"url":"https://github.com/elastic/kibana/pull/215684","mergeCommit":{"message":"fix: [Analytics:Maps page]Duplication of elements announcement (#215684)\n\nPart of: #215647\n\n## Summary\n\nIt is enough for user to hear the same information once upon reaching\nelement.\nEspecially for the users using assistive technology.\n\n### Changes made: \n\n1. Partially fix #215647. Only list page related part! Text for\n'aria-label' attribute were updated\n\n### Screen:\n\n<img width=\"1408\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/be4f6166-238e-484e-bbc2-cbb6bf5de162\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ef5a2c9adba43f849eda3a3134371461fee7c846"}},"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/215684","number":215684,"mergeCommit":{"message":"fix: [Analytics:Maps page]Duplication of elements announcement (#215684)\n\nPart of: #215647\n\n## Summary\n\nIt is enough for user to hear the same information once upon reaching\nelement.\nEspecially for the users using assistive technology.\n\n### Changes made: \n\n1. Partially fix #215647. Only list page related part! Text for\n'aria-label' attribute were updated\n\n### Screen:\n\n<img width=\"1408\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/be4f6166-238e-484e-bbc2-cbb6bf5de162\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ef5a2c9adba43f849eda3a3134371461fee7c846"}}]}] BACKPORT--> Co-authored-by: Alexey Antonov <alexwizp@gmail.com> |
||
|
Kibana Machine
|
0d8800cbee
|
[8.16] fix: [Analytics:Visualize Library page]Incorrect aria label used for Tags list (#215658) (#216183)
# Backport This will backport the following commits from `main` to `8.16`: - [fix: [Analytics:Visualize Library page]Incorrect aria label used for Tags list (#215658)](https://github.com/elastic/kibana/pull/215658) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-03-27T14:14:11Z","message":"fix: [Analytics:Visualize Library page]Incorrect aria label used for Tags list (#215658)\n\nCloses: #215004\n\n# Description\nNames of elements has to be clear and descriptive for user to know what\nelement is currently active, how to interact with it. Same with aria\nlabels.\nEspecially for the users using assistive technology.\n\n# Changes made? \n1. Fixed mentioned a11y concerns\n2. Fixed translations\n\n\n# Screen: \n<img width=\"1408\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d5b1b404-5a4a-4499-8a1c-59528c866bf9\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"418e328b9d25fde0743fa569c5b0c8a41669319e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix: [Analytics:Visualize Library page]Incorrect aria label used for Tags list","number":215658,"url":"https://github.com/elastic/kibana/pull/215658","mergeCommit":{"message":"fix: [Analytics:Visualize Library page]Incorrect aria label used for Tags list (#215658)\n\nCloses: #215004\n\n# Description\nNames of elements has to be clear and descriptive for user to know what\nelement is currently active, how to interact with it. Same with aria\nlabels.\nEspecially for the users using assistive technology.\n\n# Changes made? \n1. Fixed mentioned a11y concerns\n2. Fixed translations\n\n\n# Screen: \n<img width=\"1408\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d5b1b404-5a4a-4499-8a1c-59528c866bf9\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"418e328b9d25fde0743fa569c5b0c8a41669319e"}},"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/215658","number":215658,"mergeCommit":{"message":"fix: [Analytics:Visualize Library page]Incorrect aria label used for Tags list (#215658)\n\nCloses: #215004\n\n# Description\nNames of elements has to be clear and descriptive for user to know what\nelement is currently active, how to interact with it. Same with aria\nlabels.\nEspecially for the users using assistive technology.\n\n# Changes made? \n1. Fixed mentioned a11y concerns\n2. Fixed translations\n\n\n# Screen: \n<img width=\"1408\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d5b1b404-5a4a-4499-8a1c-59528c866bf9\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"418e328b9d25fde0743fa569c5b0c8a41669319e"}}]}] BACKPORT--> Co-authored-by: Alexey Antonov <alexwizp@gmail.com> |
||
|
Kibana Machine
|
09ea3c5bb4
|
[8.16] Prevent layout shifts after UnifiedSearch loads async (#215733) (#215954)
# Backport This will backport the following commits from `main` to `8.16`: - [Prevent layout shifts after UnifiedSearch loads async (#215733)](https://github.com/elastic/kibana/pull/215733) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alberto Blázquez","email":"albertoblaz@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-25T21:07:06Z","message":"Prevent layout shifts after UnifiedSearch loads async (#215733)\n\n## Summary\n\nPart of the solution for:\n- https://github.com/elastic/security-team/issues/12209.\n\nAdjusts UnifiedSearch's Fallback (used by React Suspense while module is\nloading) height to be equal to the final UI rendered to prevent layout\nshifts when a page opens and renders it.\n\n### Motivation\n\nThe `UnifiedSearch` module is used across all Kibana. It renders a\n`<Fallback>` component with React Suspense while the whole module is\nloading async. Once loaded, React swaps `<Fallback>` with the loaded UI.\nThe problem is their sizes are different, and thus, it gives the\nimpression of a jumpy UI with perceived low performance.\n\nThe consequence of layout shifts is browsers need to perform a new\nrendering cycle, affecting performance negatively:\n1. **Layout**. This means they need to calculate again the exact\nposition and size of every visible element, an expensive operation also\nknown as \"reflow\".\n2. **Paint**. Once the layout is ready, browsers need to fill those\npixels with colors, borders, text, shadow, etc...\n3. **Composite (Layering and rendering)**. Finally, browsers put\neverything together in different layers and render them on screen.\n\n## Screenshots\n\n### Asset Inventory before the fix\n\n| State | Screenshot |\n|--------|--------|\n| Fallback | <img width=\"690\" alt=\"Screenshot 2025-03-24 at 16 03 51\"\nsrc=\"https://github.com/user-attachments/assets/ce8e9bc3-723b-4678-9079-5e605c2fe89f\"\n/> |\n| Loaded | <img width=\"690\" alt=\"Screenshot 2025-03-24 at 14 10 44\"\nsrc=\"https://github.com/user-attachments/assets/6de30b38-91e7-4e0a-b2b4-db4477972842\"\n/> |\n\n### Asset Inventory after the fix\n\n| State | Screenshot |\n|--------|--------|\n| Fallback | <img width=\"690\" alt=\"Screenshot 2025-03-24 at 14 10 22\"\nsrc=\"https://github.com/user-attachments/assets/d2868766-3ca8-401b-9b79-63b2acde7c4a\"\n/> |\n| Loaded | <img width=\"690\" alt=\"Screenshot 2025-03-24 at 14 10 44\"\nsrc=\"https://github.com/user-attachments/assets/6de30b38-91e7-4e0a-b2b4-db4477972842\"\n/> |\n\n### Discover after the fix\n\n> [!NOTE]\n> This only addresses the case with regular queries. If running the\nES|QL mode, there's still a layout shift caused by the Monaco editor\nrendered async within the UnifiedSearch boundaries. This is beyond the\nscope of this PR\n\n| State | Screenshot |\n|--------|--------|\n| Fallback | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 11 55 29\"\nsrc=\"https://github.com/user-attachments/assets/e91fbb27-256e-40f8-ba20-8c4952ca8bc2\"\n/> |\n| Loaded | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 11 55 41\"\nsrc=\"https://github.com/user-attachments/assets/48453d4f-e108-42a4-ae28-9495f6b754dd\"\n/> |\n\n### Alerts and Findings after the fix\n\n> [!NOTE]\n> Alerts and Findings need a separate fix to render UnifiedSearch with\nthe page template's first render, not after\n\nAs of now, both pages render first a blank page template while they wait\nfor their data-view to load. This happens before rendering the\nUnifiedSearch fallback, which means there will still be a layout shift\nwhen they open. A separate fix is needed to prevent layout shifts there.\nHowever, if this is addressed, swapping Fallback with the Loaded\ncounterpart happens in-place as the images below:\n\n| State | Screenshot |\n|--------|--------|\n| Fallback | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 12 06 33\"\nsrc=\"https://github.com/user-attachments/assets/ec3f6709-cc67-4828-8c9e-ee140b618bb4\"\n/> |\n| Loaded | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 12 06 20\"\nsrc=\"https://github.com/user-attachments/assets/6894e9cf-6a26-41a4-a0c1-293c7f4872a6\"\n/> |\n\n| State | Screenshot |\n|--------|--------|\n| Fallback | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 12 07 22\"\nsrc=\"https://github.com/user-attachments/assets/f79ea420-573f-4d46-a5d9-afcc2b6ea9bb\"\n/> |\n| Loaded | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 12 07 09\"\nsrc=\"https://github.com/user-attachments/assets/d67f2368-1919-4ee9-a938-fc2ecd2d215e\"\n/> |\n\n### Edge-case: Multiple filters visible\n\n> [!NOTE]\n> Layout shifts will still happen with the filter bar visible and\nmultiple filters applied\n\nWhen the `showFilterBar` prop is `true` in UnifiedSearch and the number\nof applied filters is high enough to be broken into multiple lines, it's\nimpossible to calculate the height of the component without waiting for\nit to be loaded, rendered and then measure the DOM node's height. This\nmeans layout shifts will still happen and it's totally out of the scope\nof this PR.\n\n## More details\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nSuspensed `<Fallback>` component now depends on the `query` prop, which\nmight cause some re-renderings in case its value changes. However,\nperformance impact should be minimal.","sha":"451700afc3a513544154096b5e3a850b73ed8844","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","release_note:skip","UX","backport:all-open","v9.1.0"],"title":"Prevent layout shifts after UnifiedSearch loads async","number":215733,"url":"https://github.com/elastic/kibana/pull/215733","mergeCommit":{"message":"Prevent layout shifts after UnifiedSearch loads async (#215733)\n\n## Summary\n\nPart of the solution for:\n- https://github.com/elastic/security-team/issues/12209.\n\nAdjusts UnifiedSearch's Fallback (used by React Suspense while module is\nloading) height to be equal to the final UI rendered to prevent layout\nshifts when a page opens and renders it.\n\n### Motivation\n\nThe `UnifiedSearch` module is used across all Kibana. It renders a\n`<Fallback>` component with React Suspense while the whole module is\nloading async. Once loaded, React swaps `<Fallback>` with the loaded UI.\nThe problem is their sizes are different, and thus, it gives the\nimpression of a jumpy UI with perceived low performance.\n\nThe consequence of layout shifts is browsers need to perform a new\nrendering cycle, affecting performance negatively:\n1. **Layout**. This means they need to calculate again the exact\nposition and size of every visible element, an expensive operation also\nknown as \"reflow\".\n2. **Paint**. Once the layout is ready, browsers need to fill those\npixels with colors, borders, text, shadow, etc...\n3. **Composite (Layering and rendering)**. Finally, browsers put\neverything together in different layers and render them on screen.\n\n## Screenshots\n\n### Asset Inventory before the fix\n\n| State | Screenshot |\n|--------|--------|\n| Fallback | <img width=\"690\" alt=\"Screenshot 2025-03-24 at 16 03 51\"\nsrc=\"https://github.com/user-attachments/assets/ce8e9bc3-723b-4678-9079-5e605c2fe89f\"\n/> |\n| Loaded | <img width=\"690\" alt=\"Screenshot 2025-03-24 at 14 10 44\"\nsrc=\"https://github.com/user-attachments/assets/6de30b38-91e7-4e0a-b2b4-db4477972842\"\n/> |\n\n### Asset Inventory after the fix\n\n| State | Screenshot |\n|--------|--------|\n| Fallback | <img width=\"690\" alt=\"Screenshot 2025-03-24 at 14 10 22\"\nsrc=\"https://github.com/user-attachments/assets/d2868766-3ca8-401b-9b79-63b2acde7c4a\"\n/> |\n| Loaded | <img width=\"690\" alt=\"Screenshot 2025-03-24 at 14 10 44\"\nsrc=\"https://github.com/user-attachments/assets/6de30b38-91e7-4e0a-b2b4-db4477972842\"\n/> |\n\n### Discover after the fix\n\n> [!NOTE]\n> This only addresses the case with regular queries. If running the\nES|QL mode, there's still a layout shift caused by the Monaco editor\nrendered async within the UnifiedSearch boundaries. This is beyond the\nscope of this PR\n\n| State | Screenshot |\n|--------|--------|\n| Fallback | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 11 55 29\"\nsrc=\"https://github.com/user-attachments/assets/e91fbb27-256e-40f8-ba20-8c4952ca8bc2\"\n/> |\n| Loaded | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 11 55 41\"\nsrc=\"https://github.com/user-attachments/assets/48453d4f-e108-42a4-ae28-9495f6b754dd\"\n/> |\n\n### Alerts and Findings after the fix\n\n> [!NOTE]\n> Alerts and Findings need a separate fix to render UnifiedSearch with\nthe page template's first render, not after\n\nAs of now, both pages render first a blank page template while they wait\nfor their data-view to load. This happens before rendering the\nUnifiedSearch fallback, which means there will still be a layout shift\nwhen they open. A separate fix is needed to prevent layout shifts there.\nHowever, if this is addressed, swapping Fallback with the Loaded\ncounterpart happens in-place as the images below:\n\n| State | Screenshot |\n|--------|--------|\n| Fallback | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 12 06 33\"\nsrc=\"https://github.com/user-attachments/assets/ec3f6709-cc67-4828-8c9e-ee140b618bb4\"\n/> |\n| Loaded | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 12 06 20\"\nsrc=\"https://github.com/user-attachments/assets/6894e9cf-6a26-41a4-a0c1-293c7f4872a6\"\n/> |\n\n| State | Screenshot |\n|--------|--------|\n| Fallback | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 12 07 22\"\nsrc=\"https://github.com/user-attachments/assets/f79ea420-573f-4d46-a5d9-afcc2b6ea9bb\"\n/> |\n| Loaded | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 12 07 09\"\nsrc=\"https://github.com/user-attachments/assets/d67f2368-1919-4ee9-a938-fc2ecd2d215e\"\n/> |\n\n### Edge-case: Multiple filters visible\n\n> [!NOTE]\n> Layout shifts will still happen with the filter bar visible and\nmultiple filters applied\n\nWhen the `showFilterBar` prop is `true` in UnifiedSearch and the number\nof applied filters is high enough to be broken into multiple lines, it's\nimpossible to calculate the height of the component without waiting for\nit to be loaded, rendered and then measure the DOM node's height. This\nmeans layout shifts will still happen and it's totally out of the scope\nof this PR.\n\n## More details\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nSuspensed `<Fallback>` component now depends on the `query` prop, which\nmight cause some re-renderings in case its value changes. However,\nperformance impact should be minimal.","sha":"451700afc3a513544154096b5e3a850b73ed8844"}},"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/215733","number":215733,"mergeCommit":{"message":"Prevent layout shifts after UnifiedSearch loads async (#215733)\n\n## Summary\n\nPart of the solution for:\n- https://github.com/elastic/security-team/issues/12209.\n\nAdjusts UnifiedSearch's Fallback (used by React Suspense while module is\nloading) height to be equal to the final UI rendered to prevent layout\nshifts when a page opens and renders it.\n\n### Motivation\n\nThe `UnifiedSearch` module is used across all Kibana. It renders a\n`<Fallback>` component with React Suspense while the whole module is\nloading async. Once loaded, React swaps `<Fallback>` with the loaded UI.\nThe problem is their sizes are different, and thus, it gives the\nimpression of a jumpy UI with perceived low performance.\n\nThe consequence of layout shifts is browsers need to perform a new\nrendering cycle, affecting performance negatively:\n1. **Layout**. This means they need to calculate again the exact\nposition and size of every visible element, an expensive operation also\nknown as \"reflow\".\n2. **Paint**. Once the layout is ready, browsers need to fill those\npixels with colors, borders, text, shadow, etc...\n3. **Composite (Layering and rendering)**. Finally, browsers put\neverything together in different layers and render them on screen.\n\n## Screenshots\n\n### Asset Inventory before the fix\n\n| State | Screenshot |\n|--------|--------|\n| Fallback | <img width=\"690\" alt=\"Screenshot 2025-03-24 at 16 03 51\"\nsrc=\"https://github.com/user-attachments/assets/ce8e9bc3-723b-4678-9079-5e605c2fe89f\"\n/> |\n| Loaded | <img width=\"690\" alt=\"Screenshot 2025-03-24 at 14 10 44\"\nsrc=\"https://github.com/user-attachments/assets/6de30b38-91e7-4e0a-b2b4-db4477972842\"\n/> |\n\n### Asset Inventory after the fix\n\n| State | Screenshot |\n|--------|--------|\n| Fallback | <img width=\"690\" alt=\"Screenshot 2025-03-24 at 14 10 22\"\nsrc=\"https://github.com/user-attachments/assets/d2868766-3ca8-401b-9b79-63b2acde7c4a\"\n/> |\n| Loaded | <img width=\"690\" alt=\"Screenshot 2025-03-24 at 14 10 44\"\nsrc=\"https://github.com/user-attachments/assets/6de30b38-91e7-4e0a-b2b4-db4477972842\"\n/> |\n\n### Discover after the fix\n\n> [!NOTE]\n> This only addresses the case with regular queries. If running the\nES|QL mode, there's still a layout shift caused by the Monaco editor\nrendered async within the UnifiedSearch boundaries. This is beyond the\nscope of this PR\n\n| State | Screenshot |\n|--------|--------|\n| Fallback | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 11 55 29\"\nsrc=\"https://github.com/user-attachments/assets/e91fbb27-256e-40f8-ba20-8c4952ca8bc2\"\n/> |\n| Loaded | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 11 55 41\"\nsrc=\"https://github.com/user-attachments/assets/48453d4f-e108-42a4-ae28-9495f6b754dd\"\n/> |\n\n### Alerts and Findings after the fix\n\n> [!NOTE]\n> Alerts and Findings need a separate fix to render UnifiedSearch with\nthe page template's first render, not after\n\nAs of now, both pages render first a blank page template while they wait\nfor their data-view to load. This happens before rendering the\nUnifiedSearch fallback, which means there will still be a layout shift\nwhen they open. A separate fix is needed to prevent layout shifts there.\nHowever, if this is addressed, swapping Fallback with the Loaded\ncounterpart happens in-place as the images below:\n\n| State | Screenshot |\n|--------|--------|\n| Fallback | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 12 06 33\"\nsrc=\"https://github.com/user-attachments/assets/ec3f6709-cc67-4828-8c9e-ee140b618bb4\"\n/> |\n| Loaded | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 12 06 20\"\nsrc=\"https://github.com/user-attachments/assets/6894e9cf-6a26-41a4-a0c1-293c7f4872a6\"\n/> |\n\n| State | Screenshot |\n|--------|--------|\n| Fallback | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 12 07 22\"\nsrc=\"https://github.com/user-attachments/assets/f79ea420-573f-4d46-a5d9-afcc2b6ea9bb\"\n/> |\n| Loaded | <img width=\"690\" alt=\"Screenshot 2025-03-25 at 12 07 09\"\nsrc=\"https://github.com/user-attachments/assets/d67f2368-1919-4ee9-a938-fc2ecd2d215e\"\n/> |\n\n### Edge-case: Multiple filters visible\n\n> [!NOTE]\n> Layout shifts will still happen with the filter bar visible and\nmultiple filters applied\n\nWhen the `showFilterBar` prop is `true` in UnifiedSearch and the number\nof applied filters is high enough to be broken into multiple lines, it's\nimpossible to calculate the height of the component without waiting for\nit to be loaded, rendered and then measure the DOM node's height. This\nmeans layout shifts will still happen and it's totally out of the scope\nof this PR.\n\n## More details\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nSuspensed `<Fallback>` component now depends on the `query` prop, which\nmight cause some re-renderings in case its value changes. However,\nperformance impact should be minimal.","sha":"451700afc3a513544154096b5e3a850b73ed8844"}}]}] BACKPORT--> Co-authored-by: Alberto Blázquez <albertoblaz@users.noreply.github.com> |
||
Tiago Costa
|
f0e2691a1b
|
chore(NA): bump version to 8.16.7 (#215927)
Usually bump from 8.16.6 to 8.16.7 |
||
|
Kibana Machine
|
2dbf8e2a2d
|
[8.16] Fix text overflow and alignment in agent details integration input status (#215807) (#215936)
# Backport This will backport the following commits from `main` to `8.16`: - [Fix text overflow and alignment in agent details integration input status (#215807)](https://github.com/elastic/kibana/pull/215807) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Michel Losier","email":"mikelosier@gmail.com"},"sourceCommit":{"committedDate":"2025-03-25T15:51:26Z","message":"Fix text overflow and alignment in agent details integration input status (#215807)\n\n## Summary\n\nAddresses: https://github.com/elastic/kibana/issues/176271\n\n* Allows text overflow in the Agent details integration input statuses\nto flow to the next lines\n* Applies left alignment as well, which makes it consistent with the\nstyling in error callouts and content in the policy response tree view.","sha":"31ea22e207cae78a597581dd78106ef8d6bfc526","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","backport:prev-major","v9.1.0"],"title":"Fix text overflow and alignment in agent details integration input status","number":215807,"url":"https://github.com/elastic/kibana/pull/215807","mergeCommit":{"message":"Fix text overflow and alignment in agent details integration input status (#215807)\n\n## Summary\n\nAddresses: https://github.com/elastic/kibana/issues/176271\n\n* Allows text overflow in the Agent details integration input statuses\nto flow to the next lines\n* Applies left alignment as well, which makes it consistent with the\nstyling in error callouts and content in the policy response tree view.","sha":"31ea22e207cae78a597581dd78106ef8d6bfc526"}},"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/215807","number":215807,"mergeCommit":{"message":"Fix text overflow and alignment in agent details integration input status (#215807)\n\n## Summary\n\nAddresses: https://github.com/elastic/kibana/issues/176271\n\n* Allows text overflow in the Agent details integration input statuses\nto flow to the next lines\n* Applies left alignment as well, which makes it consistent with the\nstyling in error callouts and content in the policy response tree view.","sha":"31ea22e207cae78a597581dd78106ef8d6bfc526"}}]}] BACKPORT--> Co-authored-by: Michel Losier <mikelosier@gmail.com> |
||
|
Kibana Machine
|
a8b89ce376
|
[8.16] Disable allowAbsoluteUrls for axios (#215138) (#215826)
# Backport This will backport the following commits from `main` to `8.16`: - [Disable `allowAbsoluteUrls` for axios (#215138)](https://github.com/elastic/kibana/pull/215138) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-03-25T08:52:36Z","message":"Disable `allowAbsoluteUrls` for axios (#215138)\n\n## Summary\nAfter https://github.com/elastic/kibana/pull/214843, `axios` client\nusages need to set a flag to prevent the vulnerable behavior.\n\nTo reviewers: if you think it's a mistake, and you created a client to\nrequest for absolute URLs, consider unsetting the `baseURL` to\ncommunicate intent.","sha":"e40b17aa22ec1a2fbc56ae8651e12f658099ec14","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","Team:QA","Team:Security","release_note:skip","backport:all-open","Team:obs-ux-logs","Team:obs-ux-infra_services","v9.1.0"],"title":"Disable `allowAbsoluteUrls` for axios","number":215138,"url":"https://github.com/elastic/kibana/pull/215138","mergeCommit":{"message":"Disable `allowAbsoluteUrls` for axios (#215138)\n\n## Summary\nAfter https://github.com/elastic/kibana/pull/214843, `axios` client\nusages need to set a flag to prevent the vulnerable behavior.\n\nTo reviewers: if you think it's a mistake, and you created a client to\nrequest for absolute URLs, consider unsetting the `baseURL` to\ncommunicate intent.","sha":"e40b17aa22ec1a2fbc56ae8651e12f658099ec14"}},"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/215138","number":215138,"mergeCommit":{"message":"Disable `allowAbsoluteUrls` for axios (#215138)\n\n## Summary\nAfter https://github.com/elastic/kibana/pull/214843, `axios` client\nusages need to set a flag to prevent the vulnerable behavior.\n\nTo reviewers: if you think it's a mistake, and you created a client to\nrequest for absolute URLs, consider unsetting the `baseURL` to\ncommunicate intent.","sha":"e40b17aa22ec1a2fbc56ae8651e12f658099ec14"}}]}] BACKPORT--> --------- Co-authored-by: Alex Szabo <alex.szabo@elastic.co> |
||
|
Kibana Machine
|
69d525811a
|
[8.16] Upgrade axios 1.8.3 in buildkite (#215656) (#215886)
# Backport This will backport the following commits from `main` to `8.16`: - [Upgrade axios 1.8.3 in buildkite (#215656)](https://github.com/elastic/kibana/pull/215656) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-03-25T14:05:37Z","message":"Upgrade axios 1.8.3 in buildkite (#215656)\n\n## Summary\nAccording to:\n\nhttps://buildkite.com/elastic/kibana-on-merge/builds/65027#0195ca29-b10a-4e20-b00f-c4fbe43689fa\n\n```\n\nAnnotate test failures error Request failed with status code 404 AxiosError: Request failed with status code 404\n--\n | at settle (/opt/buildkite-agent/builds/bk-agent-prod-gcp-1742853500882456889/elastic/kibana-on-merge/kibana/.buildkite/node_modules/axios/lib/core/settle.js:19:12)\n...\n | at async /opt/buildkite-agent/builds/bk-agent-prod-gcp-1742853500882456889/elastic/kibana-on-merge/kibana/.buildkite/scripts/lifecycle/annotate_test_failures.ts:14:5\n | HTTP Error 404/Not Found (https://api.buildkite.com/v2/organizations/elastic/pipelines/kibana-on-merge/builds/65027/artifacts?page=2&per_page=100) { message: 'Not Found' }\n\n```\nThis points to the client collecting all artifacts through traversing\nthe `next` links from Buildkite's API responses. It appears, Axios is\nnot happy about these absolute paths, even if the origin is the same.\n\nThis PR adjusts the next link parsing to relativize compared to a base\nurl.","sha":"115ec32eec93fde71632f34f914b222d44eb1bbe","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","v9.1.0"],"title":"Upgrade axios 1.8.3 in buildkite","number":215656,"url":"https://github.com/elastic/kibana/pull/215656","mergeCommit":{"message":"Upgrade axios 1.8.3 in buildkite (#215656)\n\n## Summary\nAccording to:\n\nhttps://buildkite.com/elastic/kibana-on-merge/builds/65027#0195ca29-b10a-4e20-b00f-c4fbe43689fa\n\n```\n\nAnnotate test failures error Request failed with status code 404 AxiosError: Request failed with status code 404\n--\n | at settle (/opt/buildkite-agent/builds/bk-agent-prod-gcp-1742853500882456889/elastic/kibana-on-merge/kibana/.buildkite/node_modules/axios/lib/core/settle.js:19:12)\n...\n | at async /opt/buildkite-agent/builds/bk-agent-prod-gcp-1742853500882456889/elastic/kibana-on-merge/kibana/.buildkite/scripts/lifecycle/annotate_test_failures.ts:14:5\n | HTTP Error 404/Not Found (https://api.buildkite.com/v2/organizations/elastic/pipelines/kibana-on-merge/builds/65027/artifacts?page=2&per_page=100) { message: 'Not Found' }\n\n```\nThis points to the client collecting all artifacts through traversing\nthe `next` links from Buildkite's API responses. It appears, Axios is\nnot happy about these absolute paths, even if the origin is the same.\n\nThis PR adjusts the next link parsing to relativize compared to a base\nurl.","sha":"115ec32eec93fde71632f34f914b222d44eb1bbe"}},"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/215656","number":215656,"mergeCommit":{"message":"Upgrade axios 1.8.3 in buildkite (#215656)\n\n## Summary\nAccording to:\n\nhttps://buildkite.com/elastic/kibana-on-merge/builds/65027#0195ca29-b10a-4e20-b00f-c4fbe43689fa\n\n```\n\nAnnotate test failures error Request failed with status code 404 AxiosError: Request failed with status code 404\n--\n | at settle (/opt/buildkite-agent/builds/bk-agent-prod-gcp-1742853500882456889/elastic/kibana-on-merge/kibana/.buildkite/node_modules/axios/lib/core/settle.js:19:12)\n...\n | at async /opt/buildkite-agent/builds/bk-agent-prod-gcp-1742853500882456889/elastic/kibana-on-merge/kibana/.buildkite/scripts/lifecycle/annotate_test_failures.ts:14:5\n | HTTP Error 404/Not Found (https://api.buildkite.com/v2/organizations/elastic/pipelines/kibana-on-merge/builds/65027/artifacts?page=2&per_page=100) { message: 'Not Found' }\n\n```\nThis points to the client collecting all artifacts through traversing\nthe `next` links from Buildkite's API responses. It appears, Axios is\nnot happy about these absolute paths, even if the origin is the same.\n\nThis PR adjusts the next link parsing to relativize compared to a base\nurl.","sha":"115ec32eec93fde71632f34f914b222d44eb1bbe"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <alex.szabo@elastic.co> |
||
|
Kibana Machine
|
5fae0523ef
|
[8.16] [Visualize] Unskip smoke test (#214960) (#215835)
# Backport This will backport the following commits from `main` to `8.16`: - [[Visualize] Unskip smoke test (#214960)](https://github.com/elastic/kibana/pull/214960) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Vettorello","email":"marco.vettorello@elastic.co"},"sourceCommit":{"committedDate":"2025-03-25T09:30:07Z","message":"[Visualize] Unskip smoke test (#214960)\n\n## Summary\n\nUnskipping and fixing skipped test\n\nThe reported issue was referring to an issue with a TSVB chart that was\ntrying to load a missing data view.\nIf not explicitly configured in the configuration, TSVB can load the\ndefault data view configured in the Advanced Settings.\nThere is no mention of the missing dataview ID in the the dashboard nor\nin the TSVB panel configuration.\nThe TSVB configuration uses at this point the default index coming from\nthe Advanced Settings, so that ID seems to be configured as the default\nID but there is no loaded dataview with that name.\nThe data view ID appearing in the error was referencing the ecommerce\ndashboard, that was not used and not loaded in this test (all charts\nrefers to the logs* data view).\n\n\n\n\nI believe this issues was caused by other tests in the same suite/config\nthat configured the `defaultIndex` setting without unsetting it.","sha":"12aa3fc6ca8124db8cf5e940baec121482fd1a4b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","Team:Visualizations","skipped-test","release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Visualize] Unskip smoke test","number":214960,"url":"https://github.com/elastic/kibana/pull/214960","mergeCommit":{"message":"[Visualize] Unskip smoke test (#214960)\n\n## Summary\n\nUnskipping and fixing skipped test\n\nThe reported issue was referring to an issue with a TSVB chart that was\ntrying to load a missing data view.\nIf not explicitly configured in the configuration, TSVB can load the\ndefault data view configured in the Advanced Settings.\nThere is no mention of the missing dataview ID in the the dashboard nor\nin the TSVB panel configuration.\nThe TSVB configuration uses at this point the default index coming from\nthe Advanced Settings, so that ID seems to be configured as the default\nID but there is no loaded dataview with that name.\nThe data view ID appearing in the error was referencing the ecommerce\ndashboard, that was not used and not loaded in this test (all charts\nrefers to the logs* data view).\n\n\n\n\nI believe this issues was caused by other tests in the same suite/config\nthat configured the `defaultIndex` setting without unsetting it.","sha":"12aa3fc6ca8124db8cf5e940baec121482fd1a4b"}},"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/214960","number":214960,"mergeCommit":{"message":"[Visualize] Unskip smoke test (#214960)\n\n## Summary\n\nUnskipping and fixing skipped test\n\nThe reported issue was referring to an issue with a TSVB chart that was\ntrying to load a missing data view.\nIf not explicitly configured in the configuration, TSVB can load the\ndefault data view configured in the Advanced Settings.\nThere is no mention of the missing dataview ID in the the dashboard nor\nin the TSVB panel configuration.\nThe TSVB configuration uses at this point the default index coming from\nthe Advanced Settings, so that ID seems to be configured as the default\nID but there is no loaded dataview with that name.\nThe data view ID appearing in the error was referencing the ecommerce\ndashboard, that was not used and not loaded in this test (all charts\nrefers to the logs* data view).\n\n\n\n\nI believe this issues was caused by other tests in the same suite/config\nthat configured the `defaultIndex` setting without unsetting it.","sha":"12aa3fc6ca8124db8cf5e940baec121482fd1a4b"}}]}] BACKPORT--> Co-authored-by: Marco Vettorello <marco.vettorello@elastic.co> |
||
Gerard Soldevila
|
7be26238c2
|
[8.16] Fix plugin list for 8.x (asciidoc-based) docs (#215671) (#215708)
# Backport This will backport the following commits from `8.x` to `8.16`: - [Fix plugin list for 8.x (asciidoc-based) docs (#215671)](https://github.com/elastic/kibana/pull/215671) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T13:33:38Z","message":"Fix plugin list for 8.x (asciidoc-based) docs (#215671)\n\n## Summary\n\nApply the same fixes as https://github.com/elastic/kibana/pull/215648,\nbut for 8.x series.","sha":"35f17542d096452067bf792d99ed60fc0c981759","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","backport:all-open"],"title":"Fix plugin list for 8.x (asciidoc-based) docs","number":215671,"url":"https://github.com/elastic/kibana/pull/215671","mergeCommit":{"message":"Fix plugin list for 8.x (asciidoc-based) docs (#215671)\n\n## Summary\n\nApply the same fixes as https://github.com/elastic/kibana/pull/215648,\nbut for 8.x series.","sha":"35f17542d096452067bf792d99ed60fc0c981759"}},"sourceBranch":"8.x","suggestedTargetBranches":[],"targetPullRequestStates":[]}] BACKPORT--> |
||
Julia Bardi
|
6272be63eb
|
[8.16][Fleet] fix schema validation when updating package policy (#214770)
Backport https://github.com/elastic/kibana/pull/214571 --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
52d1c98c9f
|
[8.16] [ci] More info to test annotation failure logging (#215515) (#215781)
# Backport This will backport the following commits from `main` to `8.16`: - [[ci] More info to test annotation failure logging (#215515)](https://github.com/elastic/kibana/pull/215515) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T18:01:32Z","message":"[ci] More info to test annotation failure logging (#215515)\n\n## Summary\nWhile annotating test failures, we're seeing increased amount of errors\nlike this:\n```\n2025-03-21 13:52:32 INFO Artifact uploads completed successfully\n--\n | Annotate test failures error Request failed with status code 404\n | HTTP Error Response Status 404\n | HTTP Error Response Body { message: 'Not Found' }\n | user command error: exit status 10\n```\n\nIt would be nicer to show a bit more from the error to help debugging.","sha":"7120074ec32dcf693580244a01475a2af065a33d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","skip-ci","backport:all-open","v9.1.0"],"title":"[ci] More info to test annotation failure logging","number":215515,"url":"https://github.com/elastic/kibana/pull/215515","mergeCommit":{"message":"[ci] More info to test annotation failure logging (#215515)\n\n## Summary\nWhile annotating test failures, we're seeing increased amount of errors\nlike this:\n```\n2025-03-21 13:52:32 INFO Artifact uploads completed successfully\n--\n | Annotate test failures error Request failed with status code 404\n | HTTP Error Response Status 404\n | HTTP Error Response Body { message: 'Not Found' }\n | user command error: exit status 10\n```\n\nIt would be nicer to show a bit more from the error to help debugging.","sha":"7120074ec32dcf693580244a01475a2af065a33d"}},"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/215515","number":215515,"mergeCommit":{"message":"[ci] More info to test annotation failure logging (#215515)\n\n## Summary\nWhile annotating test failures, we're seeing increased amount of errors\nlike this:\n```\n2025-03-21 13:52:32 INFO Artifact uploads completed successfully\n--\n | Annotate test failures error Request failed with status code 404\n | HTTP Error Response Status 404\n | HTTP Error Response Body { message: 'Not Found' }\n | user command error: exit status 10\n```\n\nIt would be nicer to show a bit more from the error to help debugging.","sha":"7120074ec32dcf693580244a01475a2af065a33d"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <alex.szabo@elastic.co> |
||
|
Kibana Machine
|
b0bb198524
|
[8.16] [Oblt Onboarding][K8S OTel] Use helm upgrade --install (#215160) (#215679)
# Backport This will backport the following commits from `main` to `8.16`: - [[Oblt Onboarding][K8S OTel] Use helm upgrade --install (#215160)](https://github.com/elastic/kibana/pull/215160) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2025-03-24T12:20:45Z","message":"[Oblt Onboarding][K8S OTel] Use helm upgrade --install (#215160)\n\nCloses #215134\n\nUsing `helm upgrade --install` lets the user run the helm command\nmultiple times to, for example, upgrade to the new version after a stack\nrelease.\n\n\n\n## How to test\n\n1. Run Kibana and navigate to the K8S OTel onboarding flow\n2. Execute snippets provided by the flow\n3. Copy only the `helm upgrade --install ...` part of the second snippet\nand execute it again\n4. Make sure the command succeeds\n\nCo-authored-by: Joe Reuter <johannes.reuter@elastic.co>","sha":"007caa1b55b6bf47dc852aa2c38cd77ff1753d0e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-major","ci:project-deploy-observability","Feature: Observability Onboarding","v9.1.0"],"title":"[Oblt Onboarding][K8S OTel] Use helm upgrade --install","number":215160,"url":"https://github.com/elastic/kibana/pull/215160","mergeCommit":{"message":"[Oblt Onboarding][K8S OTel] Use helm upgrade --install (#215160)\n\nCloses #215134\n\nUsing `helm upgrade --install` lets the user run the helm command\nmultiple times to, for example, upgrade to the new version after a stack\nrelease.\n\n\n\n## How to test\n\n1. Run Kibana and navigate to the K8S OTel onboarding flow\n2. Execute snippets provided by the flow\n3. Copy only the `helm upgrade --install ...` part of the second snippet\nand execute it again\n4. Make sure the command succeeds\n\nCo-authored-by: Joe Reuter <johannes.reuter@elastic.co>","sha":"007caa1b55b6bf47dc852aa2c38cd77ff1753d0e"}},"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/215160","number":215160,"mergeCommit":{"message":"[Oblt Onboarding][K8S OTel] Use helm upgrade --install (#215160)\n\nCloses #215134\n\nUsing `helm upgrade --install` lets the user run the helm command\nmultiple times to, for example, upgrade to the new version after a stack\nrelease.\n\n\n\n## How to test\n\n1. Run Kibana and navigate to the K8S OTel onboarding flow\n2. Execute snippets provided by the flow\n3. Copy only the `helm upgrade --install ...` part of the second snippet\nand execute it again\n4. Make sure the command succeeds\n\nCo-authored-by: Joe Reuter <johannes.reuter@elastic.co>","sha":"007caa1b55b6bf47dc852aa2c38cd77ff1753d0e"}}]}] BACKPORT--> Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com> |
||
jennypavlova
|
6f81d4570c
|
[8.16] [APM] Fix: Add missing user_agent version field and show it on the trace summary (#215403) (#215556)
# Backport This will backport the following commits from `main` to `8.16`: - [[APM] Fix: Add missing user_agent version field and show it on the trace summary (#215403)](https://github.com/elastic/kibana/pull/215403) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T17:33:01Z","message":"[APM] Fix: Add missing user_agent version field and show it on the trace summary (#215403)\n\nCloses #215229 \n\n## Summary\n\nThis PR adds the `USER_AGENT_VERSION` missing field to the\n`optionalFields` query fields\n\n## Testing\n\n- Find a trace with user agent version (on the edge oblt we have it for\n`elastic-co-frontend` for example)\n- Go to the transaction tab (in case of `elastic-co-frontend` click on\n`/blog/:id`)\nIf the user agent version is available it should be visible in the trace\nsummary:\n\n<img width=\"1155\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/75b7e331-44d0-4d1c-8060-815c269e23c9\"\n/>","sha":"42a66131c529ff3f48a037abd40fef118a09d248","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:obs-ux-infra_services","v9.1.0"],"title":"[APM] Fix: Add missing user_agent version field and show it on the trace summary","number":215403,"url":"https://github.com/elastic/kibana/pull/215403","mergeCommit":{"message":"[APM] Fix: Add missing user_agent version field and show it on the trace summary (#215403)\n\nCloses #215229 \n\n## Summary\n\nThis PR adds the `USER_AGENT_VERSION` missing field to the\n`optionalFields` query fields\n\n## Testing\n\n- Find a trace with user agent version (on the edge oblt we have it for\n`elastic-co-frontend` for example)\n- Go to the transaction tab (in case of `elastic-co-frontend` click on\n`/blog/:id`)\nIf the user agent version is available it should be visible in the trace\nsummary:\n\n<img width=\"1155\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/75b7e331-44d0-4d1c-8060-815c269e23c9\"\n/>","sha":"42a66131c529ff3f48a037abd40fef118a09d248"}},"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/215403","number":215403,"mergeCommit":{"message":"[APM] Fix: Add missing user_agent version field and show it on the trace summary (#215403)\n\nCloses #215229 \n\n## Summary\n\nThis PR adds the `USER_AGENT_VERSION` missing field to the\n`optionalFields` query fields\n\n## Testing\n\n- Find a trace with user agent version (on the edge oblt we have it for\n`elastic-co-frontend` for example)\n- Go to the transaction tab (in case of `elastic-co-frontend` click on\n`/blog/:id`)\nIf the user agent version is available it should be visible in the trace\nsummary:\n\n<img width=\"1155\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/75b7e331-44d0-4d1c-8060-815c269e23c9\"\n/>","sha":"42a66131c529ff3f48a037abd40fef118a09d248"}}]}] BACKPORT--> |
||
Jeramy Soucy
|
d643a0533d
|
[8.16] Update dependency @openfeature/launchdarkly-client-provider to ^0.3.2 (main) (#215232) (#215653)
# Backport This will backport the following commits from `main` to `8.16`: - [Update dependency @openfeature/launchdarkly-client-provider to ^0.3.2 (main) (#215232)](https://github.com/elastic/kibana/pull/215232) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-21T06:57:46Z","message":"Update dependency @openfeature/launchdarkly-client-provider to ^0.3.2 (main) (#215232)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| @​openfeature/launchdarkly-client-provider | dependencies |\npatch | [`^0.3.1` ->\n`^0.3.2`](https://renovatebot.com/diffs/npm/@openfeature%2flaunchdarkly-client-provider/0.3.1/0.3.2)\n|\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"933564d713c3f6c090702cdca97a76073d437419","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","Team:Security","release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"Update dependency @openfeature/launchdarkly-client-provider to ^0.3.2 (main)","number":215232,"url":"https://github.com/elastic/kibana/pull/215232","mergeCommit":{"message":"Update dependency @openfeature/launchdarkly-client-provider to ^0.3.2 (main) (#215232)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| @​openfeature/launchdarkly-client-provider | dependencies |\npatch | [`^0.3.1` ->\n`^0.3.2`](https://renovatebot.com/diffs/npm/@openfeature%2flaunchdarkly-client-provider/0.3.1/0.3.2)\n|\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"933564d713c3f6c090702cdca97a76073d437419"}},"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/215436","number":215436,"state":"MERGED","mergeCommit":{"sha":"85c22772361fd4821f0b9c5acd7e281353e9594d","message":"[9.0] Update dependency @openfeature/launchdarkly-client-provider to ^0.3.2 (main) (#215232) (#215436)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [Update dependency @openfeature/launchdarkly-client-provider to ^0.3.2\n(main) (#215232)](https://github.com/elastic/kibana/pull/215232)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215232","number":215232,"mergeCommit":{"message":"Update dependency @openfeature/launchdarkly-client-provider to ^0.3.2 (main) (#215232)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| @​openfeature/launchdarkly-client-provider | dependencies |\npatch | [`^0.3.1` ->\n`^0.3.2`](https://renovatebot.com/diffs/npm/@openfeature%2flaunchdarkly-client-provider/0.3.1/0.3.2)\n|\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"933564d713c3f6c090702cdca97a76073d437419"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
520a8658d7
|
[8.16] Register resident set size and limit bytes metrics in APM (#215458) (#215613)
# Backport This will backport the following commits from `main` to `8.16`: - [Register resident set size and limit bytes metrics in APM (#215458)](https://github.com/elastic/kibana/pull/215458) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jesus Wahrman","email":"41008968+jesuswr@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-23T21:22:30Z","message":"Register resident set size and limit bytes metrics in APM (#215458)\n\n## Summary\n\nResolves https://github.com/elastic/kibana-team/issues/1565\n\nRegister resident set size and limit bytes metrics in APM.\n\n<img width=\"1614\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d5f1caf5-da4f-4acd-a63f-2b5256a91307\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"04772fcc456aa6b03d9ecec540cc927c23c0dd9a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-major","backport:current-major","v9.1.0"],"title":"Register resident set size and limit bytes metrics in APM","number":215458,"url":"https://github.com/elastic/kibana/pull/215458","mergeCommit":{"message":"Register resident set size and limit bytes metrics in APM (#215458)\n\n## Summary\n\nResolves https://github.com/elastic/kibana-team/issues/1565\n\nRegister resident set size and limit bytes metrics in APM.\n\n<img width=\"1614\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d5f1caf5-da4f-4acd-a63f-2b5256a91307\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"04772fcc456aa6b03d9ecec540cc927c23c0dd9a"}},"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/215458","number":215458,"mergeCommit":{"message":"Register resident set size and limit bytes metrics in APM (#215458)\n\n## Summary\n\nResolves https://github.com/elastic/kibana-team/issues/1565\n\nRegister resident set size and limit bytes metrics in APM.\n\n<img width=\"1614\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d5f1caf5-da4f-4acd-a63f-2b5256a91307\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"04772fcc456aa6b03d9ecec540cc927c23c0dd9a"}}]}] BACKPORT--> Co-authored-by: Jesus Wahrman <41008968+jesuswr@users.noreply.github.com> |
||
|
Kibana Machine
|
cbe918e295
|
[8.16] [Lens] fix drag and drop ghost after Chrome update to 134 (#213928) (#214123)
# Backport This will backport the following commits from `main` to `8.16`: - https://github.com/elastic/kibana/pull/213928 - https://github.com/elastic/kibana/pull/215439 <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marta Bondyra","email":"4283304+mbondyra@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-12T11:30:51Z","message":"[Lens] fix drag and drop ghost after Chrome update to 134 (#213928)\n\n## Summary\nFixes https://github.com/elastic/kibana/issues/213708\n\nFixes the ghost display. As @nickofthyme pointed out\n[here](https://github.com/elastic/kibana/issues/213708#issuecomment-2712076212),\nthe reason was using inset-inline-start: -10000px for the keyboard\nhandler that is one of the children of the draggable component. The\nquick fix is to just move it outside of the html element that is\ndragged. @markov00 please assesswhere it should be merged 🙏🏼\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"84ae9c98c208957b3efc02c6b00bed8d567d4209","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","Team:Visualizations","Feature:Lens","backport:prev-minor","backport:prev-major","Feature:UnifiedFieldList","v9.1.0"],"title":"[Lens] fix drag and drop ghost after Chrome update to 134","number":213928,"url":"https://github.com/elastic/kibana/pull/213928","mergeCommit":{"message":"[Lens] fix drag and drop ghost after Chrome update to 134 (#213928)\n\n## Summary\nFixes https://github.com/elastic/kibana/issues/213708\n\nFixes the ghost display. As @nickofthyme pointed out\n[here](https://github.com/elastic/kibana/issues/213708#issuecomment-2712076212),\nthe reason was using inset-inline-start: -10000px for the keyboard\nhandler that is one of the children of the draggable component. The\nquick fix is to just move it outside of the html element that is\ndragged. @markov00 please assesswhere it should be merged 🙏🏼\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"84ae9c98c208957b3efc02c6b00bed8d567d4209"}},"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/213928","number":213928,"mergeCommit":{"message":"[Lens] fix drag and drop ghost after Chrome update to 134 (#213928)\n\n## Summary\nFixes https://github.com/elastic/kibana/issues/213708\n\nFixes the ghost display. As @nickofthyme pointed out\n[here](https://github.com/elastic/kibana/issues/213708#issuecomment-2712076212),\nthe reason was using inset-inline-start: -10000px for the keyboard\nhandler that is one of the children of the draggable component. The\nquick fix is to just move it outside of the html element that is\ndragged. @markov00 please assesswhere it should be merged 🙏🏼\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"84ae9c98c208957b3efc02c6b00bed8d567d4209"}}]}] BACKPORT--> --------- Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com> Co-authored-by: Nick Partridge <nicholas.partridge@elastic.co> |
||
wajihaparvez
|
4c20ac689e
|
Backport 8.16.6 release notes to 8.16 (#215570)
## Summary This PR backports https://github.com/elastic/kibana/pull/215252 to 8.16. |
||
|
Kibana Machine
|
2d13929ba9
|
[8.16] [Search Profiler] Index field no longer resets on query edit (#215420) (#215496)
# Backport This will backport the following commits from `main` to `8.16`: - [[Search Profiler] Index field no longer resets on query edit (#215420)](https://github.com/elastic/kibana/pull/215420) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Matthew Kime","email":"matt@mattki.me"},"sourceCommit":{"committedDate":"2025-03-21T13:29:33Z","message":"[Search Profiler] Index field no longer resets on query edit (#215420)\n\n## Summary\n\nPreviously, editing the query would reset the index field to `_all`.\nThis was due to using `useState` instead of `useRef` to store the query\nvalue.\n\nCloses https://github.com/elastic/kibana/issues/214416\n\nHow to test\n1. Go to search profiler\n2. Enter an index name, anything but `_all` - which is already there\n3. Edit the query\n4. Did the index value remain unchanged? Good! Its fixed!\n\nALSO - need to test to make sure this works with content in the url.","sha":"f77e29f5827c621d29959cbbf8514ce497565263","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Kibana Management","Feature:Search Profiler","backport:prev-major","v9.1.0"],"title":"[Search Profiler] Index field no longer resets on query edit","number":215420,"url":"https://github.com/elastic/kibana/pull/215420","mergeCommit":{"message":"[Search Profiler] Index field no longer resets on query edit (#215420)\n\n## Summary\n\nPreviously, editing the query would reset the index field to `_all`.\nThis was due to using `useState` instead of `useRef` to store the query\nvalue.\n\nCloses https://github.com/elastic/kibana/issues/214416\n\nHow to test\n1. Go to search profiler\n2. Enter an index name, anything but `_all` - which is already there\n3. Edit the query\n4. Did the index value remain unchanged? Good! Its fixed!\n\nALSO - need to test to make sure this works with content in the url.","sha":"f77e29f5827c621d29959cbbf8514ce497565263"}},"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/215420","number":215420,"mergeCommit":{"message":"[Search Profiler] Index field no longer resets on query edit (#215420)\n\n## Summary\n\nPreviously, editing the query would reset the index field to `_all`.\nThis was due to using `useState` instead of `useRef` to store the query\nvalue.\n\nCloses https://github.com/elastic/kibana/issues/214416\n\nHow to test\n1. Go to search profiler\n2. Enter an index name, anything but `_all` - which is already there\n3. Edit the query\n4. Did the index value remain unchanged? Good! Its fixed!\n\nALSO - need to test to make sure this works with content in the url.","sha":"f77e29f5827c621d29959cbbf8514ce497565263"}}]}] BACKPORT--> Co-authored-by: Matthew Kime <matt@mattki.me> |
||
|
Kibana Machine
|
4872b3d560
|
[8.16] Hide the chrome popup about leaked passwords (#215414) (#215477)
# Backport This will backport the following commits from `main` to `8.16`: - [Hide the chrome popup about leaked passwords (#215414)](https://github.com/elastic/kibana/pull/215414) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Kurt","email":"kc13greiner@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-21T12:04:25Z","message":"Hide the chrome popup about leaked passwords (#215414)\n\n## Summary\nCloses https://github.com/elastic/kibana/issues/214355\n\nTesting with Chrome 135.x.x.x resulted in a pop up that was breaking the\nflow of tests:\n\n<img width=\"470\" alt=\"Screenshot 2025-03-20 at 4 25 17 PM\"\nsrc=\"https://github.com/user-attachments/assets/df908294-1881-4b6d-b9a2-3027b37b06ad\"\n/>\n\nThis isn't captured by the screenshotting plugin, but is visible if you\nrun `headless=0`\n\nThis adds the config to disable that popup since our generic testing\npasswords are very common and therefor flagged","sha":"f5cebe2c23dff4454ec948358cc0a938400d5ede","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Security","release_note:skip","backport:all-open","v9.1.0"],"title":"Hide the chrome popup about leaked passwords","number":215414,"url":"https://github.com/elastic/kibana/pull/215414","mergeCommit":{"message":"Hide the chrome popup about leaked passwords (#215414)\n\n## Summary\nCloses https://github.com/elastic/kibana/issues/214355\n\nTesting with Chrome 135.x.x.x resulted in a pop up that was breaking the\nflow of tests:\n\n<img width=\"470\" alt=\"Screenshot 2025-03-20 at 4 25 17 PM\"\nsrc=\"https://github.com/user-attachments/assets/df908294-1881-4b6d-b9a2-3027b37b06ad\"\n/>\n\nThis isn't captured by the screenshotting plugin, but is visible if you\nrun `headless=0`\n\nThis adds the config to disable that popup since our generic testing\npasswords are very common and therefor flagged","sha":"f5cebe2c23dff4454ec948358cc0a938400d5ede"}},"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/215414","number":215414,"mergeCommit":{"message":"Hide the chrome popup about leaked passwords (#215414)\n\n## Summary\nCloses https://github.com/elastic/kibana/issues/214355\n\nTesting with Chrome 135.x.x.x resulted in a pop up that was breaking the\nflow of tests:\n\n<img width=\"470\" alt=\"Screenshot 2025-03-20 at 4 25 17 PM\"\nsrc=\"https://github.com/user-attachments/assets/df908294-1881-4b6d-b9a2-3027b37b06ad\"\n/>\n\nThis isn't captured by the screenshotting plugin, but is visible if you\nrun `headless=0`\n\nThis adds the config to disable that popup since our generic testing\npasswords are very common and therefor flagged","sha":"f5cebe2c23dff4454ec948358cc0a938400d5ede"}}]}] BACKPORT--> Co-authored-by: Kurt <kc13greiner@users.noreply.github.com> |
||
|
Kibana Machine
|
5c7faae742
|
[8.16] [ResponseOps] Snooze Scheduler UX for recurring snoozes shows incorrect summary (#214797) (#215463)
# Backport This will backport the following commits from `main` to `8.16`: - [[ResponseOps] Snooze Scheduler UX for recurring snoozes shows incorrect summary (#214797)](https://github.com/elastic/kibana/pull/214797) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia","email":"iuliia.guskova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T10:47:28Z","message":"[ResponseOps] Snooze Scheduler UX for recurring snoozes shows incorrect summary (#214797)\n\nSolves: https://github.com/elastic/kibana/issues/210119\n\n## Summary\n\nHow to test:\nReproduce bug from an issue. But create a rule in Stack management.\nAction is not needed. You can test it on main.\n\n\n\n\nWhen you add new schedule and save it, you should see proper date here\nas well:\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] [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":"fdd872ada18ce7255cfac396a26dab46d9282dcb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","backport:version","v9.1.0","v8.19.0","v8.18.1","v8.16.6","v8.17.4"],"title":"[ResponseOps] Snooze Scheduler UX for recurring snoozes shows incorrect summary ","number":214797,"url":"https://github.com/elastic/kibana/pull/214797","mergeCommit":{"message":"[ResponseOps] Snooze Scheduler UX for recurring snoozes shows incorrect summary (#214797)\n\nSolves: https://github.com/elastic/kibana/issues/210119\n\n## Summary\n\nHow to test:\nReproduce bug from an issue. But create a rule in Stack management.\nAction is not needed. You can test it on main.\n\n\n\n\nWhen you add new schedule and save it, you should see proper date here\nas well:\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] [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":"fdd872ada18ce7255cfac396a26dab46d9282dcb"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214797","number":214797,"mergeCommit":{"message":"[ResponseOps] Snooze Scheduler UX for recurring snoozes shows incorrect summary (#214797)\n\nSolves: https://github.com/elastic/kibana/issues/210119\n\n## Summary\n\nHow to test:\nReproduce bug from an issue. But create a rule in Stack management.\nAction is not needed. You can test it on main.\n\n\n\n\nWhen you add new schedule and save it, you should see proper date here\nas well:\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] [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":"fdd872ada18ce7255cfac396a26dab46d9282dcb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia <iuliia.guskova@elastic.co> |
||
Alex Szabo
|
17b586094b
|
[8.16] [CI] Only emit .d.ts when running typecheck (#209259) (#215308)
# Backport This will backport the following commits from `main` to `8.16`: - [[CI] Only emit .d.ts when running typecheck (#209259)](https://github.com/elastic/kibana/pull/209259) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T10:48:14Z","message":"[CI] Only emit .d.ts when running typecheck (#209259)\n\n## Summary\nStop emitting any `.js` files during typechecking. We only depend on the\ndeclarations, not the emitted, compiled javascript files.\n\nAn added benefit, is making some bad import errors more obvious. \nWe'll no longer try to build javascript files in place if a poor\nimport/require is made, rather the error of importing outside projects\n(in the forest of a bunch of errors possibly) will be visible in the\ntypescript logs:\n```\n# instead of:\nproc [tsc] error TS5055: Cannot write file '/opt/buildkite-agent/builds/bk-agent-prod-gcp-1741789017236110254/elastic/kibana-pull-request/kibana/src/platform/packages/shared/kbn-babel-register/cache/no_cache_cache.js' because it would overwrite input file.\n\n# we'll see:\n... several others like this\n proc [tsc] src/platform/packages/shared/kbn-grok-ui/scripts/generate_patterns.js:10:9 - error TS6307: File '/Users/alex/Git/elastic-kibana/src/setup_node_env/index.js' is not listed within the file list of project '/Users/alex/Git/elastic-kibana/src/platform/packages/shared/kbn-grok-ui/tsconfig.type_check.json'. Projects must list all files or use an 'include' pattern.\n proc [tsc] \n proc [tsc] 10 require('../../../../../setup_node_env');\n... several others like this\n```","sha":"702c9c49dcbc9036af80ba5473c961cf96573030","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","v9.0.0","backport:all-open","v8.18.0","v9.1.0","v8.19.0"],"title":"[CI] Only emit .d.ts when running typecheck","number":209259,"url":"https://github.com/elastic/kibana/pull/209259","mergeCommit":{"message":"[CI] Only emit .d.ts when running typecheck (#209259)\n\n## Summary\nStop emitting any `.js` files during typechecking. We only depend on the\ndeclarations, not the emitted, compiled javascript files.\n\nAn added benefit, is making some bad import errors more obvious. \nWe'll no longer try to build javascript files in place if a poor\nimport/require is made, rather the error of importing outside projects\n(in the forest of a bunch of errors possibly) will be visible in the\ntypescript logs:\n```\n# instead of:\nproc [tsc] error TS5055: Cannot write file '/opt/buildkite-agent/builds/bk-agent-prod-gcp-1741789017236110254/elastic/kibana-pull-request/kibana/src/platform/packages/shared/kbn-babel-register/cache/no_cache_cache.js' because it would overwrite input file.\n\n# we'll see:\n... several others like this\n proc [tsc] src/platform/packages/shared/kbn-grok-ui/scripts/generate_patterns.js:10:9 - error TS6307: File '/Users/alex/Git/elastic-kibana/src/setup_node_env/index.js' is not listed within the file list of project '/Users/alex/Git/elastic-kibana/src/platform/packages/shared/kbn-grok-ui/tsconfig.type_check.json'. Projects must list all files or use an 'include' pattern.\n proc [tsc] \n proc [tsc] 10 require('../../../../../setup_node_env');\n... several others like this\n```","sha":"702c9c49dcbc9036af80ba5473c961cf96573030"}},"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/214944","number":214944,"state":"MERGED","mergeCommit":{"sha":"bc32304513a6315a89cb0644ad1f41343199e9c1","message":"[9.0] [CI] Only emit .d.ts when running typecheck (#209259) (#214944)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[CI] Only emit .d.ts when running typecheck\n(#209259)](https://github.com/elastic/kibana/pull/209259)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Alex Szabo <alex.szabo@elastic.co>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214942","number":214942,"state":"MERGED","mergeCommit":{"sha":"3f9d5f4d210fb38a72e1b9cc3ba1af53e354504a","message":"[8.18] [CI] Only emit .d.ts when running typecheck (#209259) (#214942)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[CI] Only emit .d.ts when running typecheck\n(#209259)](https://github.com/elastic/kibana/pull/209259)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Alex Szabo <alex.szabo@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209259","number":209259,"mergeCommit":{"message":"[CI] Only emit .d.ts when running typecheck (#209259)\n\n## Summary\nStop emitting any `.js` files during typechecking. We only depend on the\ndeclarations, not the emitted, compiled javascript files.\n\nAn added benefit, is making some bad import errors more obvious. \nWe'll no longer try to build javascript files in place if a poor\nimport/require is made, rather the error of importing outside projects\n(in the forest of a bunch of errors possibly) will be visible in the\ntypescript logs:\n```\n# instead of:\nproc [tsc] error TS5055: Cannot write file '/opt/buildkite-agent/builds/bk-agent-prod-gcp-1741789017236110254/elastic/kibana-pull-request/kibana/src/platform/packages/shared/kbn-babel-register/cache/no_cache_cache.js' because it would overwrite input file.\n\n# we'll see:\n... several others like this\n proc [tsc] src/platform/packages/shared/kbn-grok-ui/scripts/generate_patterns.js:10:9 - error TS6307: File '/Users/alex/Git/elastic-kibana/src/setup_node_env/index.js' is not listed within the file list of project '/Users/alex/Git/elastic-kibana/src/platform/packages/shared/kbn-grok-ui/tsconfig.type_check.json'. Projects must list all files or use an 'include' pattern.\n proc [tsc] \n proc [tsc] 10 require('../../../../../setup_node_env');\n... several others like this\n```","sha":"702c9c49dcbc9036af80ba5473c961cf96573030"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214943","number":214943,"state":"MERGED","mergeCommit":{"sha":"cc35bc14b0fd76dc3c7a8d9338743c4d209706a6","message":"[8.x] [CI] Only emit .d.ts when running typecheck (#209259) (#214943)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[CI] Only emit .d.ts when running typecheck\n(#209259)](https://github.com/elastic/kibana/pull/209259)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Alex Szabo <alex.szabo@elastic.co>"}}]}] BACKPORT--> |
||
Jan Monschke
|
99e99172e6
|
[8.16] [Security Solution] Add retrieve results to security solution search strategy (#207307) (#215275)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] Add retrieve results to security solution search strategy (#207307)](https://github.com/elastic/kibana/pull/207307) <!--- Backport version: 9.6.6 --> ### 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-21T13:19:49Z","message":"[Security Solution] Add retrieve results to security solution search strategy (#207307)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/pull/189031\r\n\r\nhttps://p.elstc.co/paste/pCGQy1nV#B7fBRtGiDq-QN14qT/eE8zPOPWgXP88672NIcbSblaD\r\nWithout `options.retrieveResults = true` parameter,\r\n`response.rawResponse.hits.hits` from search strategy can be undefined\r\n\r\n### Checklist\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":"91eefe437a0ef68de34cd6f50f2a1e9cb93f6fc2","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","release_note:skip","v9.0.0","v8.18.0"],"title":"[Security Solution] Add retrieve results to security solution search strategy","number":207307,"url":"https://github.com/elastic/kibana/pull/207307","mergeCommit":{"message":"[Security Solution] Add retrieve results to security solution search strategy (#207307)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/pull/189031\r\n\r\nhttps://p.elstc.co/paste/pCGQy1nV#B7fBRtGiDq-QN14qT/eE8zPOPWgXP88672NIcbSblaD\r\nWithout `options.retrieveResults = true` parameter,\r\n`response.rawResponse.hits.hits` from search strategy can be undefined\r\n\r\n### Checklist\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":"91eefe437a0ef68de34cd6f50f2a1e9cb93f6fc2"}},"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/207307","number":207307,"mergeCommit":{"message":"[Security Solution] Add retrieve results to security solution search strategy (#207307)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/pull/189031\r\n\r\nhttps://p.elstc.co/paste/pCGQy1nV#B7fBRtGiDq-QN14qT/eE8zPOPWgXP88672NIcbSblaD\r\nWithout `options.retrieveResults = true` parameter,\r\n`response.rawResponse.hits.hits` from search strategy can be undefined\r\n\r\n### Checklist\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":"91eefe437a0ef68de34cd6f50f2a1e9cb93f6fc2"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/207353","number":207353,"state":"MERGED","mergeCommit":{"sha":"ad38e9b0a80d5417e4d3d31fe96694677fe927c7","message":"[8.x] [Security Solution] Add retrieve results to security solution search strategy (#207307) (#207353)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Solution] Add retrieve results to security solution search\nstrategy (#207307)](https://github.com/elastic/kibana/pull/207307)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Angela Chuang <6295984+angorayc@users.noreply.github.com>"}}]}] BACKPORT--> Co-authored-by: Angela Chuang <6295984+angorayc@users.noreply.github.com> |
||
|
Kibana Machine
|
1ebdc6ed49
|
[8.16] Upgrade axios 1.8.3 in buildkite (#215203) (#215294)
# Backport This will backport the following commits from `main` to `8.16`: - [Upgrade axios 1.8.3 in buildkite (#215203)](https://github.com/elastic/kibana/pull/215203) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T09:58:41Z","message":"Upgrade axios 1.8.3 in buildkite (#215203)\n\n## Summary\nUpgrade `axios` to 1.8.3 in Kibana's `.buildkite` subproject; disallow\nabsolute URLs in axios clients.","sha":"d8f6bd694b5004547623f506b3a3497bb556c2a1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","v9.1.0"],"title":"Upgrade axios 1.8.3 in buildkite","number":215203,"url":"https://github.com/elastic/kibana/pull/215203","mergeCommit":{"message":"Upgrade axios 1.8.3 in buildkite (#215203)\n\n## Summary\nUpgrade `axios` to 1.8.3 in Kibana's `.buildkite` subproject; disallow\nabsolute URLs in axios clients.","sha":"d8f6bd694b5004547623f506b3a3497bb556c2a1"}},"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/215203","number":215203,"mergeCommit":{"message":"Upgrade axios 1.8.3 in buildkite (#215203)\n\n## Summary\nUpgrade `axios` to 1.8.3 in Kibana's `.buildkite` subproject; disallow\nabsolute URLs in axios clients.","sha":"d8f6bd694b5004547623f506b3a3497bb556c2a1"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <alex.szabo@elastic.co> |
||
elastic-renovate-prod[bot]
|
39969cb4b1
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to c4e10ec (8.16) (#215081)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `5ba5def` -> `c4e10ec` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNiIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
Shahzad
|
471d9b57af
|
[8.16] [Synthetics] Use range filter instead of timespan !! (#209281) (#215109)
# Backport This will backport the following commits from `main` to `8.16`: - [[Synthetics] Monitor status rule, show to which monitors rule applies !! (#209281)](https://github.com/elastic/kibana/pull/209281) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-02-06T16:07:22Z","message":"[Synthetics] Monitor status rule, show to which monitors rule applies !! (#209281)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/198688\r\n\r\nMonitor status rule, show to which monitors rule applies !!\r\n\r\nWith filters shows to which monitors the rule applies \r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/5536ad12-d0ed-4394-a511-8dd826bf3b56\"\r\n/>\r\n\r\n\r\nAlso showing an inspect flyout with query details\r\n\r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/d441e4f9-8f0c-4fac-a2ca-5f214f8d2709\"\r\n/>","sha":"ac89e472a6156d44e098d06f3665d90f892dbdba","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:obs-ux-management","backport:version","v9.1.0","v8.19.0"],"title":"[Synthetics] Monitor status rule, show to which monitors rule applies !!","number":209281,"url":"https://github.com/elastic/kibana/pull/209281","mergeCommit":{"message":"[Synthetics] Monitor status rule, show to which monitors rule applies !! (#209281)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/198688\r\n\r\nMonitor status rule, show to which monitors rule applies !!\r\n\r\nWith filters shows to which monitors the rule applies \r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/5536ad12-d0ed-4394-a511-8dd826bf3b56\"\r\n/>\r\n\r\n\r\nAlso showing an inspect flyout with query details\r\n\r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/d441e4f9-8f0c-4fac-a2ca-5f214f8d2709\"\r\n/>","sha":"ac89e472a6156d44e098d06f3665d90f892dbdba"}},"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/210061","number":210061,"state":"MERGED","mergeCommit":{"sha":"67b17c8bbb945e918be2a44a9e44cbfe7f513815","message":"[9.0] [Synthetics] Monitor status rule, show to which monitors rule applies !! (#209281) (#210061)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Synthetics] Monitor status rule, show to which monitors rule applies\n!! (#209281)](https://github.com/elastic/kibana/pull/209281)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209281","number":209281,"mergeCommit":{"message":"[Synthetics] Monitor status rule, show to which monitors rule applies !! (#209281)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/198688\r\n\r\nMonitor status rule, show to which monitors rule applies !!\r\n\r\nWith filters shows to which monitors the rule applies \r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/5536ad12-d0ed-4394-a511-8dd826bf3b56\"\r\n/>\r\n\r\n\r\nAlso showing an inspect flyout with query details\r\n\r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/d441e4f9-8f0c-4fac-a2ca-5f214f8d2709\"\r\n/>","sha":"ac89e472a6156d44e098d06f3665d90f892dbdba"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/215097","number":215097,"state":"OPEN"}]}] BACKPORT--> |
||
|
wajihaparvez
|
cb2a7ce254
|
[Docs] Add link to dependencies page - 8.16 backport (#215019)
## Summary This PR backports https://github.com/elastic/kibana/pull/214667 to 8.16. Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> |
||
|
elastic-renovate-prod[bot]
|
cfe87bd2c5
|
Update dependency chromedriver to v134 (8.16) (#214148)
This PR contains the following updates: | Package | Type | Update | Change | Pending | |---|---|---|---|---| | [chromedriver](https://redirect.github.com/giggio/node-chromedriver) | devDependencies | major | [`^133.0.2` -> `^134.0.0`](https://renovatebot.com/diffs/npm/chromedriver/133.0.3/134.0.0) | `134.0.2` (+1) | --- ### Release Notes <details> <summary>giggio/node-chromedriver (chromedriver)</summary> ### [`v134.0.0`](https://redirect.github.com/giggio/node-chromedriver/compare/133.0.3...134.0.0) [Compare Source](https://redirect.github.com/giggio/node-chromedriver/compare/133.0.3...134.0.0) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNiIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
elastic-renovate-prod[bot]
|
76c375ed1d
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 5ba5def (8.16) (#214956)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `66d427a` -> `5ba5def` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNiIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
6c7c4d0b6a
|
[8.16] Fix sort for rollup data views (#214656) (#215033)
# Backport This will backport the following commits from `main` to `8.16`: - [Fix sort for rollup data views (#214656)](https://github.com/elastic/kibana/pull/214656) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lukas Olson","email":"lukas@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T17:17:53Z","message":"Fix sort for rollup data views (#214656)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/213629.\n\nSince https://github.com/elastic/kibana/pull/163784 we have included a\n`format` parameter in the `sort` that we send to Elasticsearch. This\nworked for everything except rollup data views, which break when the\n`format` parameter is provided.\n\nThis restores the behavior prior to that PR (we still send the `sort`\nbut don't include the `format` parameter). Ideally we would probably not\nsend the timestamp field at all for rollup data views since we treat\nthem as if they are non-time-based, but this would require a bit of a\nrefactor, and rollups are deprecated anyway.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\n### Release notes\n\nFixes opening a rollup data view in Discover.\n\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"2de4b331d334454c4b3bb17b75dcdb83207ee9f9","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Search","release_note:fix","Feature:Data Views","Feature:Rollups","Team:DataDiscovery","backport:all-open","v9.1.0"],"title":"Fix sort for rollup data views","number":214656,"url":"https://github.com/elastic/kibana/pull/214656","mergeCommit":{"message":"Fix sort for rollup data views (#214656)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/213629.\n\nSince https://github.com/elastic/kibana/pull/163784 we have included a\n`format` parameter in the `sort` that we send to Elasticsearch. This\nworked for everything except rollup data views, which break when the\n`format` parameter is provided.\n\nThis restores the behavior prior to that PR (we still send the `sort`\nbut don't include the `format` parameter). Ideally we would probably not\nsend the timestamp field at all for rollup data views since we treat\nthem as if they are non-time-based, but this would require a bit of a\nrefactor, and rollups are deprecated anyway.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\n### Release notes\n\nFixes opening a rollup data view in Discover.\n\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"2de4b331d334454c4b3bb17b75dcdb83207ee9f9"}},"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/214656","number":214656,"mergeCommit":{"message":"Fix sort for rollup data views (#214656)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/213629.\n\nSince https://github.com/elastic/kibana/pull/163784 we have included a\n`format` parameter in the `sort` that we send to Elasticsearch. This\nworked for everything except rollup data views, which break when the\n`format` parameter is provided.\n\nThis restores the behavior prior to that PR (we still send the `sort`\nbut don't include the `format` parameter). Ideally we would probably not\nsend the timestamp field at all for rollup data views since we treat\nthem as if they are non-time-based, but this would require a bit of a\nrefactor, and rollups are deprecated anyway.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\n### Release notes\n\nFixes opening a rollup data view in Discover.\n\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"2de4b331d334454c4b3bb17b75dcdb83207ee9f9"}}]}] BACKPORT--> Co-authored-by: Lukas Olson <lukas@elastic.co> |
||
|
Tiago Costa
|
86b8706a96
|
skip flaky suite (#194701) | ||
|
Jeramy Soucy
|
49466c5e41
|
[8.16] Upgrade xml-crypto 6.0.0 → 6.0.1 (#214792) (#214906)
# Backport This will backport the following commits from `main` to `8.16`: - [Upgrade xml-crypto 6.0.0 → 6.0.1 (#214792)](https://github.com/elastic/kibana/pull/214792) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jeramy Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2025-03-17T17:57:41Z","message":"Upgrade xml-crypto 6.0.0 → 6.0.1 (#214792)\n\n## Summary\n\nUpgrades `xml-crypto` from v6.0.0 to v6.0.1","sha":"da7e44988d160c55147765959dcc19ff59d1cdb6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","backport:all-open","v9.1.0","v9.0.1"],"title":"Upgrade xml-crypto 6.0.0 → 6.0.1","number":214792,"url":"https://github.com/elastic/kibana/pull/214792","mergeCommit":{"message":"Upgrade xml-crypto 6.0.0 → 6.0.1 (#214792)\n\n## Summary\n\nUpgrades `xml-crypto` from v6.0.0 to v6.0.1","sha":"da7e44988d160c55147765959dcc19ff59d1cdb6"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214792","number":214792,"mergeCommit":{"message":"Upgrade xml-crypto 6.0.0 → 6.0.1 (#214792)\n\n## Summary\n\nUpgrades `xml-crypto` from v6.0.0 to v6.0.1","sha":"da7e44988d160c55147765959dcc19ff59d1cdb6"}},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
elastic-vault-github-plugin-prod[bot]
|
a62da54d1e
|
[8.16] Sync bundled packages with Package Storage (#214913)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2460 Co-authored-by: elasticmachine <elasticmachine@elastic.co> |
||
|
Kibana Machine
|
7d2899b52a
|
[8.16] [Automatic Import] Fix chunking of samples in ecs mapping (#214702) (#214734)
# Backport This will backport the following commits from `main` to `8.16`: - [[Automatic Import] Fix chunking of samples in ecs mapping (#214702)](https://github.com/elastic/kibana/pull/214702) <!--- Backport version: 9.6.6 --> ### 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-03-17T12:52:37Z","message":"[Automatic Import] Fix chunking of samples in ecs mapping (#214702)","sha":"059e7e7c52076298537a4faf351ae77eb0563309","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport","v9.1.0"],"title":"[Automatic Import] Fix chunking of samples in ecs mapping","number":214702,"url":"https://github.com/elastic/kibana/pull/214702","mergeCommit":{"message":"[Automatic Import] Fix chunking of samples in ecs mapping (#214702)","sha":"059e7e7c52076298537a4faf351ae77eb0563309"}},"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/214702","number":214702,"mergeCommit":{"message":"[Automatic Import] Fix chunking of samples in ecs mapping (#214702)","sha":"059e7e7c52076298537a4faf351ae77eb0563309"}}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com> |
||
|
elastic-renovate-prod[bot]
|
91869ed65f
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 66d427a (8.16) (#214631)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `3f6bcf4` -> `66d427a` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNiIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Jeramy Soucy
|
4772a30390
|
[8.16] [Automatic Import] Remove pipeline tests from the package (#211223) (#214622)
# Backport This will backport the following commits from `main` to `8.16`: - [[Automatic Import] Remove pipeline tests from the package (#211223)](https://github.com/elastic/kibana/pull/211223) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-17T09:28:57Z","message":"[Automatic Import] Remove pipeline tests from the package (#211223)\n\n## Summary\r\n\r\nThis PR removes unused pipeline tests from the packaging of integration.\r\n\r\nThe pipeline tests are not run today when the integration is built.\r\nHence removing them for now.","sha":"54b6e65a2047cdcc727032e1734170e7c8307aff","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","backport:prev-major","ci:build-cloud-image","ci:cloud-deploy","Team:Security-Scalability","Feature:AutomaticImport","v8.18.0","v9.1.0","v8.19.0","v8.17.3"],"number":211223,"url":"https://github.com/elastic/kibana/pull/211223","mergeCommit":{"message":"[Automatic Import] Remove pipeline tests from the package (#211223)\n\n## Summary\r\n\r\nThis PR removes unused pipeline tests from the packaging of integration.\r\n\r\nThe pipeline tests are not run today when the integration is built.\r\nHence removing them for now.","sha":"54b6e65a2047cdcc727032e1734170e7c8307aff"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211385","number":211385,"state":"MERGED","mergeCommit":{"sha":"d6385326d0eca3c09ae13b73f674f5537d7f9aae","message":"[9.0] [Automatic Import] Remove pipeline tests from the package (#211223) (#211385)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Automatic Import] Remove pipeline tests from the package\n(#211223)](https://github.com/elastic/kibana/pull/211223)\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-17T09:28:57Z\",\"message\":\"[Automatic\nImport] Remove pipeline tests from the package (#211223)\\n\\n##\nSummary\\r\\n\\r\\nThis PR removes unused pipeline tests from the packaging\nof integration.\\r\\n\\r\\nThe pipeline tests are not run today when the\nintegration is built.\\r\\nHence removing them for\nnow.\",\"sha\":\"54b6e65a2047cdcc727032e1734170e7c8307aff\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"backport:prev-minor\",\"backport:prev-major\",\"ci:build-cloud-image\",\"ci:cloud-deploy\",\"Team:Security-Scalability\",\"Feature:AutomaticImport\",\"v9.1.0\"],\"title\":\"[Automatic\nImport] Remove pipeline tests from the\npackage\",\"number\":211223,\"url\":\"https://github.com/elastic/kibana/pull/211223\",\"mergeCommit\":{\"message\":\"[Automatic\nImport] Remove pipeline tests from the package (#211223)\\n\\n##\nSummary\\r\\n\\r\\nThis PR removes unused pipeline tests from the packaging\nof integration.\\r\\n\\r\\nThe pipeline tests are not run today when the\nintegration is built.\\r\\nHence removing them for\nnow.\",\"sha\":\"54b6e65a2047cdcc727032e1734170e7c8307aff\"}},\"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/211223\",\"number\":211223,\"mergeCommit\":{\"message\":\"[Automatic\nImport] Remove pipeline tests from the package (#211223)\\n\\n##\nSummary\\r\\n\\r\\nThis PR removes unused pipeline tests from the packaging\nof integration.\\r\\n\\r\\nThe pipeline tests are not run today when the\nintegration is built.\\r\\nHence removing them for\nnow.\",\"sha\":\"54b6e65a2047cdcc727032e1734170e7c8307aff\"}}]}] BACKPORT-->\n\nCo-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com>"}},{"branch":"8.18","label":"v8.18.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211398","number":211398,"state":"MERGED","mergeCommit":{"sha":"158cfac027e31dd6ca46340a775c019d2228d0ce","message":"[8.18] [Automatic Import] Remove pipeline tests from the package (#211223) (#211398)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[Automatic Import] Remove pipeline tests from the package\n(#211223)](https://github.com/elastic/kibana/pull/211223)\n\n<!--- Backport version: 9.6.4 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Bharat\nPasupula\",\"email\":\"123897612+bhapas@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-17T09:28:57Z\",\"message\":\"[Automatic\nImport] Remove pipeline tests from the package (#211223)\\n\\n##\nSummary\\r\\n\\r\\nThis PR removes unused pipeline tests from the packaging\nof integration.\\r\\n\\r\\nThe pipeline tests are not run today when the\nintegration is built.\\r\\nHence removing them for\nnow.\",\"sha\":\"54b6e65a2047cdcc727032e1734170e7c8307aff\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"backport:prev-minor\",\"backport:prev-major\",\"ci:build-cloud-image\",\"ci:cloud-deploy\",\"Team:Security-Scalability\",\"Feature:AutomaticImport\",\"v9.1.0\"],\"title\":\"[Automatic\nImport] Remove pipeline tests from the\npackage\",\"number\":211223,\"url\":\"https://github.com/elastic/kibana/pull/211223\",\"mergeCommit\":{\"message\":\"[Automatic\nImport] Remove pipeline tests from the package (#211223)\\n\\n##\nSummary\\r\\n\\r\\nThis PR removes unused pipeline tests from the packaging\nof integration.\\r\\n\\r\\nThe pipeline tests are not run today when the\nintegration is built.\\r\\nHence removing them for\nnow.\",\"sha\":\"54b6e65a2047cdcc727032e1734170e7c8307aff\"}},\"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/211223\",\"number\":211223,\"mergeCommit\":{\"message\":\"[Automatic\nImport] Remove pipeline tests from the package (#211223)\\n\\n##\nSummary\\r\\n\\r\\nThis PR removes unused pipeline tests from the packaging\nof integration.\\r\\n\\r\\nThe pipeline tests are not run today when the\nintegration is built.\\r\\nHence removing them for\nnow.\",\"sha\":\"54b6e65a2047cdcc727032e1734170e7c8307aff\"}}]}] BACKPORT-->"}},{"branch":"main","label":"v9.1.0","labelRegex":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211223","number":211223,"mergeCommit":{"message":"[Automatic Import] Remove pipeline tests from the package (#211223)\n\n## Summary\r\n\r\nThis PR removes unused pipeline tests from the packaging of integration.\r\n\r\nThe pipeline tests are not run today when the integration is built.\r\nHence removing them for now.","sha":"54b6e65a2047cdcc727032e1734170e7c8307aff"}},{"branch":"8.x","label":"v8.19.0","labelRegex":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211393","number":211393,"state":"MERGED","mergeCommit":{"sha":"7f23710f4afb022b15aa1e5a1f25fcdeef2f1b9c","message":"[8.x] [Automatic Import] Remove pipeline tests from the package (#211223) (#211393)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Automatic Import] Remove pipeline tests from the package\n(#211223)](https://github.com/elastic/kibana/pull/211223)\n\n<!--- Backport version: 9.6.4 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Bharat\nPasupula\",\"email\":\"123897612+bhapas@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-17T09:28:57Z\",\"message\":\"[Automatic\nImport] Remove pipeline tests from the package (#211223)\\n\\n##\nSummary\\r\\n\\r\\nThis PR removes unused pipeline tests from the packaging\nof integration.\\r\\n\\r\\nThe pipeline tests are not run today when the\nintegration is built.\\r\\nHence removing them for\nnow.\",\"sha\":\"54b6e65a2047cdcc727032e1734170e7c8307aff\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"backport:prev-minor\",\"backport:prev-major\",\"ci:build-cloud-image\",\"ci:cloud-deploy\",\"Team:Security-Scalability\",\"Feature:AutomaticImport\",\"v9.1.0\"],\"title\":\"[Automatic\nImport] Remove pipeline tests from the\npackage\",\"number\":211223,\"url\":\"https://github.com/elastic/kibana/pull/211223\",\"mergeCommit\":{\"message\":\"[Automatic\nImport] Remove pipeline tests from the package (#211223)\\n\\n##\nSummary\\r\\n\\r\\nThis PR removes unused pipeline tests from the packaging\nof integration.\\r\\n\\r\\nThe pipeline tests are not run today when the\nintegration is built.\\r\\nHence removing them for\nnow.\",\"sha\":\"54b6e65a2047cdcc727032e1734170e7c8307aff\"}},\"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/211223\",\"number\":211223,\"mergeCommit\":{\"message\":\"[Automatic\nImport] Remove pipeline tests from the package (#211223)\\n\\n##\nSummary\\r\\n\\r\\nThis PR removes unused pipeline tests from the packaging\nof integration.\\r\\n\\r\\nThe pipeline tests are not run today when the\nintegration is built.\\r\\nHence removing them for\nnow.\",\"sha\":\"54b6e65a2047cdcc727032e1734170e7c8307aff\"}}]}] BACKPORT-->"}},{"branch":"8.17","label":"v8.17.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211405","number":211405,"state":"MERGED","mergeCommit":{"sha":"6b2ed55f13b5e6a4a6feed75906716653d2aa6b2","message":"[8.17] [Automatic Import] Remove pipeline tests from the package (#211223) (#211405)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.17`:\n- [[Automatic Import] Remove pipeline tests from the package\n(#211223)](https://github.com/elastic/kibana/pull/211223)\n\n<!--- Backport version: 9.6.4 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Bharat\nPasupula\",\"email\":\"123897612+bhapas@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-17T09:28:57Z\",\"message\":\"[Automatic\nImport] Remove pipeline tests from the package (#211223)\\n\\n##\nSummary\\r\\n\\r\\nThis PR removes unused pipeline tests from the packaging\nof integration.\\r\\n\\r\\nThe pipeline tests are not run today when the\nintegration is built.\\r\\nHence removing them for\nnow.\",\"sha\":\"54b6e65a2047cdcc727032e1734170e7c8307aff\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"backport:prev-minor\",\"backport:prev-major\",\"ci:build-cloud-image\",\"ci:cloud-deploy\",\"Team:Security-Scalability\",\"Feature:AutomaticImport\",\"v9.1.0\"],\"title\":\"[Automatic\nImport] Remove pipeline tests from the\npackage\",\"number\":211223,\"url\":\"https://github.com/elastic/kibana/pull/211223\",\"mergeCommit\":{\"message\":\"[Automatic\nImport] Remove pipeline tests from the package (#211223)\\n\\n##\nSummary\\r\\n\\r\\nThis PR removes unused pipeline tests from the packaging\nof integration.\\r\\n\\r\\nThe pipeline tests are not run today when the\nintegration is built.\\r\\nHence removing them for\nnow.\",\"sha\":\"54b6e65a2047cdcc727032e1734170e7c8307aff\"}},\"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/211223\",\"number\":211223,\"mergeCommit\":{\"message\":\"[Automatic\nImport] Remove pipeline tests from the package (#211223)\\n\\n##\nSummary\\r\\n\\r\\nThis PR removes unused pipeline tests from the packaging\nof integration.\\r\\n\\r\\nThe pipeline tests are not run today when the\nintegration is built.\\r\\nHence removing them for\nnow.\",\"sha\":\"54b6e65a2047cdcc727032e1734170e7c8307aff\"}}]}] BACKPORT-->"}}]}] BACKPORT--> --------- Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com> Co-authored-by: Kylie Meli <kylie.geller@elastic.co> |
||
|
Jan Monschke
|
f219410251
|
[8.16] [Threat Hunting Investigations] Fix timeline column width bug (#214178) (#214520)
# Backport This will backport the following commits from `main` to `8.16`: - [[Threat Hunting Investigations] Fix timeline column width bug (#214178)](https://github.com/elastic/kibana/pull/214178) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jan Monschke","email":"jan.monschke@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T18:49:16Z","message":"[Threat Hunting Investigations] Fix timeline column width bug (#214178)\n\n## Summary\n\nFixes: https://github.com/elastic/kibana/issues/213754\n\nThe issue above describes a bug in timeline that makes it impossible to\nchange the width of a timeline column. This PR fixes that issue and\nmakes sure that timeline column width settings are saved to\nlocalStorage. This mimics the behaviour of the alerts table elsewhere in\nsecurity solution.\n\n\nhttps://github.com/user-attachments/assets/8b9803a0-406d-4f2d-ada5-4c0b76cd6ab8\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"edbc618321930e358b2e0910f1c5cb5f7606e621","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:Threat Hunting:Investigations","backport:all-open","v8.18.0","v9.1.0","v8.19.0"],"title":"[Threat Hunting Investigations] Fix timeline column width bug","number":214178,"url":"https://github.com/elastic/kibana/pull/214178","mergeCommit":{"message":"[Threat Hunting Investigations] Fix timeline column width bug (#214178)\n\n## Summary\n\nFixes: https://github.com/elastic/kibana/issues/213754\n\nThe issue above describes a bug in timeline that makes it impossible to\nchange the width of a timeline column. This PR fixes that issue and\nmakes sure that timeline column width settings are saved to\nlocalStorage. This mimics the behaviour of the alerts table elsewhere in\nsecurity solution.\n\n\nhttps://github.com/user-attachments/assets/8b9803a0-406d-4f2d-ada5-4c0b76cd6ab8\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"edbc618321930e358b2e0910f1c5cb5f7606e621"}},"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/214473","number":214473,"state":"MERGED","mergeCommit":{"sha":"6c1aa0a4d9f5d605ad037ace4515c848af38f6f4","message":"[9.0] [Threat Hunting Investigations] Fix timeline column width bug (#214178) (#214473)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Threat Hunting Investigations] Fix timeline column width bug\n(#214178)](https://github.com/elastic/kibana/pull/214178)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Jan Monschke <jan.monschke@elastic.co>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214471","number":214471,"state":"MERGED","mergeCommit":{"sha":"f2c8c4c0ce81a88387e0eb400ae6166aceb751f0","message":"[8.18] [Threat Hunting Investigations] Fix timeline column width bug (#214178) (#214471)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[Threat Hunting Investigations] Fix timeline column width bug\n(#214178)](https://github.com/elastic/kibana/pull/214178)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Jan Monschke <jan.monschke@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214178","number":214178,"mergeCommit":{"message":"[Threat Hunting Investigations] Fix timeline column width bug (#214178)\n\n## Summary\n\nFixes: https://github.com/elastic/kibana/issues/213754\n\nThe issue above describes a bug in timeline that makes it impossible to\nchange the width of a timeline column. This PR fixes that issue and\nmakes sure that timeline column width settings are saved to\nlocalStorage. This mimics the behaviour of the alerts table elsewhere in\nsecurity solution.\n\n\nhttps://github.com/user-attachments/assets/8b9803a0-406d-4f2d-ada5-4c0b76cd6ab8\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"edbc618321930e358b2e0910f1c5cb5f7606e621"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214472","number":214472,"state":"MERGED","mergeCommit":{"sha":"b578cc110edf15ae10f5a284a4bc110dbbbd5173","message":"[8.x] [Threat Hunting Investigations] Fix timeline column width bug (#214178) (#214472)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Threat Hunting Investigations] Fix timeline column width bug\n(#214178)](https://github.com/elastic/kibana/pull/214178)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Jan Monschke <jan.monschke@elastic.co>"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
46b9080e7a
|
[8.16] [kbn/server-route-repository] Use appropriate log level based on HTTP status (#214185) (#214580)
# Backport This will backport the following commits from `main` to `8.16`: - [[kbn/server-route-repository] Use appropriate log level based on HTTP status (#214185)](https://github.com/elastic/kibana/pull/214185) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Milton Hultgren","email":"milton.hultgren@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T13:54:08Z","message":"[kbn/server-route-repository] Use appropriate log level based on HTTP status (#214185)","sha":"f2af002a5e51594b0ae2e195bac7f5a7dfe9c383","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.1.0"],"title":"[kbn/server-route-repository] Use appropriate log level based on HTTP status","number":214185,"url":"https://github.com/elastic/kibana/pull/214185","mergeCommit":{"message":"[kbn/server-route-repository] Use appropriate log level based on HTTP status (#214185)","sha":"f2af002a5e51594b0ae2e195bac7f5a7dfe9c383"}},"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/214185","number":214185,"mergeCommit":{"message":"[kbn/server-route-repository] Use appropriate log level based on HTTP status (#214185)","sha":"f2af002a5e51594b0ae2e195bac7f5a7dfe9c383"}}]}] BACKPORT--> Co-authored-by: Milton Hultgren <milton.hultgren@elastic.co> |
||
|
Jan Monschke
|
da72ed698e
|
[8.16] [Threat Hunting Investigations] Improve API docs for notes/timeline (#213584) (#214533)
# Backport This will backport the following commits from `main` to `8.16`: - [[Threat Hunting Investigations] Improve API docs for notes/timeline (#213584)](https://github.com/elastic/kibana/pull/213584) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jan Monschke","email":"jan.monschke@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T17:55:54Z","message":"[Threat Hunting Investigations] Improve API docs for notes/timeline (#213584)\n\n## Summary\n\n[META\nissue](https://github.com/elastic/security-docs-internal/issues/57)\n\nThis PR improves the API documentation for timeline/notes/pinned events\nas per the definition in the meta issue.\n\n### Notes\n#### Timeline API\n- `eventType`:\n\t- is always set to `all`\n\t- looks like it's been superseded by dataView?\n\t- I marked it as `deperecated` \n- `eventIdToNoteIds`:\n- there's a type mismatch between what the frontend expects and what is\nreturned\n\t- also it does not seem to be used anymore?\n\t- it needs to be investigated further\n#### Notes API\n- `GlobalNote`:\n\t- looks like it's not used anymore\n\t- I removed it, nothing broke\n- `eventIngested`, `eventTimestamp`, `eventDataView` and `overrideOwner`\nare all not used on the patch note endpoint, I removed them. The\n`event*` ones I have never seen before to be honest.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e3311c516b45999e875b92ff14140a3197babfc6","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:all-open","v9.1.0"],"title":"[Threat Hunting Investigations] Improve API docs for notes/timeline","number":213584,"url":"https://github.com/elastic/kibana/pull/213584","mergeCommit":{"message":"[Threat Hunting Investigations] Improve API docs for notes/timeline (#213584)\n\n## Summary\n\n[META\nissue](https://github.com/elastic/security-docs-internal/issues/57)\n\nThis PR improves the API documentation for timeline/notes/pinned events\nas per the definition in the meta issue.\n\n### Notes\n#### Timeline API\n- `eventType`:\n\t- is always set to `all`\n\t- looks like it's been superseded by dataView?\n\t- I marked it as `deperecated` \n- `eventIdToNoteIds`:\n- there's a type mismatch between what the frontend expects and what is\nreturned\n\t- also it does not seem to be used anymore?\n\t- it needs to be investigated further\n#### Notes API\n- `GlobalNote`:\n\t- looks like it's not used anymore\n\t- I removed it, nothing broke\n- `eventIngested`, `eventTimestamp`, `eventDataView` and `overrideOwner`\nare all not used on the patch note endpoint, I removed them. The\n`event*` ones I have never seen before to be honest.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e3311c516b45999e875b92ff14140a3197babfc6"}},"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/214261","number":214261,"state":"MERGED","mergeCommit":{"sha":"77caf7c24a7424c52e5b37107768ce3d4ff15bfb","message":"[9.0] [Threat Hunting Investigations] Improve API docs for notes/timeline (#213584) (#214261)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Threat Hunting Investigations] Improve API docs for notes/timeline\n(#213584)](https://github.com/elastic/kibana/pull/213584)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Jan Monschke <jan.monschke@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213584","number":213584,"mergeCommit":{"message":"[Threat Hunting Investigations] Improve API docs for notes/timeline (#213584)\n\n## Summary\n\n[META\nissue](https://github.com/elastic/security-docs-internal/issues/57)\n\nThis PR improves the API documentation for timeline/notes/pinned events\nas per the definition in the meta issue.\n\n### Notes\n#### Timeline API\n- `eventType`:\n\t- is always set to `all`\n\t- looks like it's been superseded by dataView?\n\t- I marked it as `deperecated` \n- `eventIdToNoteIds`:\n- there's a type mismatch between what the frontend expects and what is\nreturned\n\t- also it does not seem to be used anymore?\n\t- it needs to be investigated further\n#### Notes API\n- `GlobalNote`:\n\t- looks like it's not used anymore\n\t- I removed it, nothing broke\n- `eventIngested`, `eventTimestamp`, `eventDataView` and `overrideOwner`\nare all not used on the patch note endpoint, I removed them. The\n`event*` ones I have never seen before to be honest.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e3311c516b45999e875b92ff14140a3197babfc6"}}]}] BACKPORT--> |
||
Antonio
|
6645f27122
|
[8.16] [ResponseOps][MW] Use date format from settings in MW UI (#211576) (#214545)
# Backport This will backport the following commits from `main` to `8.16`: - [[ResponseOps][MW] Use date format from settings in MW UI (#211576)](https://github.com/elastic/kibana/pull/211576) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Antonio","email":"antonio.coelho@elastic.co"},"sourceCommit":{"committedDate":"2025-03-07T12:45:48Z","message":"[ResponseOps][MW] Use date format from settings in MW UI (#211576)\n\nCloses #199315\n\n## Summary\n\nThis PR changes the Maintenance Window UI to respect the date format\nconfigured in Kibana's advanced settings.\n\n3 places needed changing:\n- Maintenance window list.\n- Maintenance window creation page.\n- Event popover in the maintenance window list(for recurring MWs).","sha":"2ead636ebd3d8dc911dd870111c8e016035169c1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","backport:version","v9.1.0","v8.19.0"],"title":"[ResponseOps][MW] Use date format from settings in MW UI","number":211576,"url":"https://github.com/elastic/kibana/pull/211576","mergeCommit":{"message":"[ResponseOps][MW] Use date format from settings in MW UI (#211576)\n\nCloses #199315\n\n## Summary\n\nThis PR changes the Maintenance Window UI to respect the date format\nconfigured in Kibana's advanced settings.\n\n3 places needed changing:\n- Maintenance window list.\n- Maintenance window creation page.\n- Event popover in the maintenance window list(for recurring MWs).","sha":"2ead636ebd3d8dc911dd870111c8e016035169c1"}},"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/211576","number":211576,"mergeCommit":{"message":"[ResponseOps][MW] Use date format from settings in MW UI (#211576)\n\nCloses #199315\n\n## Summary\n\nThis PR changes the Maintenance Window UI to respect the date format\nconfigured in Kibana's advanced settings.\n\n3 places needed changing:\n- Maintenance window list.\n- Maintenance window creation page.\n- Event popover in the maintenance window list(for recurring MWs).","sha":"2ead636ebd3d8dc911dd870111c8e016035169c1"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214438","number":214438,"state":"MERGED","mergeCommit":{"sha":"e74dfe03009087cf65fce16bf43c4053120aff46","message":"[8.x] [ResponseOps][MW] Use date format from settings in MW UI (#211576) (#214438)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[ResponseOps][MW] Use date format from settings in MW UI\n(#211576)](https://github.com/elastic/kibana/pull/211576)\n\n<!--- Backport version: 9.6.6 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n<!--BACKPORT\n[{\"author\":{\"name\":\"Antonio\",\"email\":\"antonio.coelho@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-03-07T12:45:48Z\",\"message\":\"[ResponseOps][MW]\nUse date format from settings in MW UI (#211576)\\n\\nCloses #199315\\n\\n##\nSummary\\n\\nThis PR changes the Maintenance Window UI to respect the date\nformat\\nconfigured in Kibana's advanced settings.\\n\\n3 places needed\nchanging:\\n- Maintenance window list.\\n- Maintenance window creation\npage.\\n- Event popover in the maintenance window list(for recurring\nMWs).\",\"sha\":\"2ead636ebd3d8dc911dd870111c8e016035169c1\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"Team:ResponseOps\",\"backport\nmissing\",\"backport:version\",\"v9.1.0\",\"v8.19.0\"],\"title\":\"[ResponseOps][MW]\nUse date format from settings in MW\nUI\",\"number\":211576,\"url\":\"https://github.com/elastic/kibana/pull/211576\",\"mergeCommit\":{\"message\":\"[ResponseOps][MW]\nUse date format from settings in MW UI (#211576)\\n\\nCloses #199315\\n\\n##\nSummary\\n\\nThis PR changes the Maintenance Window UI to respect the date\nformat\\nconfigured in Kibana's advanced settings.\\n\\n3 places needed\nchanging:\\n- Maintenance window list.\\n- Maintenance window creation\npage.\\n- Event popover in the maintenance window list(for recurring\nMWs).\",\"sha\":\"2ead636ebd3d8dc911dd870111c8e016035169c1\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.x\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/211576\",\"number\":211576,\"mergeCommit\":{\"message\":\"[ResponseOps][MW]\nUse date format from settings in MW UI (#211576)\\n\\nCloses #199315\\n\\n##\nSummary\\n\\nThis PR changes the Maintenance Window UI to respect the date\nformat\\nconfigured in Kibana's advanced settings.\\n\\n3 places needed\nchanging:\\n- Maintenance window list.\\n- Maintenance window creation\npage.\\n- Event popover in the maintenance window list(for recurring\nMWs).\",\"sha\":\"2ead636ebd3d8dc911dd870111c8e016035169c1\"}},{\"branch\":\"8.x\",\"label\":\"v8.19.0\",\"branchLabelMappingKey\":\"^v8.19.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
0230153476
|
[8.16] [EDR Workflows] Rename enforce_registry_filters advanced option (#214106) (#214546)
# Backport This will backport the following commits from `main` to `8.16`: - [[EDR Workflows] Rename `enforce_registry_filters` advanced option (#214106)](https://github.com/elastic/kibana/pull/214106) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T10:55:16Z","message":"[EDR Workflows] Rename `enforce_registry_filters` advanced option (#214106)\n\n## Summary\n\nThis PR renames the path for the following advanced option from\n`windows.advanced.events.registry.enforce_registry_filters` to\n`windows.advanced.events.enforce_registry_filters` in order to harmonize\nwith Endpoint.\n\nmigration is not added, see this comment for rationale:\nhttps://github.com/elastic/kibana/issues/212526#issuecomment-2724023199\n\n### Release note\n\nElastic Defend package policy's ineffective advanced option\n`enforce_registry_filters` is replaced with a new field which now\nprovides the expected effect.\nManual act is needed from users to fill the new field, while the old\nfield is still visible in policy response.\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] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b9a258723d06bcf29392f19e3a80c544e6550fa2","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","v9.1.0"],"title":"[EDR Workflows] Rename `enforce_registry_filters` advanced option","number":214106,"url":"https://github.com/elastic/kibana/pull/214106","mergeCommit":{"message":"[EDR Workflows] Rename `enforce_registry_filters` advanced option (#214106)\n\n## Summary\n\nThis PR renames the path for the following advanced option from\n`windows.advanced.events.registry.enforce_registry_filters` to\n`windows.advanced.events.enforce_registry_filters` in order to harmonize\nwith Endpoint.\n\nmigration is not added, see this comment for rationale:\nhttps://github.com/elastic/kibana/issues/212526#issuecomment-2724023199\n\n### Release note\n\nElastic Defend package policy's ineffective advanced option\n`enforce_registry_filters` is replaced with a new field which now\nprovides the expected effect.\nManual act is needed from users to fill the new field, while the old\nfield is still visible in policy response.\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] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b9a258723d06bcf29392f19e3a80c544e6550fa2"}},"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/214106","number":214106,"mergeCommit":{"message":"[EDR Workflows] Rename `enforce_registry_filters` advanced option (#214106)\n\n## Summary\n\nThis PR renames the path for the following advanced option from\n`windows.advanced.events.registry.enforce_registry_filters` to\n`windows.advanced.events.enforce_registry_filters` in order to harmonize\nwith Endpoint.\n\nmigration is not added, see this comment for rationale:\nhttps://github.com/elastic/kibana/issues/212526#issuecomment-2724023199\n\n### Release note\n\nElastic Defend package policy's ineffective advanced option\n`enforce_registry_filters` is replaced with a new field which now\nprovides the expected effect.\nManual act is needed from users to fill the new field, while the old\nfield is still visible in policy response.\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] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b9a258723d06bcf29392f19e3a80c544e6550fa2"}}]}] BACKPORT--> Co-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co> |
||
|
elastic-renovate-prod[bot]
|
4c654acb46
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 3f6bcf4 (8.16) (#214511)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `69a0542` -> `3f6bcf4` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNiIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
323ec9c7ca
|
[8.16] [Fleet] fix UI bug displaying default agent binary source (#214360) (#214449)
# Backport This will backport the following commits from `main` to `8.16`: - [[Fleet] fix UI bug displaying default agent binary source (#214360)](https://github.com/elastic/kibana/pull/214360) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-13T17:01:08Z","message":"[Fleet] fix UI bug displaying default agent binary source (#214360)\n\n## Summary\n\nFix UI bug when an agent policy uses the default download source\nexplicitly. The Agent binary download UI select was empty.\n\nTo verify:\n- create a new agent binary download source\n- create an agent policy with using the default download source\n- check on Agent policy details UI that the Agent binary download UI\nselect is populated correctly\n\n```\nPOST kbn:/api/fleet/agent_policies\n{\n \"name\": \"demo-policy-5\",\n \"description\": \"\",\n \"namespace\": \"default\",\n \"monitoring_enabled\": [\n \"logs\",\n \"metrics\",\n \"traces\"\n ],\n \"inactivity_timeout\": 1209600,\n \"is_protected\": false,\n \"download_source_id\": \"fleet-default-download-source\"\n}\n```\n\nBefore:\n\n\n\n\nAfter:\n\n<img width=\"1517\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f5d19520-317e-4df8-aaed-0e367a2e6d9b\"\n/>","sha":"eb62a047bd06ebb70c6119bf3c19145df901fdda","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Fleet] fix UI bug displaying default agent binary source","number":214360,"url":"https://github.com/elastic/kibana/pull/214360","mergeCommit":{"message":"[Fleet] fix UI bug displaying default agent binary source (#214360)\n\n## Summary\n\nFix UI bug when an agent policy uses the default download source\nexplicitly. The Agent binary download UI select was empty.\n\nTo verify:\n- create a new agent binary download source\n- create an agent policy with using the default download source\n- check on Agent policy details UI that the Agent binary download UI\nselect is populated correctly\n\n```\nPOST kbn:/api/fleet/agent_policies\n{\n \"name\": \"demo-policy-5\",\n \"description\": \"\",\n \"namespace\": \"default\",\n \"monitoring_enabled\": [\n \"logs\",\n \"metrics\",\n \"traces\"\n ],\n \"inactivity_timeout\": 1209600,\n \"is_protected\": false,\n \"download_source_id\": \"fleet-default-download-source\"\n}\n```\n\nBefore:\n\n\n\n\nAfter:\n\n<img width=\"1517\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f5d19520-317e-4df8-aaed-0e367a2e6d9b\"\n/>","sha":"eb62a047bd06ebb70c6119bf3c19145df901fdda"}},"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/214360","number":214360,"mergeCommit":{"message":"[Fleet] fix UI bug displaying default agent binary source (#214360)\n\n## Summary\n\nFix UI bug when an agent policy uses the default download source\nexplicitly. The Agent binary download UI select was empty.\n\nTo verify:\n- create a new agent binary download source\n- create an agent policy with using the default download source\n- check on Agent policy details UI that the Agent binary download UI\nselect is populated correctly\n\n```\nPOST kbn:/api/fleet/agent_policies\n{\n \"name\": \"demo-policy-5\",\n \"description\": \"\",\n \"namespace\": \"default\",\n \"monitoring_enabled\": [\n \"logs\",\n \"metrics\",\n \"traces\"\n ],\n \"inactivity_timeout\": 1209600,\n \"is_protected\": false,\n \"download_source_id\": \"fleet-default-download-source\"\n}\n```\n\nBefore:\n\n\n\n\nAfter:\n\n<img width=\"1517\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f5d19520-317e-4df8-aaed-0e367a2e6d9b\"\n/>","sha":"eb62a047bd06ebb70c6119bf3c19145df901fdda"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
a92a3848fc
|
[8.16] [APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (#214356) (#214417)
# Backport This will backport the following commits from `main` to `8.16`: - [[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (#214356)](https://github.com/elastic/kibana/pull/214356) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T15:20:17Z","message":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (#214356)\n\nCloses #214328 \n\n## Summary\n\nThis PR fixes the issue with loading an otel native dashboard\n\n## Testing\n- Run ` node scripts/synthtrace otel_edot_simple_trace.ts`\n- ⚠️ As our test data has only a java service there is a small manual\nstep needed (it will be listed below **^**)\n- Open the metrics tab for the service (currently we don't have a\ndashboard):\n\n\n\n\n\n- **^** Go to the `dashboard_catalog.ts` and add mapping for otel native\njava case:\n - first: `'otel_native-edot-java',`\n\n\n\n - second: \n ```js \n case 'otel_native-edot-java': {\n return import(\n /* webpackChunkName: \"lazyJavaOtelNativeDashboard\" */\n './opentelemetry_java.json'\n );\n }\n ``\n\n-\n\n\n- Check the same page after refresh\n\n","sha":"ebe7ef6da0f25b09e1d576e7d8975d7b0b2a95b1","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:obs-ux-infra_services","v9.1.0"],"title":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard","number":214356,"url":"https://github.com/elastic/kibana/pull/214356","mergeCommit":{"message":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (#214356)\n\nCloses #214328 \n\n## Summary\n\nThis PR fixes the issue with loading an otel native dashboard\n\n## Testing\n- Run ` node scripts/synthtrace otel_edot_simple_trace.ts`\n- ⚠️ As our test data has only a java service there is a small manual\nstep needed (it will be listed below **^**)\n- Open the metrics tab for the service (currently we don't have a\ndashboard):\n\n\n\n\n\n- **^** Go to the `dashboard_catalog.ts` and add mapping for otel native\njava case:\n - first: `'otel_native-edot-java',`\n\n\n\n - second: \n ```js \n case 'otel_native-edot-java': {\n return import(\n /* webpackChunkName: \"lazyJavaOtelNativeDashboard\" */\n './opentelemetry_java.json'\n );\n }\n ``\n\n-\n\n\n- Check the same page after refresh\n\n","sha":"ebe7ef6da0f25b09e1d576e7d8975d7b0b2a95b1"}},"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/214356","number":214356,"mergeCommit":{"message":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (#214356)\n\nCloses #214328 \n\n## Summary\n\nThis PR fixes the issue with loading an otel native dashboard\n\n## Testing\n- Run ` node scripts/synthtrace otel_edot_simple_trace.ts`\n- ⚠️ As our test data has only a java service there is a small manual\nstep needed (it will be listed below **^**)\n- Open the metrics tab for the service (currently we don't have a\ndashboard):\n\n\n\n\n\n- **^** Go to the `dashboard_catalog.ts` and add mapping for otel native\njava case:\n - first: `'otel_native-edot-java',`\n\n\n\n - second: \n ```js \n case 'otel_native-edot-java': {\n return import(\n /* webpackChunkName: \"lazyJavaOtelNativeDashboard\" */\n './opentelemetry_java.json'\n );\n }\n ``\n\n-\n\n\n- Check the same page after refresh\n\n","sha":"ebe7ef6da0f25b09e1d576e7d8975d7b0b2a95b1"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co> |
||
Alejandro Fernández Haro
|
8020063671
|
[8.16] [Feature Flags] ECS-compliant logger (#214231) (#214353)
# Backport This will backport the following commits from `main` to `8.16`: - [[Feature Flags] ECS-compliant logger (#214231)](https://github.com/elastic/kibana/pull/214231) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T23:24:40Z","message":"[Feature Flags] ECS-compliant logger (#214231)\n\n## Summary\n\nThe OpenFeature clients receive a logger, but it logs errors like\n`log('something went wrong', error)`. Our core logger then removes the\n`error.message` as it prefers the message provided as the first\nargument.\n\nThis PR wraps the logger to make sure that we handle this type of usage.\n\ncc @pmuellr as he found out about this bug\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98986a86a1086d0047d60a14425920b3c5fbc343","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Feature Flags] ECS-compliant logger","number":214231,"url":"https://github.com/elastic/kibana/pull/214231","mergeCommit":{"message":"[Feature Flags] ECS-compliant logger (#214231)\n\n## Summary\n\nThe OpenFeature clients receive a logger, but it logs errors like\n`log('something went wrong', error)`. Our core logger then removes the\n`error.message` as it prefers the message provided as the first\nargument.\n\nThis PR wraps the logger to make sure that we handle this type of usage.\n\ncc @pmuellr as he found out about this bug\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98986a86a1086d0047d60a14425920b3c5fbc343"}},"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/214304","number":214304,"state":"MERGED","mergeCommit":{"sha":"fa04dc0e0536ced502e3eb8993aa7ba227f7299d","message":"[9.0] [Feature Flags] ECS-compliant logger (#214231) (#214304)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Feature Flags] ECS-compliant logger\n(#214231)](https://github.com/elastic/kibana/pull/214231)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214231","number":214231,"mergeCommit":{"message":"[Feature Flags] ECS-compliant logger (#214231)\n\n## Summary\n\nThe OpenFeature clients receive a logger, but it logs errors like\n`log('something went wrong', error)`. Our core logger then removes the\n`error.message` as it prefers the message provided as the first\nargument.\n\nThis PR wraps the logger to make sure that we handle this type of usage.\n\ncc @pmuellr as he found out about this bug\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98986a86a1086d0047d60a14425920b3c5fbc343"}}]}] BACKPORT--> |
||
|
elastic-vault-github-plugin-prod[bot]
|
21fa4b5b22
|
[8.16] Sync bundled packages with Package Storage (#214242)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2434 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Alejandro Fernández Haro
|
a17cb1c163
|
[8.16] [Feature Flags] Retry provider setup (#214200) (#214300)
# Backport This will backport the following commits from `main` to `8.16`: - [[Feature Flags] Retry provider setup (#214200)](https://github.com/elastic/kibana/pull/214200) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T21:45:38Z","message":"[Feature Flags] Retry provider setup (#214200)\n\n## Summary\n\nWe identified that on some occasions, the Feature Flags provider times\nout when setting up, and, since we don't restart the Kibana server, it\nnever sets it up.\n\nThis PR adds a retry logic to try to set the provider in case there's an\nerror.\n\ncc @pmuellr as he found out about this bug\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1337c11ac3c4c94c828db52a9ab9768ccf9a1c45","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Feature Flags] Retry provider setup","number":214200,"url":"https://github.com/elastic/kibana/pull/214200","mergeCommit":{"message":"[Feature Flags] Retry provider setup (#214200)\n\n## Summary\n\nWe identified that on some occasions, the Feature Flags provider times\nout when setting up, and, since we don't restart the Kibana server, it\nnever sets it up.\n\nThis PR adds a retry logic to try to set the provider in case there's an\nerror.\n\ncc @pmuellr as he found out about this bug\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1337c11ac3c4c94c828db52a9ab9768ccf9a1c45"}},"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/214200","number":214200,"mergeCommit":{"message":"[Feature Flags] Retry provider setup (#214200)\n\n## Summary\n\nWe identified that on some occasions, the Feature Flags provider times\nout when setting up, and, since we don't restart the Kibana server, it\nnever sets it up.\n\nThis PR adds a retry logic to try to set the provider in case there's an\nerror.\n\ncc @pmuellr as he found out about this bug\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1337c11ac3c4c94c828db52a9ab9768ccf9a1c45"}},{"url":"https://github.com/elastic/kibana/pull/214288","number":214288,"branch":"9.0","state":"OPEN"}]}] BACKPORT--> |