Skip to content

Conversation

kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 9.2:

Questions ?

Please refer to the Backport tool documentation

## Summary

(Showing both nav versions at the same time just for comparison and
saving one image upload)
<img width="1862" height="1342" alt="image"
src="https://github.com/user-attachments/assets/bd9b9114-2176-41a0-9048-ea8625ea25b6"
/>

- v1 shows badge at all times
- v2 shows badge on hover after a short delay
- Show badge on landing page

<img width="1862" height="1342" alt="image"
src="https://github.com/user-attachments/assets/01f148c7-cfe2-42fe-bf78-583ee080f870"
/>
<img width="1862" height="1342" alt="image"
src="https://github.com/user-attachments/assets/31731db0-0085-466d-a532-7f2179787e55"
/>

- Agents / tools list pages shows tech preview badge next to the page
title

### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [ ] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

(cherry picked from commit fc3b98e)
@kibanamachine kibanamachine requested review from a team as code owners October 3, 2025 14:55
@kibanamachine kibanamachine added the backport This PR is a backport of another PR label Oct 3, 2025
@kibanamachine kibanamachine enabled auto-merge (squash) October 3, 2025 14:55
@elasticmachine
Copy link
Contributor

💔 Build Failed

Failed CI Steps

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
onechat 610 612 +2

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
enterpriseSearch 951.1KB 951.1KB +39.0B
onechat 320.4KB 320.5KB +128.0B
total +167.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
onechat 16.0KB 16.0KB -2.0B
serverlessSearch 29.8KB 29.9KB +39.0B
total +37.0B

cc @zacharyparikh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport This PR is a backport of another PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants