fix(ci): npm token not working in release workflows

[gabrielmfern]

Summary by cubic

Fixes npm auth in canary and stable release workflows by writing the NPM token to ~/.npmrc, ensuring publishes can run successfully.

• Bug Fixes
  • Add step to create ~/.npmrc with //registry.npmjs.org/:_authToken from secrets.NPM_TOKEN in both workflows.
  • Remove NPM_TOKEN env from the canary publish step in favor of .npmrc auth.

^{Written for commit f4f1761. Summary will update on new commits.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: f4f1761

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

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

Project	Deployment	Review	Updated (UTC)
react-email	Ready	Preview, Comment	Jan 19, 2026 7:34pm
react-email-demo	Ready	Preview, Comment	Jan 19, 2026 7:34pm

[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
	@​sendgrid/​mail@​7.7.0
	postmark@​3.11.0
	next@​16.1.3
	@​react-email/​components@​0.0.36
	mailersend@​2.6.0
	nodemailer@​7.0.12
	react-dom@​19.2.3
	@​aws-sdk/​client-ses@​3.971.0
	resend@​4.8.0

View full report

[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		Install-time scripts: npm sharp during install Install script: install Source: node install/check.js || npm run build From: ? → npm/next@16.1.3 → npm/sharp@0.34.5 ℹ 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 support@socket.dev. 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/sharp@0.34.5. 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

[cubic-dev-ai]

No issues found across 2 files