next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.2.4 to 13.3.0
1 release in betweenevery note read
- 2
- changes to make
- 0
- advisories fixed
- 67
- new
- 90
- fixes
Before you upgrade
Tick each one off as you go- Breaking13.3.0
- Breaking13.3.0
Security
30 advisories still affect 13.3.0
- 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
Bump minimum ts version to 4.5.2
- Breaking
Remove experimental fontLoaders option from next.config.js
- New
Add Zod and router state validation
- New
Support default arrow function export in server boundary #46977
- Breaking
98 other lines we could not sort, mostly version bumps
- 13.3.0
Generate fixed route path for favicon.ico
- 13.3.0
Update turbopack
- 13.3.0
Update next/font/google data
- 13.3.0
Reorganize client references manifest
- 13.3.0
Opt-in to dynamic rendering when reading searchParams
- 13.3.0
i18n Improvements
- 13.3.0
Split app-render functions into separate files
- 13.3.0
Limit the api surface of
util - 13.3.0
Parallel routes: fix duplicate dev warning
- 13.3.0
next/font/local prep: compartmentalize next/font/google
120 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.