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 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 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.