Skip to content

chore(deps): bump next and react-email#28

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/multi-f927101c4f
Open

chore(deps): bump next and react-email#28
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/multi-f927101c4f

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 21, 2026

Copy link
Copy Markdown
Contributor

Removes next. It's no longer used after updating ancestor dependency react-email. These dependencies need to be updated together.

Removes next

Updates react-email from 3.0.1 to 6.3.0

Release notes

Sourced from react-email's releases.

react-email@6.3.0

No release notes provided.

react-email@6.2.0

Minor Changes

  • 192d82a: Add theme and utility props to <Tailwind> for Tailwind v4 CSS-first configuration. Both accept a CSS string and can be combined with the existing config prop.

    import themeCss from "./theme.css?inline";
<Tailwind theme={themeCss}>
<div className="bg-brand font-display">Custom themed content</div>
</Tailwind>;

    Empty strings are no-ops. The base Tailwind theme and utilities are still loaded — theme and utility layer on top.

    The preview server, email export, and the caniemail compatibility check all understand the Vite-style ?inline and ?raw suffixes on CSS imports, so the pattern above works the same in your project and inside the preview UI. The compatibility check also extracts the theme and utility props (in addition to config) when analyzing your template, so any caniemail incompatibilities in CSS produced by those props will surface as warnings.

    Internal note: the exported setupTailwind helper now takes { config, cssConfigs } instead of a positional TailwindConfig. Calling it with the old shape throws with a migration hint.

Patch Changes

  • 06f1d05: Watch directories targeted by dynamic import() template literals so changes to runtime-resolved files trigger preview reloads.

react-email@6.1.5

Patch Changes

  • 1a61cb0: Avoid OOM when running email export on projects with many templates. esbuild builds now run in batches of 10 entry points, and the render phase runs each batch of 25 templates inside a worker_threads worker so V8 isolate memory is reclaimed between batches.

react-email@6.1.4

Patch Changes

  • 1c386ce: Avoid spamming each spinner frame as a new line on non-TTY streams (CI logs, pipes, dumb terminals). The spinner now logs each status text once instead of redrawing animated frames when the output is not a TTY.
  • ad6a9de: - deprecate packageManager CLI option for email build, only supporting npm
    • ensure email build dependency installation includes dev dependencies

react-email@6.1.3

No release notes provided.

react-email@6.1.1

Patch Changes

  • 3c62bd0: fix divider with extra borders around other corners

react-email@6.1.0

Patch Changes

  • 47eeece: Tailwind: clearer error when <Head> is outside <Tailwind>

... (truncated)

Changelog

Sourced from react-email's changelog.

6.3.0

6.2.0

Minor Changes

  • 192d82a: Add theme and utility props to <Tailwind> for Tailwind v4 CSS-first configuration. Both accept a CSS string and can be combined with the existing config prop.

    import themeCss from "./theme.css?inline";
<Tailwind theme={themeCss}>
<div className="bg-brand font-display">Custom themed content</div>
</Tailwind>;

    Empty strings are no-ops. The base Tailwind theme and utilities are still loaded — theme and utility layer on top.

    The preview server, email export, and the caniemail compatibility check all understand the Vite-style ?inline and ?raw suffixes on CSS imports, so the pattern above works the same in your project and inside the preview UI. The compatibility check also extracts the theme and utility props (in addition to config) when analyzing your template, so any caniemail incompatibilities in CSS produced by those props will surface as warnings.

    Internal note: the exported setupTailwind helper now takes { config, cssConfigs } instead of a positional TailwindConfig. Calling it with the old shape throws with a migration hint.

Patch Changes

  • 06f1d05: Watch directories targeted by dynamic import() template literals so changes to runtime-resolved files trigger preview reloads.

6.1.5

Patch Changes

  • 1a61cb0: Avoid OOM when running email export on projects with many templates. esbuild builds now run in batches of 10 entry points, and the render phase runs each batch of 25 templates inside a worker_threads worker so V8 isolate memory is reclaimed between batches.

6.1.4

Patch Changes

  • 1c386ce: Avoid spamming each spinner frame as a new line on non-TTY streams (CI logs, pipes, dumb terminals). The spinner now logs each status text once instead of redrawing animated frames when the output is not a TTY.
  • ad6a9de: - deprecate packageManager CLI option for email build, only supporting npm
    • ensure email build dependency installation includes dev dependencies

6.1.3

6.1.2

6.1.1

Patch Changes

  • 3c62bd0: fix divider with extra borders around other corners

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for react-email since your current version.


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 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.

@dependabot
chore(deps): bump next and react-email
2f3b7ee 
Removes [next](https://github.com/vercel/next.js). It's no longer used after updating ancestor dependency [react-email](https://github.com/resend/react-email/tree/HEAD/packages/react-email). These dependencies need to be updated together.


Removes `next`

Updates `react-email` from 3.0.1 to 6.3.0
- [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/react-email@6.3.0/packages/react-email)

---
updated-dependencies:
- dependency-name: next
  dependency-version:
  dependency-type: indirect
- dependency-name: react-email
  dependency-version: 6.3.0
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels May 21, 2026
@dependabot dependabot Bot mentioned this pull request May 21, 2026
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants