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 for chunking and HMR, along with various test stability fixes and typo corrections. Several internal tooling and documentation updates were also included.
Developers using Next.js canary builds may benefit from Turbopack improvements and test stability fixes.
Test the canary build for Turbopack-related improvements if using experimental features.
This canary release of Next.js includes various fixes for debug build paths, middleware redirect routes, and Turbopack runtime initialization. It also addresses issues with stale data after navigation and allows literal exports in 'use cache' files.
Developers using the canary version of Next.js may encounter fixes for debug build paths, middleware redirect routes, and Turbopack runtime initialization.
Update to this canary version if you are experiencing issues with debug build paths, middleware redirect routes, or Turbopack runtime initialization.
This release focuses on internal optimizations and updates, including decoupling loader tree construction and improvements to Turbopack's cache handling.
Developers using Turbopack or loader tree construction may benefit from performance improvements.
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 release focuses on bug fixes, documentation improvements, and minor refactoring. Notable changes include encoding cache item names, renaming APIs, and fixing various typos and formatting issues.
Developers using Next.js may benefit from improved debugging, caching, and route tracing capabilities.
This canary release of Next.js includes a minor change related to Turbopack's handling of constants.
Developers using Turbopack may be affected by changes in how constants are handled.
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 canary release focuses on Turbopack improvements, Server Actions handling, and minor bug fixes. It includes enhancements to DiskWatcher configuration, shared runtime enablement, and CJS tree shaking by default.
Developers using Turbopack or Server Actions in Next.js may benefit from these updates.
This canary release includes several fixes for Turbopack and Pages Router SSR, addressing issues with module naming, error handling, and style application.
Developers using Next.js with Turbopack or Pages Router SSR may be affected by the fixes.
Update to this canary release to benefit from the fixes if you encounter the mentioned issues.
This release ports ReplyServer traversal guards to FlightClient, improving consistency between server and client behavior.
Users of Next.js 15.x may be affected by changes in FlightClient behavior.
Update to v15.5.23 to benefit from the latest fixes.
This canary release focuses on internal refactoring and unification of navigation response types and client-side data structures. It also introduces automated update pull requests and removes an experimental scroll handler configuration.
Developers using `config.experimental.appNewScrollHandler` will need to update their configurations.
Update configurations to remove references to `config.experimental.appNewScrollHandler`.
This canary release introduces several breaking changes by removing or replacing execution modes, while also adding new features to improve rendering pipelines and prefetch policies.
Developers using WorkStore execution mode, cache revalidation execution mode, or App Page execution mode are affected by breaking changes.
Review breaking changes and update code accordingly if using deprecated execution modes.
This release includes fixes for Turbopack worker chunk loading with asset prefix and updates to react-sync pull request handling.
Developers using Turbopack with asset prefixes or relying on react-sync pull request automation are affected.
Update to this canary release to benefit from the fixes.
This canary release includes several Turbopack improvements and updates React to a newer version. It also contains miscellaneous fixes and documentation updates.
Developers using Turbopack or specific React versions may be affected by the changes.
Update to this version if you are using Turbopack or need the latest React changes.
This canary release includes several documentation corrections and improvements to dynamic navigation and static generation features. Turbopack also sees updates to its runtime chunk handling and exports behavior.
Developers using dynamic navigation and static generation features may be affected by the changes.
Review the changes related to dynamic navigation and static generation if your application uses these features.
This release fixes an issue where catch-all index pages were incorrectly served for every other slug.
Developers using catch-all index pages may have experienced incorrect routing behavior.
Update to this version to resolve the catch-all index page routing issue.
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 canary release enables Turbopack's filesystem cache by default, which should improve build performance for developers using Turbopack.
Developers using Turbopack in Next.js may see improved build performance due to filesystem caching.
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.
This canary release of Next.js includes various improvements, such as enabling `turbopackFileSystemCacheForBuild` by default, fixing component chunks for workers, and upgrading React. It also introduces documentation for `experimental.turbopackChunking` and stabilizes test checks.
Developers using Next.js with Turbopack or React may be affected by these changes.
Update to this canary release to test new features and improvements.