next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.4.7 to 13.4.8
1 release in betweenevery note read
Security
37 advisories still affect 13.4.8
- 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
Support for numeric separators in revalidate config
- New
Support response aborting
- New
Add edge rendering for app dir for Turbopack
- New
Add esm entry for next/server and alias @vercel/og
- New
33 other lines we could not sort, mostly version bumps
- 13.4.8
Auto fill title/images/description from openGraph for twitter if missing
- 13.4.8
Route Module Updates
- 13.4.8
Next Build Turbo POC (2)
- 13.4.8
bugfix: Route interception with dynamic paths
- 13.4.8
Pages Error Route Module Rendering
- 13.4.8
Revert "add edge rendering for app dir for Turbopack"
- 13.4.8
Update cache handling in draft mode
- 13.4.8
Hot reload when conflicted pages detected and when conflicts are resolved
- 13.4.8
Type check tests (and convert next-test-utils.js to ts)
- 13.4.8
Move Pages
renderout of server
58 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.