next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.5.11 to 14.0.0
1 release in betweenevery note read
- 9
- changes to make
- 0
- advisories fixed
- 27
- new
- 42
- fixes
Start here
Before you upgrade
Tick each one off as you go- Breaking14.0.0
- Breaking14.0.0
- Breaking14.0.0
- Breaking14.0.0
- Breaking14.0.0
- Breaking14.0.0
- Breaking14.0.0
- Deprecated14.0.0
- Deprecated14.0.0
Security
36 advisories still affect 14.0.0
- 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
- Breaking
Drop Node.js 16
- Breaking
next/image: Mark
onLoadingCompleteas deprecated in favor ofonLoad - Breaking
next/image: Mark
domainsas deprecated in favorremotePatterns - Breaking
Remove the experimental
serverActionsflag
- Breaking
73 other lines we could not sort, mostly version bumps
- 14.0.0
Update React from d900fadbf to 09fbee89d. Removes server context and experimental prefix for server action APIs
- 14.0.0
Update Babel dependencies
- 14.0.0
Adding <GoogleTagManager> component to @next/third-parties
- 14.0.0
Replace
Promise.withResolverspolyfill withDetachedPromise - 14.0.0
Reland "feat(turbopack): support basic next/dynamic"
- 14.0.0
Web Streams cleanup
- 14.0.0
Improve performance of String.prototype.split uses
- 14.0.0
Move ImageResponse to next/og
- 14.0.0
Prefer module over main on main fields for app router server compiler
- 14.0.0
Bump packages version to match canary versions
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.