chore(deps): bump @react-email/render from 0.0.12 to 1.0.1

[dependabot]

Bumps @react-email/render from 0.0.12 to 1.0.1.

Release notes

Sourced from @​react-email/render's releases.

@​react-email/render 1.0.1

What's Changed

• 7481b12: Add a wrapping Suspense to all email templates before rendering

Full Changelog: https://github.com/resend/react-email/compare/@​react-email/render@​1.0.0...@​react-email/render@​1.0.1

@​react-email/render 1.0.0

What's Changed

Major Changes

• f9483ec: 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` resend/react-email#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.

Patch Changes

• 3caaf53: Updated peer dependencies to allow for React 19 release candidate and React 19 itself

Full Changelog: https://github.com/resend/react-email/compare/@​react-email/render@​0.0.17...@​react-email/render@​1.0.0

@​react-email/render 0.0.16

What's Changed

• Fixes an issue with ESM on #1491 by @​gabrielmfern

Full Changelog: https://github.com/resend/react-email/compare/@​react-email/render@​0.0.15...@​react-email/render@​0.0.16

@​react-email/render 0.0.16-canary.0

What's Changed

• Fixes an issue with ESM on #1491 by @​gabrielmfern

Full Changelog: https://github.com/resend/react-email/compare/@​react-email/render@​0.0.15...@​react-email/render@​0.0.16-canary.0

... (truncated)

Changelog

Sourced from @​react-email/render's changelog.

1.0.1

Patch Changes

• 7481b12: Add a wrapping Suspense to all email templates before rendering

1.0.0

Major Changes

• f9483ec: 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` resend/react-email#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.

Patch Changes

• 3caaf53: Updated peer dependencies to allow for React 19 release candidated and React 19 itself

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` resend/react-email#1144 for more info.

  How to upgrade

... (truncated)

Commits

• f48c7f5 chore: Bump for release (#1642)
• 7481b12 feat(render): Suspense wrapping all elements passed to render (#1637)
• 07e931b chore: Version packages
• 7ce855f chore: Bump for release (canary) (#1592)
• f9483ec feat(render): Substitute implementation of render with the one from `render...
• 1a47335 feat(react-email): Build preview app and run it built instead of as dev (#1537)
• 6b8ad7d refactor: Simplify types and remove unused babel config files (#1583)
• fa3918b chore: Bump for release (canary) (#1554)
• 3caaf53 chore: Add direct support for React 19 (#1474)
• e97b08c chore: Bump for release (#1552)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
dashboard	❌ Failed (Inspect)			Oct 28, 2024 10:39am
engineering	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 28, 2024 10:39am
play	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 28, 2024 10:39am
workflows	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 28, 2024 10:39am
www	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 28, 2024 10:39am

[changeset-bot]

⚠️ No Changeset found

Latest commit: e6e02b0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Thank you for following the naming conventions for pull request titles! 🙏

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[dependabot]

Superseded by #2630.