Skip to content

chore(deps): bump next and react-email in /server #47

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github May 15, 2025

Bumps next to 15.3.2 and updates ancestor dependency react-email. These dependencies need to be updated together.

Updates next from 15.1.2 to 15.3.2

Release notes

Sourced from next's releases.

v15.3.2

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • backport: fix(turbopack): Store persistence of wrapped task on RawVc::LocalOutput (#78488) (#78883)
  • @​next/mdx: Use stable turbopack config options (#78880)
  • Fix react-compiler: Fix detection of interest (#78879)
  • Fix turbopack: Backport sourcemap bugfix (#78881)
  • [next-server] preserve rsc query for rsc redirects (#78876)
  • Update middleware public/static matching (#78875)

Credits

Huge thanks to @​ijjk, @​huozhi, @​kdy1, @​wbinnssmith, and @​bgw for helping!

v15.3.1

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

Credits

Huge thanks to @​kdy1 and @​styfle for helping!

v15.3.1-canary.15

Core Changes

  • [Turbopack] refactor persistent caching from log based to cow approach: #76234

Misc Changes

  • fix(turbo-tasks-fs): Handle filesystem watcher rescan events: #78045

Credits

Huge thanks to @​bgw and @​sokra for helping!

v15.3.1-canary.14

Core Changes

  • Add graceful error boundary for bots requests: #78298
  • make sure eslint-plugin-next is built when running 'pnpm dev': #78305
  • Migrate pages API routes to handler interface: #78166

... (truncated)

Commits

Updates react-email from 3.0.7 to 4.0.13

Release notes

Sourced from react-email's releases.

[email protected]

Patch Changes

  • 8e4afce: fix hot reloading support for users with NodeNext-style imports

Full Changelog: https://github.com/resend/react-email/compare/[email protected]@4.0.13

[email protected]

Patch Changes

  • aa518a3: Add an explicit error when running Node <= 17

Full Changelog: https://github.com/resend/react-email/compare/[email protected]@4.0.12

[email protected]

Patch Changes

  • 1a17219: fix improper require in email export
  • 45ab698: update next to 15.3.1

Full Changelog: https://github.com/resend/react-email/compare/[email protected]@4.0.11

[email protected]

Patch Changes

  • 5ef9fe8: fix support for import ... = require(...) syntax
  • 4c7f597: fix email dev not working with traversal error

Full Changelog: https://github.com/resend/react-email/compare/[email protected]@4.0.10

[email protected]

Patch Changes

  • 643d841: Add .json import support for hot reloading
  • f21a983: fix Node 18 support
  • cd02449: Ensure dependencies outside emails directory are completely resolved
  • 73a31ed: Fix dependent of dependents not causing hot reloads
  • bdffd8c: fix backwards compatibility with render versions
  • e7fa043: Fix access to files outside static directory
  • 9aa033c: Use range of versions for dependencies
  • ab70556: Fix non-email files being rendered during hot reloading
  • 9c9aa5d: Add error message for when an email template does not have a default export

Full Changelog: https://github.com/resend/react-email/compare/[email protected]@4.0.9

[email protected]

[!NOTE] This is a release to backport fixes, it does not contain what was released in the latest canaries.

Patch changes

... (truncated)

Changelog

Sourced from react-email's changelog.

4.0.13

Patch Changes

  • 8e4afce: fix hot reloading support for users with NodeNext-style imports

4.0.12

Patch Changes

  • aa518a3: Add an explicit error when running Node <= 17

4.0.11

Patch Changes

  • 1a17219: fix improper require in email export
  • 45ab698: update next to 15.3.1

4.0.10

Patch Changes

  • 5ef9fe8: fix support for import ... = require(...) syntax
  • 4c7f597: fix email dev not working with traversal error

4.0.9

Patch Changes

  • 643d841: Add .json import support for hot reloading
  • f21a983: fix Node 18 support
  • cd02449: Ensure dependencies outside emails directory are completely resolved
  • 73a31ed: Fix dependent of dependents not causing hot reloads
  • bdffd8c: fix backwards compatibility with render versions
  • e7fa043: Fix access to files outside static directory
  • 9aa033c: Use range of versions for dependencies
  • ab70556: Fix non-email files being rendered during hot reloading
  • 9c9aa5d: Add error message for when an email template does not have a default export

4.0.8

Patch Changes

  • ea579b5: Log out errors that happen when export's esbuild fails

4.0.7

Patch Changes

... (truncated)

Commits
  • 9208f58 chore(root): Version packages (#2228)
  • 8e4afce fix(react-email): Support for users with NodeNext-style imports (#2227)
  • 221ebf7 chore(root): Version packages (#2216)
  • aa518a3 fix(react-email): No explicit error when running with Node <= 17 (#1923)
  • dcb8164 chore(root): Version packages (#2208)
  • e42c267 chore(react-email): Remove debugging log
  • 45ab698 fix(react-email): "createServerParamsForMetadata is not a function" (#2206)
  • 1a17219 fix(react-email): Import compiled templates with createRequire's require (#...
  • 6e33167 chore(root): Version packages (#2203)
  • a41a943 fix(react-email): Tests not importing @​babel/traverse the same as raw ESM (#2...
  • 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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Summary by Sourcery

Bump server dependencies by upgrading Next.js to 15.3.2 and react-email to 4.0.13

Enhancements:

  • Upgrade Next.js from 15.1.2 to 15.3.2 to pull in backported bug fixes and stability improvements
  • Upgrade react-email from 3.x to 4.0.13 to align with updated peer dependency and include hot-reload and import fixes

Bumps [next](https://github.com/vercel/next.js) to 15.3.2 and updates ancestor dependency [react-email](https://github.com/resend/react-email/tree/HEAD/packages/react-email). These dependencies need to be updated together.


Updates `next` from 15.1.2 to 15.3.2
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v15.1.2...v15.3.2)

Updates `react-email` from 3.0.7 to 4.0.13
- [Release notes](https://github.com/resend/react-email/releases)
- [Changelog](https://github.com/resend/react-email/blob/canary/packages/react-email/CHANGELOG.md)
- [Commits](https://github.com/resend/react-email/commits/[email protected]/packages/react-email)

---
updated-dependencies:
- dependency-name: next
  dependency-version: 15.3.2
  dependency-type: indirect
- dependency-name: react-email
  dependency-version: 4.0.13
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels May 15, 2025
Copy link

sourcery-ai bot commented May 15, 2025

Reviewer's Guide

This PR updates the server’s Next.js dependency to v15.3.2 and its react-email dependency to v4.0.13 by modifying package.json entries and regenerating the lockfile to reflect updated transitive dependencies.

File-Level Changes

Change Details Files
Bump Next.js and react-email versions in server dependencies
  • Update next to 15.3.2 in server/package.json
  • Update react-email to 4.0.13 in server/package.json
  • Regenerate server/package-lock.json to capture new versions
server/package.json
server/package-lock.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

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.

0 participants