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(deps): bump @react-email/render from 0.0.12 to 1.0.2 #2630

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 31, 2024

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

Release notes

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

@​react-email/render 1.0.2

What's Changed

Patch Changes

  • 4627675: Fix null characters in between chunks when using high-density characters

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

@​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

... (truncated)

Changelog

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

1.0.2

Patch Changes

  • 4627675: Fix null characters in between chunks when using high-density characters

1.0.2-canary.0

Patch Changes

  • 0fab161: Fix null characters in between chunks when using high-density characters

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

... (truncated)

Commits
  • 17eb85c chore: Bump for release (#1751)
  • cf1f2e1 chore: Bump for release (canary) (#1710)
  • 4627675 fix(render): Null characters in between chunks (#1709)
  • 598fe95 Fix(docs): add await to the integration examples in the documentation (#1672)
  • 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)
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Oct 31, 2024
@dependabot dependabot bot requested a review from mcstepp as a code owner October 31, 2024 18:03
@dependabot dependabot bot added the javascript Pull requests that update Javascript code label Oct 31, 2024
@dependabot dependabot bot requested a review from MichaelUnkey as a code owner October 31, 2024 18:03
Copy link

vercel bot commented Oct 31, 2024

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

Name Status Preview Comments Updated (UTC)
dashboard ❌ Failed (Inspect) Nov 3, 2024 9:33am
engineering ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 3, 2024 9:33am
play ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 3, 2024 9:33am
www ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 3, 2024 9:33am
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
workflows ⬜️ Ignored (Inspect) Visit Preview Nov 3, 2024 9:33am

Copy link

changeset-bot bot commented Oct 31, 2024

⚠️ No Changeset found

Latest commit: a546649

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

Copy link
Contributor

coderabbitai bot commented Oct 31, 2024

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.

Copy link
Contributor

github-actions bot commented Oct 31, 2024

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

Bumps [@react-email/render](https://github.com/resend/react-email/tree/HEAD/packages/render) from 0.0.12 to 1.0.2.
- [Release notes](https://github.com/resend/react-email/releases)
- [Changelog](https://github.com/resend/react-email/blob/canary/packages/render/CHANGELOG.md)
- [Commits](https://github.com/resend/react-email/commits/@react-email/[email protected]/packages/render)

---
updated-dependencies:
- dependency-name: "@react-email/render"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 4, 2024

A newer version of @​react-email/render exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant