chore(root): version packages (canary)

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to canary, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

canary is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on canary.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@react-email/[email protected]

Patch Changes

• d89af46: Broken links to React lines of code in the toolbar

[email protected]

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
react-email	Ready	Preview	Comment	Nov 21, 2025 0:35am
react-email-demo	Ready	Preview	Comment	Nov 21, 2025 0:35am

[cubic-dev-ai]

No issues found across 5 files

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​nodemailer@​6.4.21
	@​plunk/​node@​3.0.3
	postmark@​3.11.0
	mailersend@​2.6.0
	@​sendgrid/​mail@​7.7.0
	next@​16.0.3
	@​react-email/​components@​0.0.36
	typescript@​4.9.5
	nodemailer@​6.10.1
	react-dom@​19.2.0
	@​aws-sdk/​client-ses@​3.936.0
	resend@​4.8.0

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Install-time scripts: npm sharp during install Install script: install Source: node install/check.js || npm run build From: ? → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is an install script? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report