what stackpulse tracks
Next.js releases from GitHub
StackPulse watches Next.js release notes and keeps the original source link close to every summary.
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 removes stale `.next/dev/types` artifacts during `next typegen` and `next build`. It also simplifies conditional deployment-ID code generation and includes several Turbopack backend and persistence changes.
Developers using `next typegen` or `next build` may see stale development type artifacts removed; other listed changes concern Turbopack internals.
This canary release includes one miscellaneous change to the turbo-tasks backend: it releases the owner task before the reader side of keyed refinement. The notes provide no further details about the change or its user-facing impact.
The change affects the turbo-tasks backend; the release notes do not specify which users or workflows are affected.
This canary enables Turbopack minification before chunking and Turbopack garbage collection by default, alongside improvements to manifests, memory handling, and route reporting. It also fixes RSC navigation and runtime prefetches in `next start`, image LCP loading-state checks, and repeated prerenders during fallback-shell revalidation.
Canary users of Next.js, particularly those using Turbopack, `next dev`, or RSC navigation and prefetching with `next start`, are affected.
Canary users should test the new default Turbopack behaviors and update any code that depends on the removed `durability` property.
This canary release includes fixes and optimizations across Next.js, Turbopack, and its task and persistence systems. It also updates React and improves build diagnostics, metadata resolution, prerendering, and link linting; the notes do not identify breaking changes or security fixes.
Next.js canary users and contributors may see improved build and prerender behavior, updated React, and Turbopack performance and reliability improvements.
This canary release includes core fixes for prerendering route handlers that await immediates, detached telemetry flush processes, and persistence of dev overlay errors across no-op webpack hot updates. It also upgrades React and includes Turbopack and task-system improvements, alongside documentation and test updates.
Next.js canary users may benefit from prerendering and development overlay fixes, as well as internal Turbopack and task-system improvements.
This canary release fixes Next.js image distortion detection by using intrinsic proportions and adds CPU profile output for static workers during `next build`. It also includes Turbopack and turbo-tasks fixes and improvements; the notes do not describe a breaking change or a security fix.
Next.js canary users may benefit from improved image distortion detection and build profiling, while Turbopack and turbo-tasks users receive additional fixes and improvements.
This canary release includes fixes to route prediction, prerender response statuses, fetch-cache lock handling, the development overlay’s npm registry check, and deployed RSC responses after static-to-partial revalidation. It also includes Turbopack and test-infrastructure changes, plus an improvement to the commands shown after creating an app from a template.
Next.js canary users may benefit from fixes to routing, prerendering, caching, RSC responses, and the development overlay; create-next-app users also get clearer next steps after template-based setup.
This backport release includes fixes for development-mode Turbopack garbage collection and automatically compresses route handler responses when they are not already compressed. It also pins Tailwind to 4.3.3 in create-next-app and tests; the release does not include all pending canary features or changes.
Next.js users may benefit from route handler response compression and improved Turbopack garbage collection during development; create-next-app and tests use Tailwind 4.3.3.
This canary release adds Turbopack support for `turbopackIgnore` on `new URL()`. It also includes task-storage capacity management and an internal Turbopack AST-path storage change, plus a documentation clarification.
Users of Turbopack who use `turbopackIgnore` with `new URL()` are affected by the added support.
This canary release primarily updates documentation, clarifying client cache behavior, Cache Components configuration errors, and Image priority migration choices. It also updates a dependency and upgrades the Rust toolchain.
Users consulting Next.js documentation may benefit from the clarifications; the notes do not describe behavior changes affecting application code.
This canary release improves prerendered Link header handling during revalidation and reduces header allocations in NodeNextResponse. It also changes the image optimizer transform package path and includes updates to Request Insights, build analysis, Turbopack, and documentation.
Next.js canary users working with the image optimizer transform public API, prerendered links, or Request Insights are most directly affected.
Update imports if you use `next/image-optimizer-transform`, following its move to the `next/experimental` namespace.
This prerelease improves Request Insights with persistent session history, route-module loading and preparation details, and more request and fetch information. It also adds automatic compression for route-handler responses that are not already compressed and includes several Turbopack and tooling fixes.
Next.js users, particularly those using Request Insights, route handlers, or `next/image-optimizer-transform`, may be affected.
If your code imports `optimizeImage` from `next/image-optimizer-transform`, review and update that usage because the release removes it from the public API.
This canary adds internal image redirects to `next/image` and introduces Request Insights filters and pause controls. It also includes Turbopack, tracing, image-optimizer, and configuration improvements, plus assorted fixes.
Next.js canary users are affected, particularly those using `experimental.lockDistDir` or the updated image and Request Insights functionality.
If your configuration uses `experimental.lockDistDir`, remove that option before upgrading.
This canary release adds `instrumentationInject` for adapter-supplied instrumentation and experimental support for App Router `route.go` handlers. It also improves build-trace performance and includes fixes for server actions and the Turbopack task snapshot loop.
Adapter authors and developers experimenting with App Router `route.go` handlers may be affected; the release also includes build and internal reliability improvements.
This canary release fixes several cache and request-handling issues, including cache key and cross-root-parameter reuse bugs, shared-shell poisoning, and forwarded-response framing. It also fixes image format detection and includes Turbopack and tooling improvements; the notes describe no explicit user-facing migration steps.
Applications using Next.js caching, middleware, forwarded fetch responses, next/image, or Turbopack may benefit from the fixes; no broader impact is specified.
Consider updating to this canary if affected by the listed cache, middleware, response-framing, or image-detection issues.
This release contains security fixes addressing seven moderate advisories. The issues affect caching, response handling, image optimization, and cookie exposure in Edge runtime routes.
Applications using Next.js may be affected, particularly those relying on 'use cache', forwarded fetched responses, image optimization, or Edge runtime routes.
Upgrade to Next.js 16.4.5 to receive the listed security fixes.
This release contains security fixes for three moderate-severity vulnerabilities. The issues affect forwarded fetched responses in self-hosted applications, SVG rejection in image optimization, and exposure of HttpOnly cookies through an internal response header in Edge runtime routes.
Self-hosted Next.js applications forwarding fetched responses, applications using image optimization, and applications with Edge runtime routes may be affected.
Upgrade to Next.js 15.5.29 to receive these security fixes.
This canary release fixes blocking revalidation for `fetch` and `unstable_cache`. It also includes Turbopack and turbo-tasks improvements, fixes layout client chunk leakage across async server imports, and pins Tailwind to 4.3.3 in `create-next-app`.
The changes affect Next.js users relying on `fetch` or `unstable_cache` revalidation, as well as users of Turbopack and `create-next-app`.
Consider upgrading to this canary if you are affected by blocking revalidation issues.
This canary adds the experimental `router.experimental_prepare()` API and a Turbopack experimental minify-before-chunking feature. It also includes fixes for ISR navigation rerenders, cache revalidation with short stale times, registry version checks, and Turbopack lazy-compilation invalidation.
Next.js canary users, particularly those using the App Router, ISR, or Turbopack, may see the new experimental options and fixes.
This is a backport release of bug fixes and does not include all pending changes on canary. It fixes Turbopack CSS update handling and ensures the shared-runtime bootstrap in PPR resumes receives the CSP nonce, along with analyzer, deployment-test, and JWT-library changes.
Next.js users on the 16.4.4 release line may benefit from the backported fixes, particularly those using Turbopack or PPR resumes.