What changed in next.js, release by release
The lines under each release are next.js's own release-note bullets with pull request numbers, names and links removed, grouped by its own headings. Wording is theirs. Not affiliated with next.js.
v16.5.0-canary.54 (pre-release)
- FixedPrefer exact pathnames after rewrites
- ChangedReject the experimental testing API opt-in without Cache Components
- ChangedPreserve CSP nonces on static fallback bootstrap scripts
v16.5.0-canary.53 (pre-release)
- ChangedLint against new as any casts and require a reason to disable it
- Changed[no-unsafe-inline] Stop inlining the Turbopack chunk group bootstrap
v16.5.0-canary.52 (pre-release)
- ChangedRemove stale .next/dev/types in next typegen and next build
- ChangedSimplify the code gen that adds deployment ids conditionally
v16.5.0-canary.51 (pre-release)
- ChangedTurbo-tasks-backend: release the owner task before the reader side of keyed refinement
v16.5.0-canary.50 (pre-release)
- FixedCheck the LCP element loading state
- ChangedEnable turbopackMinifyBeforeChunking by default on canary releases
- ChangedTurbopack: write smaller/faster client reference manifests
v16.5.0-canary.49 (pre-release)
- ChangedOptimize NFT base path mapping
- ChangedFix ImageResponse prerendering with --debug-prerender
v16.5.0-canary.48 (pre-release)
- ChangedPrerender route handlers that await immediates
- ChangedFix orphaned detached telemetry flush processes
v16.5.0-canary.47 (pre-release)
- FixedDetect distortion using intrinsic proportions
- ChangedWrite CPU profiles for next build static workers
- ChangedTurbo-tasks-backend: process aggregation edge removals after additions and balancing
v16.5.0-canary.46 (pre-release)
- ChangedResolve parallel route params from the URL when predicting routes
- ChangedPrevent prerenders from changing foreground response status
v16.4.6
- Changed[lts-active] Pin Tailwind to 4.3.3 in create-next-app and tests
- Changed[lts-active] Automatically compress route handler responses if not already compressed
How we calculate
- Days between releases: The median of the gaps, in days, between the release dates listed above.
Data: vercel/next.js's GitHub releases page, read November 18, 2026. Every other figure on this page is copied from the record, not calculated by us.
Get this for your repo, every release
next.js publishes release notes that people can read. FoxPlug writes yours from what you ship: a changelog entry and posts for the places your users are, each approved by you.
Get this for your repo, every releaseTry it on your repo nowYour changelog, written for you
FoxPlug writes your changelog from your releases and commits in plain English and publishes it as a page and a feed your users can follow. The page above shows what that looks like for a product people really use.
Write my changelog See the changelog FoxPlug wrote from its own commits
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Written from your releases and commits, in plain English your users read
- Connect GitHub and new releases become new entries