Update @elastic/ml-ui dependencies (main)

[elastic-renovate-prod]

This PR contains the following updates:

Package	Type	Update	Change
@types/async (source)	devDependencies	patch	^3.2.3 -> ^3.2.24
@types/he (source)	devDependencies	minor	^1.1.1 -> ^1.2.3
async (source)	dependencies	patch	^3.2.3 -> ^3.2.6
react-popper-tooltip	dependencies	major	^3.1.1 -> ^4.4.2

---

Release Notes

mohsinulhaq/react-popper-tooltip (react-popper-tooltip)

v4.4.2: Fix missing hover check in interactive mode

Compare Source

Thanks, @​cgsdev0 https://github.com/mohsinulhaq/react-popper-tooltip/pull/156

v4.4.1: Fix unintentional dependency change

Compare Source

Thanks @​JohnDaly

v4.4.0: Add double click trigger, improve styles declaration, ability to change default tooltip text color

https://github.com/mohsinulhaq/react-popper-tooltip/pull/148
https://github.com/mohsinulhaq/react-popper-tooltip/pull/149
https://github.com/mohsinulhaq/react-popper-tooltip/pull/154

v4.3.0: Add Shadow DOM support

Compare Source

As pointed out by https://github.com/mohsinulhaq/react-popper-tooltip/issues/133 (thanks @​shovalk), interactions with the tooltip when rendered using Shadow DOM wasn't working properly. This release adds support for that by using Event.composedPath to get event target, with event.target as fallback for IE11.

v4.2.0: Revert to mouseenter/mouseleave hover mechanic

Compare Source

v4.1.0 introduced a new way of handling hover trigger, which had a couple of improvements over the old one, but unintentionally led to another set of serious issues.
We have now reverted to the older hover mechanic while also solving the older problems by setting pointer-events: none on the arrow as well as the non-interactive tooltip.

v4.1.2: Hover trigger bug fixes introduced in v4.1.0 🐛

Compare Source

Fixes: https://github.com/mohsinulhaq/react-popper-tooltip/issues/117 & https://github.com/mohsinulhaq/react-popper-tooltip/issues/118

v4.1.1

Compare Source

v4.1.0: An improved and more resilient hover trigger!

Thanks to the contribution by @​czabaj 👑, the hover trigger is now improved quite a bit, accounting for the gap between the trigger and the tooltip and also fixing a glitch in cases where tooltip and trigger overlap.

v4.0.0: usePopperTooltip hook! 🪝

Compare Source

Release notes

With react-popper, used under the hood of react-popper-tooltip, introducing the usePopper hook in the last
major update, we're now releasing the hook version of our own library as well - usePopperTooltip. The hook provides many new features and flexibility
and allows for implementations not possible before.

Breaking changes

This release onwards, the hook is the only way of creating tooltips. This version drops the support of
the TooltipTrigger render prop component. If you want to upgrade and still keep using render prop API,
refer to our example section to implement the legacy API with our new hook.

We wrote this version from scratch. Although thoroughly tested, it can still possibly contain some regressions. Please,
report any problems using the issues link.

• For the sake of consistency, we made some changes to the props names.

  • defaultTooltipShown is renamed to defaultVisible
  • tooltipShown is renamed to visible
  • onVisibilityChange is renamed to onVisibleChange
  • closeOnReferenceHidden is renamed to closeOnTriggerHidden and the default value changed from true to false

• The default placement is now bottom instead of right, in line with react-popper defaults.

• The string value "none" for the prop trigger is replaced with null.

• The default CSS has a few positioning and naming changes.

• Previously, when a user hovered the tooltip, it stayed open to allow the user to interact with the tooltip's content.
  Now the tooltip closes as soon as the cursor leaves the trigger element. The new option interactive has been added to
  configure this behavior.

• getTriggerProps and arrowRef are no longer needed.

---

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[darnautov]

@elasticmachine merge upstream

[Ikuni17]

buildkite test this

[Ikuni17]

@darnautov @peteharverson CI does not automatically run on renovate PRs in the Kibana repo to reduce CI costs. Commenting with /ci or buildkite test this will trigger the CI.

[peteharverson]

Tested changes in f6ce007 inside ML and Dashboard embeddables and LGTM. Didn't see any regressions.

[walterra]

For reference, I used this migration guide to update the tooltips: https://github.com/mohsinulhaq/react-popper-tooltip/blob/HEAD/migrating.md

[walterra]

/ci

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: c6deb67

Failed CI Steps

• Check Types

History

• 💔 Build #265752 failed fcdf1e8

[elastic-renovate-prod]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[walterra]

/ci

[kibanamachine]

Starting backport for target branches: 7.17, 8.16, 8.17, 8.x

https://github.com/elastic/kibana/actions/runs/12907593394

[kibanamachine]

💔 Some backports could not be created

Status	Branch	Result
❌	7.17	Backport failed because of merge conflicts
❌	8.16	Backport failed because of merge conflicts You might need to backport the following PRs to 8.16: - Update platform security modules (main) (#206227)
❌	8.17	Backport failed because of merge conflicts You might need to backport the following PRs to 8.17: - Update platform security modules (main) (#206227)
✅	8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

node scripts/backport --pr 204210

Questions ?

Please refer to the Backport tool documentation

[walterra]

💚 All backports created successfully

Status	Branch	Result
✅	8.17

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

[walterra]

💚 All backports created successfully

Status	Branch	Result
✅	8.16

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

[walterra]

💚 All backports created successfully

Status	Branch	Result
✅	7.17

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.