next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 14.0.1 to 14.0.2
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 8
- new
- 26
- fixes
Before you upgrade
Tick each one off as you go- Breaking14.0.2
Security
36 advisories still affect 14.0.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.
- 14.0.2
Improve CSRF protection error in Server Actions
Release by release
- Security
Improve CSRF protection error in Server Actions
- Breaking
Remove legacy handling for suspense option of next/dynamic
- New
Add @highlight-run/node to externals list
- New
Change the chunks configuration for server code
- Security
27 other lines we could not sort, mostly version bumps
- 14.0.2
Serialize trace info across workers to preserve .next/trace with webpackBuildWorker
- 14.0.2
Remove the
actionBrowserto RSCclientlayering issue - 14.0.2
Revert "perf: enable webpack build worker (#57346)"
- 14.0.2
Polish logging segments of page route
- 14.0.2
Inherit title and description from metadata into social cards
- 14.0.2
ppr: Fail static generation if postponed & missing postpone data
- 14.0.2
Reduce FS access for incremental cache
- 14.0.2
Suspend in render, not in reducers
- 14.0.2
Move static worker IPC server behind experimental flag
- 14.0.2
Improve grammar of removable Babel config warning
58 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.