next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.1.5 to 13.1.6
1 release in betweenevery note read
Security
29 advisories still affect 13.1.6
- 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 debug info to static bailout message
- New
Add build time error if error.js is missing "use client"
- New
Avoid sync re-renders when using next/link and next/image
- New
Support metadata icons field
- New
17 other lines we could not sort, mostly version bumps
- 13.1.6
Show component stack in error overlay on hydration error
- 13.1.6
Reduce component stack spacing for components without metadata
- 13.1.6
Revert "Revert "Revert "Revert "Initial support for metadata (#44729)"" (#45113)""
- 13.1.6
Update handling of autoscrolling on navigation in app
- 13.1.6
misc: Change strategy for link prefetch test
- 13.1.6
Update transform exports and tests
- 13.1.6
Attach exports information in SWC transforms
- 13.1.6
Update app cache handling in development
- 13.1.6
TS plugin: warn about
ampconfig in app - 13.1.6
Improve
fetchstack traces in edge runtime
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.