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/
loading releases…
releases
breaking
security
deprecated
migrations
The React Framework for the Web StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Next.js release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This canary release focuses on Turbopack improvements, bug fixes, and documentation updates. Notable changes include optimizations for CJS tree-shaking in Turbopack and fixes for optimistic routing bugs.
Developers using Turbopack or legacy PPR code paths may be affected by changes and deprecations.
Review deprecations and update code to avoid using legacy PPR paths.
This canary release of Next.js focuses on Turbopack improvements and documentation updates, including fixes for potential deadlocks and better handling of async modules.
Developers using Turbopack or static exports in Next.js may be affected by these changes.
Update to this canary version to benefit from Turbopack improvements and follow the updated documentation for static exports.
This release focuses on bug fixes, performance improvements, and Turbopack enhancements. Key changes include a security fix for lodash, improvements to Turbopack's HMR and CSS handling, and various optimizations for server-side rendering and routing.
Developers using lodash or Turbopack are most affected by this release.
Update lodash to 4.17.23 to mitigate CVE-2025-13465.
This release includes a deprecation warning for `experimental.useCache` and fixes hybrid Pages/App Router not-found rendering with adapters.
Developers using `experimental.useCache` or hybrid Pages/App Router not-found rendering with adapters are affected.
Update code to avoid using `experimental.useCache` and verify hybrid Pages/App Router not-found rendering behavior.