chore(components, create-email, head, react-email, render, tailwind): Bump for canary release #1459
Conversation
This file contains hidden or 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 ↗︎
|
gabrielmfern
force-pushed
the
chore/bump-for-canary-release
branch
from
e871aa4 to
945e930
Compare
…nents and react-email to 0.0.18-canary.0 2.1.3-canary.0 respectively
…nents` 2.1.3-canary.0 -> react-email 0.0.18-canary.0 -> @react-email/components
gabrielmfern
force-pushed
the
chore/bump-for-canary-release
branch
from
4933680 to
c62d6df
Compare
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.
When React launched
18.3.xwe had issues due to our being dependenciesbeing setup in a bad way which forced me into publishing a new release for
all packages while not merging in the canary changes because of me being
unsure of their stability, so there was this weird mismatch
between versions where we had a previous canary release that was
meant to be for a later release, this PR fixes that.
This PR also bumps
renderto a canary that it wasn't on beforebecause of #1443.
Here are the bumps that I did on this PR by each commit bump that
this PR does: