next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 16.0.2 to 16.0.3
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 8
- new
- 24
- fixes
Before you upgrade
Tick each one off as you go- Breaking16.0.3
Security
48 advisories still affect 16.0.3
- Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are usedcritical · GHSA-2464-fhr4-w9xw
- Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routeshigh · GHSA-267c-6grr-h53f
- Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Uphigh · GHSA-26hh-7cqf-hhc6
Upgrading to 16.4.5 clears them.
Release by release
- Breaking
Turbopack: Remove
non_operation_vc_strongly_consistentfeature usage from next-api - New
Allow inspecting dev server on default port with
next dev --inspect - New
Support relative paths in turbopack source maps.
- New
Enable React's default Transition indicator behind a flag
- Breaking
19 other lines we could not sort, mostly version bumps
- 16.0.3
Cache the head separately from the route tree
- 16.0.3
Move generation of
cacheLifetypes out of the webpack plugin and into the dev bundler directly - 16.0.3
Update parallel routes in build-complete
- 16.0.3
Fully remove clientSegmentCache flag
- 16.0.3
Release unnecessary memory on hydration finish
- 16.0.3
Preserve interception markers in parameter types
- 16.0.3
Move segment cache entries to top level segment-cache dir
- 16.0.3
Remove title from preferences
- 16.0.3
Update font data
- 16.0.3
Remove unused RSC payload property
109 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.