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/preview-server@5.1.0-canary.0

Minor Changes

• 3c2aa37: use turbo for email build

Patch Changes

• ff89ad8: Buffer logs written to console.log,info,warn,error until spinner is done

react-email@5.1.0-canary.0

Minor Changes

• 3c2aa37: use turbo for email build

[vercel]

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

Project	Deployment	Review	Updated (UTC)
react-email	Ready	Preview, Comment	Dec 12, 2025 9:18pm
react-email-demo	Ready	Preview, Comment	Dec 12, 2025 9:18pm

[cubic-dev-ai]

No issues found across 5 files

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm safer-buffer is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: pnpm-lock.yaml → npm/safer-buffer@2.1.2 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. 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

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	normalize-path@​3.0.0
	punycode@​2.3.1
	css-tree@​3.1.0
	tsconfig-paths@​4.2.0
	typescript@​5.8.3

View full report