chore: use ^18.2.0 instead of 18.2.0 for all react dependency entries #1434
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
bukinoshita
approved these changes
Apr 26, 2024
gabrielmfern
added a commit
that referenced
this pull request
Apr 26, 2024
gabrielmfern
added a commit
that referenced
this pull request
Apr 26, 2024
gabrielmfern
added a commit
that referenced
this pull request
Apr 26, 2024
gabrielmfern
added a commit
that referenced
this pull request
Apr 29, 2024
gabrielmfern
added a commit
that referenced
this pull request
Apr 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR just changes all of our uses of React from exact
18.2.0to
^18.2.0so that they all can use the new18.3.0. We already hadthis for the
react-emailpackage (our CLI), but after the new versionreleased it was causing errors due to
@react-email/componentsrequiringreactexactly at18.2.0instead of^18.2.0, so this PR changesthose versions into using
^18.2.0.This is meant for #1432.