Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Bump for release (canary) #1592

Merged
merged 1 commit into from
Aug 21, 2024
Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Aug 16, 2024

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to canary, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

canary is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on canary.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

react-email@3.0.0-canary.0

Major Changes

  • f552226: Use a built version of preview app when running email dev

Patch Changes

  • 2799bb4: fix email template preview failing with emails having spaces

  • 3f67038: Deprecated renderAsync and made render itself always async

    Why

    Three reasons:

    1. Better support of NextJS's latest versions
    2. Being ready for future React API deprecations
    3. Support for Suspense which allows for using async inside components

    See deprecation of `renderAsync` and usage of its implementation on `render` #1144 for more info.

    How to upgrade

    If you are using the old render, you will need to now treat the Promise
    that comes out of it, as it is now async. If you are using renderAsync,
    you can replace it with render and things should work the same.

@react-email/render@1.0.0-canary.1

Major Changes

  • 3f67038: Deprecated renderAsync and made render itself always async

    Why

    Three reasons:

    1. Better support of NextJS's latest versions
    2. Being ready for future React API deprecations
    3. Support for Suspense which allows for using async inside components

    See deprecation of `renderAsync` and usage of its implementation on `render` #1144 for more info.

    How to upgrade

    If you are using the old render, you will need to now treat the Promise
    that comes out of it, as it is now async. If you are using renderAsync,
    you can replace it with render and things should work the same.

@react-email/components@0.0.23-canary.3

Patch Changes

  • Updated dependencies [3f67038]
    • @react-email/render@1.0.0-canary.1
    • @react-email/body@0.0.10-canary.0
    • @react-email/button@0.0.17-canary.1
    • @react-email/code-block@0.0.7-canary.0
    • @react-email/code-inline@0.0.4-canary.0
    • @react-email/column@0.0.12-canary.0
    • @react-email/container@0.0.14-canary.0
    • @react-email/font@0.0.8-canary.0
    • @react-email/head@0.0.11-canary.0
    • @react-email/heading@0.0.14-canary.0
    • @react-email/hr@0.0.10-canary.0
    • @react-email/html@0.0.10-canary.0
    • @react-email/img@0.0.10-canary.0
    • @react-email/link@0.0.10-canary.0
    • @react-email/markdown@0.0.12-canary.0
    • @react-email/preview@0.0.11-canary.0
    • @react-email/row@0.0.10-canary.0
    • @react-email/section@0.0.14-canary.0
    • @react-email/text@0.0.10-canary.0

create-email@0.0.31-canary.5

react-email-starter@0.0.31-canary.5

Patch Changes

  • Updated dependencies [f552226]
  • Updated dependencies [2799bb4]
  • Updated dependencies [3f67038]
    • react-email@3.0.0-canary.0
    • @react-email/components@0.0.23-canary.3

Copy link

vercel bot commented Aug 16, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
react-email ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 21, 2024 2:57pm
react-email-demo ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 21, 2024 2:57pm

@gabrielmfern gabrielmfern merged commit a5294f8 into canary Aug 21, 2024
5 checks passed
@gabrielmfern gabrielmfern deleted the changeset-release/canary branch August 21, 2024 14:59
gabrielmfern pushed a commit that referenced this pull request Aug 22, 2024
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant