next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 15.2.9 to 15.3.0
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 31
- new
- 65
- fixes
Before you upgrade
Tick each one off as you go- Deprecated15.3.0
Security
40 advisories still affect 15.3.0
- 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
- Deprecated
Add deprecation warning for legacyBehavior prop
- New
metadata: Add pinterest meta tag
- New
Turbopack: Implement deploymentId
- New
Add
sizesetting to preferences
- Deprecated
94 other lines we could not sort, mostly version bumps
- 15.3.0
Customize
<select>styling for consistency - 15.3.0
Apply env inlining during generate build mode
- 15.3.0
Track persistent caching usage
- 15.3.0
re-insert icons to head for streamed metadata
- 15.3.0
Move static-env imports
- 15.3.0
Unify allowed origin detection handling
- 15.3.0
Highlight errored code line for runtime errors
- 15.3.0
NFT: Ignore all of Webpack
- 15.3.0
(feat) support client-side instrumentation
- 15.3.0
Slightly improve error handling for unknown server actions
110 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.