next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.4.3 to 13.4.4
1 release in betweenevery note read
Security
36 advisories still affect 13.4.4
- 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
x-forwarded-*headers to turbopack renders - New
Add optional generic parameter to NextResponse
- New
turbopack: Initial sass-loader support
- New
Add warning for edge with force-static
- New
18 other lines we could not sort, mostly version bumps
- 13.4.4
Pages Module Transition
- 13.4.4
Error in next export when serverActions is enabled
- 13.4.4
turbopack: Update renamed SubpathValue
- 13.4.4
Always defer close tags to be the suffix of body stream
- 13.4.4
Remove node-sass from peerDependencies
- 13.4.4
create-next-app: Respecting the user's
init.defaultBranchgit con… - 13.4.4
Move debugging variable into useEffect
- 13.4.4
Refactor webpack loaders
- 13.4.4
Change static path to /_next/static/media
- 13.4.4
Revert "feat(next-swc): Implement CJS optimizer"
15 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.