what stackpulse tracks
Next.js releases from GitHub
StackPulse watches Next.js release notes and keeps the original source link close to every summary.
#stacks/nextjs/framework
Next.js release notes, breaking changes, and upgrade notes.
The React Framework for the Web StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
releases
20
breaking
1
security
0
deprecated
2
migrations
0
upgrade risk
Breaking changes and deprecations
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Source-backed next steps
Migration steps and recommended actions are only shown when the upstream release notes support them.
# latest_releases
source-backedv16.3.0-canary.61mediumbreakingdeprecationfeatureprereleaseJun 23, 2026
v16.3.0-canary.61
This canary release includes various fixes and improvements, such as statically prerendering metadata image routes under Cache Components and upgrading React. It also removes legacy PPR codepaths and adds a global opt-in for Cached Navigations.
affected
Users relying on legacy PPR codepaths or the turbopack edge runtime will be affected.
action
Update code to use the new self-contained runtime and migrate away from legacy PPR codepaths.
release_signals
-Remove legacy PPR codepaths
-[turbopack] Rename the edge runtime to the self-contained runtime
!Remove legacy PPR codepaths
+Statically prerender metadata image routes under Cache Components
+Add a global opt-in for the runtime stage of Cached Navigations
+[turbopack] Rename the edge runtime to the self-contained runtime