chore(render): bump baseline-browser-mapping in the Next.js e2e app

Merged
DI
2d ago
+3-3

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).