Repository navigation
fix(react-email): upgrade chokidar to v5 - #3755
Merged
Merged
Conversation
chokidar 4.0.3 was published without npm provenance, so pnpm with trustPolicy set to no-downgrade refuses to install react-email. chokidar 5.0.0 and its only dependency readdirp 5 both carry provenance. The API used by the hot-reload watcher is unchanged. chokidar 5 requires Node 20.19, so the engines field moves from 20.0.0 to 20.19.0. Node 20 reached end of life on 2026-04-30. Closes #3728
🦋 Changeset detectedLatest commit: 88c106b The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
klotty
approved these changes
Sep 23, 2026
klotty
left a comment
klotty
left a comment
There was a problem hiding this comment.
No issues found across 3 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Auto-approved: Upgrades chokidar from v4 to v5 to fix failed installs under pnpm's no-downgrade trust policy; behavior is unchanged and the changeset correctly raises the Node floor to 20.19 per chokidar 5's engine requirement.
Re-trigger cubic
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Installs of
react-emailno longer fail under pnpm'strustPolicy: no-downgrade. chokidar 4.0.3 shipped without npm provenance, so pnpm refused it as a possible package takeover. The hot reload watcher keeps the same behavior on chokidar 5.Decision. The Node floor moves to 20.19, which chokidar 5 needs. Node 20 reached end of life on 2026-04-30, so the changeset is minor rather than major.
Closes #3728. Supersedes #3730.
Summary by cubic
Fixes
react-emailinstalls failing under pnpm'strustPolicy: no-downgradeby upgradingchokidarto v5, which ships with npm provenance. Hot reload behavior is unchanged.Migration
Written for commit 88c106b. Summary will update on new commits.