next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 15.2.0 to 15.2.1
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 3
- new
- 20
- fixes
Before you upgrade
Tick each one off as you go- Breaking15.2.1
Security
41 advisories still affect 15.2.1
- 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 15.5.29 clears them.
Release by release
- Breaking
Remove
revalidateproperty from incremental cachectxforFETCHkind - New
Implement hash-only navigations
- New
Support output: "export" mode
- New
Turbopack: Add test test for css order
- Breaking
22 other lines we could not sort, mostly version bumps
- 15.2.1
Unify Link and Form prefetching
- 15.2.1
Control dark theme in one place
- 15.2.1
Change css var for terminal
- 15.2.1
Discriminate stack frame settled typed
- 15.2.1
Remove obsolete
sourcePackagereferences - 15.2.1
Webpack: Abstract away getting compilation spans
- 15.2.1
Report compiler duration for webpack and improve numbers
- 15.2.1
Omit from bundle if flag disabled
- 15.2.1
Refresh on same-page navigation
- 15.2.1
re-enable streaming metadata with PPR
37 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.