next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 15.0.0 to 15.0.1
1 release in betweenevery note read
Security
41 advisories still affect 15.0.1
- 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 --turbopack CLI flag
- New
Enable source maps for
pnpm debug - Fixed
Avoid triggering memory leak false positive with makeHangingPromise
- Fixed
Avoid logging stacks for internal errors
- New
8 other lines we could not sort, mostly version bumps
- 15.0.1
Reland "[dynamicIO] warn for disallowed dynamic in dev"
- 15.0.1
next-upgrade: Prompt (un)install only when there's a change
- 15.0.1
Update prerender to use Fizz prerender
- 15.0.1
misc(next-upgrade): reuse process.cwd() value
- 15.0.1
dynamicIO: Dev navigations should show disallowed dynamic errors
- 15.0.1
next-lint: Use ESLint v9 by default
- 15.0.1
Improve type coverage of setup-dev-bundler
- 15.0.1
Detect metadata boundaries in dev using server component stacks
12 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.