Skip to content

chore(deps): update react-email monorepo#7546

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/react-email-monorepo
Open

chore(deps): update react-email monorepo#7546
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/react-email-monorepo

Conversation

@renovate

@renovate renovate Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@react-email/render (source) 2.0.82.0.9 age confidence
@react-email/ui (source) 6.6.16.6.3 age confidence
react-email (source) 6.1.06.6.3 age confidence

Release Notes

resend/react-email (@​react-email/render)

v2.0.9

Compare Source

Patch Changes
  • 60a5b09: Add npm support metadata for the package homepage and issue tracker.
resend/react-email (@​react-email/ui)

v6.6.3

Compare Source

Patch Changes
  • 5ad1d79: Update the existing Resend template on upload instead of always creating a new one. The "Upload to Resend" and "Bulk Upload" actions now look the template up by name and update it in place when exactly one matches, so re-uploading no longer produces duplicates (welcome, welcome (1), ...).

v6.6.2

Compare Source

v6.6.1

Compare Source

Patch Changes
  • 1dd2bff: Fix line and column calculation for CRLF line endings in the email validation diagnostics. A \r\n was being counted as two line breaks, so line and column numbers reported for templates authored with Windows line endings were off.

v6.6.0

Compare Source

v6.5.0

Compare Source

Minor Changes
  • 3875d2a: add a --clients option to email dev and a COMPATIBILITY_EMAIL_CLIENTS environment variable to narrow which email clients trigger compatibility warnings. By default the preview still warns for gmail, apple-mail, outlook, and yahoo. Teams that only target one or two clients can now skip the noise: email dev --clients outlook,apple-mail. The CLI flag wins over the env var; an empty or fully-invalid list falls back to the defaults so warnings can't be silently switched off. Builds on #​2797 by @​ReemX.

v6.4.0

Compare Source

v6.3.3

Compare Source

Patch Changes
  • 86745ec: reject paths that resolve outside the configured emails directory in renderEmailByPath and getEmailPathFromSlug to close a path-traversal vector in the preview server

v6.3.2

Compare Source

v6.3.1

Compare Source

Patch Changes
  • 27587f1: stop accepting the emails directory path as a server-action argument

    The getEmailsDirectoryMetadataAction server action used to take an
    absolute filesystem path from the client and walk that directory on the
    server, which allowed any caller of the endpoint to enumerate arbitrary
    directories on the host. The action now reads the path from the server-only
    REACT_EMAIL_INTERNAL_EMAILS_DIR_ABSOLUTE_PATH env variable and ignores
    client input.

v6.3.0

Compare Source

Minor Changes
  • 99cadf3: support previewing HTML email templates
Patch Changes
  • fd140fc: quality of life improvements to the send email flow:
    • infer a proper title based on the file name
    • store preferred subject per email when modified
    • store recipient for testing in local storage as well

v6.2.0

Compare Source

v6.1.5

Compare Source

v6.1.4

Compare Source

v6.1.3

Compare Source

Patch Changes

v6.1.1

Compare Source

resend/react-email (react-email)

v6.6.3

Compare Source

v6.6.2

Compare Source

Patch Changes
  • 437c414: Fix Tailwind opacity modifiers (e.g. bg-blue-600/50) rendering an invalid percentage alpha that breaks in some email clients.

v6.6.1

Compare Source

Patch Changes
  • 21bac49: Fix Markdown corrupting double quotes in markdownCustomStyles. Inline style values containing a " (e.g. fontFamily: '"Times New Roman", serif') were escaped to the apostrophe entity ' instead of ", silently rewriting the quoted value. Double quotes are now escaped as ".
  • Updated dependencies [60a5b09]

v6.6.0

Compare Source

Minor Changes
  • 16ff94c: add a useTitleTag in Preview component so users can disable it if they want to

v6.5.0

Compare Source

Minor Changes
  • 3875d2a: add a --clients option to email dev and a COMPATIBILITY_EMAIL_CLIENTS environment variable to narrow which email clients trigger compatibility warnings. By default the preview still warns for gmail, apple-mail, outlook, and yahoo. Teams that only target one or two clients can now skip the noise: email dev --clients outlook,apple-mail. The CLI flag wins over the env var; an empty or fully-invalid list falls back to the defaults so warnings can't be silently switched off. Builds on #​2797 by @​ReemX.
Patch Changes
  • d47825a: Add accessibility defaults to components: dir/lang on Body, an empty alt fallback on Img, role="presentation" on the Markdown table, and a <title> from Preview.

v6.4.0

Compare Source

Minor Changes
  • ba99365: resolve and strip unresolved --tw-* CSS variables in non-inlinable rules so Tailwind media query utilities no longer break Gmail

v6.3.3

Compare Source

v6.3.2

Compare Source

Patch Changes
  • fbda5c8: increase whitespace padding to 200 characters for better Gmail preview text rendering

v6.3.1

Compare Source

Patch Changes
  • c610dc0: fix: padding in Container/Section failing on Klaviyo and Outlook desktop

v6.3.0

Compare Source

v6.2.0

Compare Source

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.

v6.1.5

Compare Source

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.

v6.1.4

Compare Source

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

v6.1.3

Compare Source

v6.1.1

Compare Source

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

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@sonarqubecloud

Copy link
Copy Markdown

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.

0 participants