2026-08-02 · Article

next.js breaking changes and release tracker

Every breaking and material change in next.js over the last 365 days, quoted from the official Next.js release notes.

By Tech Sight

next.js moves often, and the release that costs you an afternoon is rarely the one with an announcement. This page tracks every change we classify as breaking or material, quoted from the Next.js release notes so you can check it yourself.

Covering the last 365 days: 1 breaking, 3 material.

Breaking changes

v16.3.0 — 2026-08-03

fix(devtools): detect VS Code renamed macOS binary in launch-editor: #93971

Release notes

Material changes worth reading

Deprecations, security fixes and migrations. Not breaking today, but the ones that become breaking later.

v16.3.0-canary.106 — 2026-08-01

Warn that experimental.useCache is deprecated: #96448

Release notes

v16.3.0-preview.10 — 2026-07-28

fix: remove deprecated url.parse() from custom-server example: #96105

Release notes

v16.3.0-canary.95 — 2026-07-23

fix: remove deprecated url.parse() from custom-server example: #96105

Release notes

How these are classified

Breaking means the vendor's own notes say so in plain language, or the package crossed a major version. Material means a deprecation, a security fix, or a migration note. A routine minor bump is neither, because flagging every release is how people learn to ignore alerts.

We do not claim to know about a change before it ships. What we do is read the release the moment it is published and tell you whether it matters.

Get next.js changes as a feed

This page is free and refreshes as new releases land. If you would rather have the signal delivered than remember to check, the paid feed returns these same classified next.js changes as JSON over an authenticated API, ready for CI, a Slack channel or your own dashboard.

TechSight Data Feeds — Pro, $29/month. Cancel any time; access is issued and revoked automatically.

Also tracked: the cross-SDK breaking-changes roundup.