next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.4.2 to 13.4.3
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 6
- new
- 10
- fixes
Before you upgrade
Tick each one off as you go- Deprecated13.4.3
Security
36 advisories still affect 13.4.3
- 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
- Deprecated
next-core: Deprecate custom_ecmascript_transforms
- New
Optimize trace span relationships
- New
Add @swc/core to server external packages
- New
Add support for globally providing mdx components to turbopack
- Deprecated
12 other lines we could not sort, mostly version bumps
- 13.4.3
Remove old-space-size filtering from dev server
- 13.4.3
Rework client router filter handling
- 13.4.3
Apply user-defined PostCSS transforms to foreign code
- 13.4.3
turbo-binding->turbopack-binding - 13.4.3
Refactor pages structure
- 13.4.3
Port sorted-routes.ts to Rust
- 13.4.3
Move build workers count change behind flag
- 13.4.3
Update default for appDocumentPreloading config for minimalMode
- 13.4.3
Error in
next exportwhenserverActionsis enabled - 13.4.3
Reset not-found and error boundary when navigating
13 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.