chore: fix @react-email/body version (RESOLVED)

[wthrajat]

PS: see #3039 (comment)

---

The latest version is v0.2.1 (see: https://www.npmjs.com/package/@react-email/body)

This is causing an error while installing the lib:

rajat@mac ~> pnpm i @react-email/components


ERR_PNPM_NO_MATCHING_VERSION  No matching version found for @react-email/body@0.3.0 while fetching it from https://registry.npmjs.org/

This error happened while installing the dependencies of @react-email/components@1.0.9

The latest release of @react-email/body is "0.2.1".

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3bf7358

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]

@wthrajat is attempting to deploy a commit to the resend Team on Vercel.

A member of the Team first needs to authorize it.

[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
	stacktrace-parser@​0.1.11
	mdast-util-to-string@​4.0.0
	punycode@​2.3.1
	postcss@​8.5.6
	remark@​15.0.1
	tsconfig-paths@​4.2.0
	sharp@​0.34.5
	typescript@​5.9.3
	three@​0.170.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: packages/preview-server/package.json → 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 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Auto-approved: Fixes invalid package version in package.json to match the latest published version on npm, resolving installation errors.}

---

Since this is your first cubic review, here's how it works:

• cubic automatically reviews your code and comments on bugs and improvements
• Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
• Add one-off context when rerunning by tagging @cubic-dev-ai with guidance or docs links (including llms.txt)
• Ask questions if you need clarification on any suggestion

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@react-email/body@3039

commit: fe3b296

[wthrajat]

@gabrielmfern ah I see #3035 now, looks like the manual versioning might have caused a registry mismatch.

It seems @react-email/components@1.0.9 was published, but it requires @react-email/body@0.3.0, which isn't available on NPM yet (latest is still 0.2.1). This is causing an ERR_PNPM_NO_MATCHING_VERSION for anyone trying to install the latest components:

Was the publish for body@0.3.0 successful on your end, or did the changeset bug block that specific package?

For now in our source code, we've managed to do a workaround using pnpm override. Still flagging this up. Also now I realise this should have been an issue, not a PR ;)

[gabrielmfern]

Was the publish for body@0.3.0 successful on your end, or did the changeset bug block that specific package?

Was successful, I did it manually out of CI

[wthrajat]

Awesome, thanks!