Skip to content
This repository has been archived by the owner on Jun 9, 2023. It is now read-only.

Using reach/tooltip@0.13.0 #433

Merged
merged 1 commit into from
Mar 1, 2023
Merged

Using reach/tooltip@0.13.0 #433

merged 1 commit into from
Mar 1, 2023

Conversation

philippemiguet
Copy link
Contributor

Description

Finally, using reach/tooltip@0.13.0 because of an error in their tagging, and 0.12.1 was still required react < 17.

Related to: #432

Motivation and Context

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style and guidelines of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have updated the CHANGELOG document.
  • I have added tests to cover my changes.
  • I have performed a self-review of my own code
  • I have tested my changes/additions in the latest Chrome, Firefox, and Safari.
  • I have commented my code, particularly in hard-to-understand areas
  • All new and existing tests passed.
  • I have performed the accessibility audit of my UI changes according to the accessibility doc.
  • [Buffer Engineers] Someone from the Design team reviewed and approved my changes
  • [Buffer Engineers] I have notified the BDS team of my changes in the #proj-design-system Slack channel

@philippemiguet philippemiguet merged commit 20dbb4a into main Mar 1, 2023
@philippemiguet philippemiguet deleted the task/peer-dep branch March 1, 2023 05:42
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant