next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.3.0 to 13.3.1
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 24
- new
- 30
- fixes
Before you upgrade
Tick each one off as you go- Breaking13.3.1
Security
32 advisories still affect 13.3.1
- 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
- Breaking
Drop object config export support for app dir
- New
Support og image with edge
- New
Add flag to control app document preloading
- New
Add experimental React related warning
- Breaking
52 other lines we could not sort, mostly version bumps
- 13.3.1
Change metadata routes suffix to number and chars
- 13.3.1
Update query param prefix to reduce length
- 13.3.1
turbopack: Bind server to IPv6 loopback
- 13.3.1
turbopack: Pass ENV vars to route handlers
- 13.3.1
Parallel routes: fix layout not re-rendering
- 13.3.1
Next Cache Telemetry
- 13.3.1
Remove change leftover from experimental precompiled server
- 13.3.1
Re-land "Vendor
react@experimentalunder anexperimentalReactflag" - 13.3.1
Update next/font/google data
- 13.3.1
Remove warning for metadataBase fallback
32 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.