next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.1.2 to 13.1.3
1 release in betweenevery note read
Security
29 advisories still affect 13.1.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
- New
Add built-in server-only and client-only
- New
Add experimental.allowedRevalidateHeaderKeys config
- New
Add proper error when app path switches static to dynamic
- New
Add project directory rename/remove handling
- New
11 other lines we could not sort, mostly version bumps
- 13.1.3
Refactor next dynamic
- 13.1.3
Update pre-compiled
- 13.1.3
Use sequentialRead while encoding images with sharp
- 13.1.3
Move server-external-packages to JSON
- 13.1.3
Custom RSC compiler error message in pages/
- 13.1.3
Replace eslint rule for
no-shadowwithtypescript-eslint/no-shadow - 13.1.3
Use withoutEnlargement instead of sharp.metadata()
- 13.1.3
Update res.revalidate to pass through headers
- 13.1.3
Gracefully handle telemetry not being available
- 13.1.3
Remove next-app-loader from import trace
24 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.