[dielduarte]

The render Next.js e2e app's package-lock.json has baseline-browser-mapping 2.10.28 (via next > browserslist); the advisory is fixed in 2.11.0.

Changes

• packages/render/e2e/nextjs/package-lock.json: baseline-browser-mapping 2.10.28 → 2.11.34 (version, resolved and integrity only). next asks for ^2.9.19, and this browser-data package publishes every few days, so it's at the latest.

I edited the one entry by hand: npm update also rewrote unrelated bundled-dependency entries for @tailwindcss/oxide-wasm32-wasi, a lockfile-format difference between npm versions.

Test fixture only; no changeset.

Testing

• pnpm test:e2e in packages/render: 6 passed, 2 skipped (already it.skip). It runs npm install against this lockfile, which installs 2.11.34 and leaves the lockfile unchanged, then builds and serves the Next.js app.

---

Summary by cubic

Bumps baseline-browser-mapping in the Next.js e2e app's lockfile from 2.10.28 to 2.11.34 to pick up the advisory fix. next allows ^2.9.19, so this lands at the latest published version.

Notes

• Only version, resolved, and integrity changed; edited by hand because npm update rewrites unrelated bundled-dependency entries.
• Test fixture only; no changelog needed. pnpm test:e2e passes (6 passed, 2 skipped).

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

[vercel]

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

Project	Deployment	Actions	Updated
react-email	Ready	Preview	Oct 29, 2026 1:36pm UTC
react-email-demo	Ready	Preview	Oct 29, 2026 1:36pm UTC

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4bdd4cc

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

[klotty]

No issues found across 1 file

Confidence score: 5/5

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

<sub>Auto-approved: Bumps baseline-browser-mapping to 2.11.34 in the Next.js e2e test lockfile to pick up an advisory fix; only version/resolved/integrity fields change in a test fixture, and the e2e suite passes.

View guided diff | Re-trigger cubic</sub>

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@react-email/render@3837

commit: 4bdd4cc