Repository navigation
chore(deps): upgrade chokidar to v5 - #3730
Closed
Larslllllll wants to merge 2 commits into
Closed
Larslllllll wants to merge 2 commits into
Larslllllll wants to merge 2 commits into
Conversation
added 2 commits
September 6, 2026 01:07
…e override Before this fix, the Section component split padding styles to <td> while keeping className on <table>. This caused Tailwind responsive variants (e.g. max-sm:px-5) to be applied to <table> while base padding sat on <td>, making responsive overrides impossible. After: all styles (including padding) are passed through to <table>, matching where className is applied. This allows responsive variants to properly override base padding via CSS cascade. Fixes #3693.
Fixes #3728. chokidar v4.0.3 lacks npm provenance causing pnpm trustPolicy no-downgrade to reject the package. v5 requires Node.js >=20.19, satisfied by the existing >=20.0.0 engine constraint.
Contributor
|
Someone is attempting to deploy a commit to the resend Team on Vercel. A member of the Team first needs to authorize it. |
🦋 Changeset detectedLatest commit: 483dcbb The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
Member
|
can you point this at canary instead? closing the duplicate #3731 |
Member
|
Hey, this one was targeting |
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
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.
Summary
Fixes #3728. chokidar v4.0.3 was released without npm provenance, causing pnpm with trustPolicy: no-downgrade to reject the package:
chokidar v5.0.0 includes provenance and requires Node.js >=20.19, which is satisfied by the existing >=20.0.0 engine constraint.
Changes
Fixes #3728.
Summary by cubic
Upgrades
chokidarto v5 so pnpm withtrustPolicy: no-downgradeaccepts it, and bundles a Next.js security bump, markdown endpoints for LLM agents, a Section padding fix, an editor alignment fix, and a new ZeptoMail example. Section now keeps padding on the same element as className so Tailwind responsive variants can override it; the editor's Left alignment button resolves inherited alignment instead of reporting a falseleft, and explicit left alignment now persists to HTML.Dependencies
chokidarv4.0.3 was released without npm provenance, so pnpm rejected it undertrustPolicy: no-downgrade; v5.0.0 includes provenance and requires Node >=20.19, which the existing engine constraint already satisfies.New Features
/api/markdownroutes, withAcceptnegotiation and.mdURL rewrites handled by proxy middleware.robots.txtnow emits aContent-Signalheader for AI agents.Written for commit 483dcbb. Summary will update on new commits.