next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.0.7 to 13.1.0
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 11
- new
- 8
- fixes
Before you upgrade
Tick each one off as you go- Breaking13.1.0
Security
29 advisories still affect 13.1.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
Remove devcontainer network host argument
- New
Add tracing for testing tools
- New
App dir error-global component
- New
Add lodash to server components external packages
- Breaking
18 other lines we could not sort, mostly version bumps
- 13.1.0
Hash both pitch and main loader for server CSS imports
- 13.1.0
Run packing in tests in parallel
- 13.1.0
Revert "Remove
useStatefromnext/image(#43587)" - 13.1.0
Should not contain pages css in app dir
- 13.1.0
Upgrade undici to 5.14.0 to fix fetch redirect bug
- 13.1.0
Align onRecoverableError callback between pages and app dir
- 13.1.0
Update styled-jsx
- 13.1.0
Also check error.message as digest for recoverable errors in pages
- 13.1.0
Move options to stable
- 13.1.0
Move
transpilePackagesout of experimental
30 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.