next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 14.2.1 to 14.2.2
1 release in betweenevery note read
Security
37 advisories still affect 14.2.2
- Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are usedcritical · GHSA-2464-fhr4-w9xw
- Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are usedcritical · GHSA-2xp9-vwfh-vxw4
- Next.js has a Middleware / Proxy bypass in Pages Router applications using i18nhigh · GHSA-36qx-fr4f-26g5
Upgrading to 15.5.29 clears them.
Release by release
- New
Strip traceparent header from cachekey
- New
Turbopack: Allow client components to be imported in app routes
- New
Add pathname normalizer for actions
- Fixed
Fix Server Action error logs for unhandled POST requests
- New
7 other lines we could not sort, mostly version bumps
- 14.2.2
Improve rendering performance
- 14.2.2
Tweak test for Azure
- 14.2.2
Router restore should take priority over pending actions
- 14.2.2
Improve turborepo caching
- 14.2.2
Update lockfile for compatibility with turbo
- 14.2.2
Disable production chunking in dev
- 14.2.2
hotfix(turbopack): Update with patch for postcss.config.js path resolution on Windows
2 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.