Skip to content

fix(tooltip): allow explicit boundary element (#1049) [25.0.x]#1056

Merged
nickofthyme merged 1 commit intoelastic:25.0.xfrom
nickofthyme:backport/25.0.x/pr-1049
Mar 4, 2021
Merged

fix(tooltip): allow explicit boundary element (#1049) [25.0.x]#1056
nickofthyme merged 1 commit intoelastic:25.0.xfrom
nickofthyme:backport/25.0.x/pr-1049

Conversation

@nickofthyme
Copy link
Copy Markdown
Collaborator

@nickofthyme nickofthyme commented Mar 4, 2021

Backports the following commits to 25.0.x:

@nickofthyme nickofthyme changed the title fix(tooltip): allow explicit boundary element (#1049) [{baseBranch}] fix(tooltip): allow explicit boundary element (#1049) [25.0.x] Mar 4, 2021
@nickofthyme nickofthyme merged commit 05d6885 into elastic:25.0.x Mar 4, 2021
@nickofthyme nickofthyme deleted the backport/25.0.x/pr-1049 branch March 4, 2021 20:40
github-actions bot pushed a commit that referenced this pull request Mar 4, 2021
@semantic-release-bot
chore(release): 25.0.2 [skip ci]
f6074c2 
## [25.0.2](v25.0.1...v25.0.2) (2021-03-04)

### Bug Fixes

* **tooltip:** allow explicit boundary element ([#1049](#1049)) ([#1056](#1056)) ([05d6885](05d6885))
@nickofthyme
Copy link
Copy Markdown
Collaborator Author

nickofthyme commented Mar 4, 2021

🎉 This PR is included in version 25.0.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

backport released on @25.0.x

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@nickofthyme