next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.4.1 to 13.4.2
1 release in betweenevery note read
Security
36 advisories still affect 13.4.2
- 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 typescript version to next-info
- New
app-router: Add startTransition call to revalidate dispatcher
- New
Add link to Server Actions docs.
- New
Add request-async-storage to the shared layer
- New
15 other lines we could not sort, mostly version bumps
- 13.4.2
Make sure server component externals only apply to files resolvable by node
- 13.4.2
Remove empty config warning
- 13.4.2
Inline static data buffer instead of using fs read
- 13.4.2
Replace metadata clone with custom handler in dev
- 13.4.2
Restrict
useOptimisticanduseFormStatusAPIs on the server layer - 13.4.2
type: Update React.CSSProperties type to Record
- 13.4.2
actions: Forward fetch rejections to the action handler
- 13.4.2
actions: Make cookies.set revalidate
- 13.4.2
Interception route: fix route groups breaking the referrer computation
- 13.4.2
Update cache method handling during build
16 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.