Next.js Updates & Release Notes
72 updates curated from 2 sources by the Releasebot Team. Last updated: Jun 1, 2026
- Jun 1, 2026
- Date parsed from source:Jun 1, 2026
- First seen by Releasebot:Jun 1, 2026
v16.2.7
Next.js ships a 16.2 backport release focused on bug fixes and stability, with documentation updates, hydration and router fixes, cache tag encoding improvements, server action and middleware fixes, Turbopack changes, and FormData handling improvements.
Note
This release is backporting bug fixes. It does
not
include all pending features/changes on canary.Core Changes
- Backport documentation fixes for v16.2 (#93804)
- [backport] Patch playwright-core to resolve _finishedPromise on requestFailed (#93920)
- [backport] Fix dev mode hydration failure when page is served from HTTP cache (#93492)
- [backport] Fix catch-all router.query corruption with basePath + rewrites (#93917)
- [backport] Encode non-ASCII characters in cache tags at construction (#93918)
- [backport] Fix server action forwarding loop with middleware rewrites (#93919)
- [backport] Turbopack: switch from base40 to base38 hash encoding (#93932)
- [ci] Disable hanging node 24 typescript tests on 16.2 backport branch (#94164)
- [backport] Fix "type: module" in project dir when using standalone or adapters (#94050)
- [backport] Propagate adapter preferred regions (#94200)
- [16.2.x] Don't drop FormData entries (#94240)
- [backport] feat(turbopack): add LocalPathOrProjectPath PostCSS config resolution (#94284)
Credits
Huge thanks to @eps1lon, @icyJoseph, @unstubbable, @mischnic, @bgw, @timneutkens, and @lukesandberg for helping!
Original source - Jun 1, 2026
- Date parsed from source:Jun 1, 2026
- First seen by Releasebot:Jun 1, 2026
v15.5.19
Next.js backports bug fixes to improve FormData handling and CI stability.
Note
This release is backporting bug fixes. It does
not
include all pending features/changes on canary.Core Changes
- [15.5.x] Don't drop FormData entries (#94244)
Other
- [15.5.x] Fix CI (#94281)
Credits
Huge thanks to @eps1lon for helping!
Original source All of your release notes in one feed
Join Releasebot and get updates from Vercel and hundreds of other software products.
- May 5, 2026
- Date parsed from source:May 5, 2026
- First seen by Releasebot:May 12, 2026
v16.2.5
Next.js releases a security-focused patch with backported bug fixes, addressing multiple high, moderate, and low severity advisories across Server Components, App Router, Middleware and Proxy, image optimization, and cache handling while improving route and deployment behavior.
Note
This release contains security fixes and backported bug fixes. It does not include all pending features/changes on canary.
Security Fixes
The following advisories have been addressed:
High
- GHSA-8h8q-6873-q5fj: Denial of Service with Server Components
- GHSA-267c-6grr-h53f: Middleware / Proxy bypass in App Router applications via segment-prefetch routes
- GHSA-mg66-mrh9-m8jx: Denial of Service via connection exhaustion in applications using Cache Components
- GHSA-492v-c6pp-mqqv: Middleware / Proxy bypass through dynamic route parameter injection
- GHSA-c4j6-fc7j-m34r: Server-side request forgery in applications using WebSocket upgrades
- GHSA-36qx-fr4f-26g5: Middleware / Proxy bypass in Pages Router applications using i18n
Moderate
- GHSA-ffhc-5mcf-pf4q: Cross-site scripting in App Router applications using CSP nonces
- GHSA-gx5p-jg67-6x7h: Cross-site scripting in beforeInteractive scripts with untrusted input
- GHSA-h64f-5h5j-jqjh: Denial of Service in the Image Optimization API
- GHSA-wfc6-r584-vfw7: Cache poisoning in React Server Component responses
Low
- GHSA-vfv6-92ff-j949: Cache poisoning via collisions in React Server Component cache-busting
- GHSA-3g8h-86w9-wvmq: Middleware / Proxy redirects can be cache-poisoned
Core Changes
- fix: preserve HTTP access fallbacks during prerender recovery (#92231)
- Fix fallback route params case in app-page handler (#91737)
- Fix invalid HTML response for route-level RSC requests in deployment adapter (#91541)
- Patch setHeader for direct route handlers (#93101)
- Include deployment id in cacheHandlers keys (#93453)
- Fix double-encoding of URL pathname parts in client param parsing (#93491)
- May 7, 2026
- Date parsed from source:May 7, 2026
- First seen by Releasebot:May 7, 2026
- Modified by Releasebot:May 12, 2026
v16.2.6
Next.js ships security fixes and backported bug fixes, addressing multiple high, moderate, and low severity advisories along with core fixes for prerender recovery, route params, route handlers, cache keys, and client param parsing.
Note
This release contains security fixes and backported bug fixes. It does not include all pending features/changes on canary.
Security Fixes
The following advisories have been addressed:
High:
- GHSA-8h8q-6873-q5fj: Denial of Service with Server Components
- GHSA-267c-6grr-h53f: Middleware / Proxy bypass in App Router applications via segment-prefetch routes
- GHSA-26hh-7cqf-hhc6: Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up
- GHSA-mg66-mrh9-m8jx: Denial of Service via connection exhaustion in applications using Cache Components
- GHSA-492v-c6pp-mqqv: Middleware / Proxy bypass through dynamic route parameter injection
- GHSA-c4j6-fc7j-m34r: Server-side request forgery in applications using WebSocket upgrades
- GHSA-36qx-fr4f-26g5: Middleware / Proxy bypass in Pages Router applications using i18n
Moderate:
- GHSA-ffhc-5mcf-pf4q: Cross-site scripting in App Router applications using CSP nonces
- GHSA-gx5p-jg67-6x7h: Cross-site scripting in beforeInteractive scripts with untrusted input
- GHSA-h64f-5h5j-jqjh: Denial of Service in the Image Optimization API
- GHSA-wfc6-r584-vfw7: Cache poisoning in React Server Component responses
Low:
- GHSA-vfv6-92ff-j949: Cache poisoning via collisions in React Server Component cache-busting
- GHSA-3g8h-86w9-wvmq: Middleware / Proxy redirects can be cache-poisoned
Core Changes
- fix: preserve HTTP access fallbacks during prerender recovery (#92231)
- Fix fallback route params case in app-page handler (#91737)
- Fix invalid HTML response for route-level RSC requests in deployment adapter (#91541)
- Patch setHeader for direct route handlers (#93101)
- Include deployment id in cacheHandlers keys (#93453)
- Fix double-encoding of URL pathname parts in client param parsing (#93491)
- May 6, 2026
- Date parsed from source:May 6, 2026
- First seen by Releasebot:May 7, 2026
- Modified by Releasebot:May 13, 2026
v15.5.18
Next.js ships security fixes across Server Components, App Router, Middleware and Proxy, addressing denial of service, bypass, XSS, SSRF and cache poisoning issues to strengthen overall app safety.
This release contains security fixes for the following advisories:
High
- GHSA-8h8q-6873-q5fj: Denial of Service with Server Components
- GHSA-267c-6grr-h53f: Middleware / Proxy bypass in App Router applications via segment-prefetch routes
- GHSA-26hh-7cqf-hhc6: Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up
- GHSA-mg66-mrh9-m8jx: Denial of Service via connection exhaustion in applications using Cache Components
- GHSA-492v-c6pp-mqqv: Middleware / Proxy bypass through dynamic route parameter injection
- GHSA-c4j6-fc7j-m34r: Server-side request forgery in applications using WebSocket upgrades
- GHSA-36qx-fr4f-26g5: Middleware / Proxy bypass in Pages Router applications using i18n
Moderate
- GHSA-ffhc-5mcf-pf4q: Cross-site scripting in App Router applications using CSP nonces
- GHSA-gx5p-jg67-6x7h: Cross-site scripting in beforeInteractive scripts with untrusted input
- GHSA-h64f-5h5j-jqjh: Denial of Service in the Image Optimization API
- GHSA-wfc6-r584-vfw7: Cache poisoning in React Server Component responses
Low
- GHSA-vfv6-92ff-j949: Cache poisoning via collisions in React Server Component cache-busting
- GHSA-3g8h-86w9-wvmq: Middleware / Proxy redirects can be cache-poisoned
- Apr 16, 2026
- Date parsed from source:Apr 16, 2026
- First seen by Releasebot:Apr 16, 2026
v16.2.4
Next.js ships a backport release focused on bug fixes and stability, including Turbopack and compiler improvements, Safari cache-buster scoping, Windows ARM64 Google Fonts support, and better tracing and error messages.
Note
This release is backporting bug fixes. It does not include all pending features/changes on canary.
Core Changes
- chore: Bump reqwest to 0.13.2 (Fixes Google Fonts with Turbopack for Windows on ARM64) (#92713)
- Turbopack: fix filesystem watcher config not applying follow_symlinks(false) (#92631)
- Scope Safari ?ts= cache-buster to CSS/font assets only (Pages Router) (#92580)
- Compiler: Support boolean and number primtives in next.config defines (#92731)
- turbo-tasks: Fix recomputation loop by allowing cell cleanup on error during recomputation (#92725)
- Turbopack: shorter error for ChunkGroupInfo::get_index_of (#92814)
- Turbopack: shorter error message for ModuleBatchesGraph::get_entry_index (#92828)
- Adding more system info to the 'initialize project' trace (#92427)
Credits
Huge thanks to @Badbird5907, @lukesandberg, @andrewimm, @sokra, and @mischnic for helping!
Original source - Apr 8, 2026
- Date parsed from source:Apr 8, 2026
- First seen by Releasebot:Apr 9, 2026
v16.2.3
Next.js ships backported security and bug fixes, including stale ISR revalidation error reporting, a manifest.ts HMR fix, output asset deduplication, styled-jsx race condition fixes, and turbo-tasks-backend stability improvements.
Note
This release is backporting security and bug fixes. For more information about the fixed security vulnerability, please see https://vercel.com/changelog/summary-of-cve-2026-23869. The release does not include all pending features/changes on canary.
Core Changes
- Ensure app-page reports stale ISR revalidation errors via onRequestError (#92282)
- Fix [Bug]: manifest.ts breaks HMR in Next.js 16.2 (#91981 through #92273)
- Deduplicate output assets and detect content conflicts on emit (#92292)
- Fix styled-jsx race condition: styles lost due to concurrent rendering (#92459)
- turbo-tasks-backend: stability fixes for task cancellation and error handling (#92254)
Credits
Huge thanks to @icyJoseph, @sokra, @wbinnssmith, @eps1lon, and @ztanner for helping!
Original source - Apr 1, 2026
- Date parsed from source:Apr 1, 2026
- First seen by Releasebot:Apr 1, 2026
v16.2.2
Next.js backports bug fixes and select updates, including create-next-app CLI improvements, a new next.config.js option for serverFastRefresh, and Turbopack HMR fixes for app routes and metadata routes. It also includes TypeScript deprecations and Safari CSS HMR fixes.
Note
This release is backporting bug fixes. It does not include all pending features/changes on canary.
Core Changes
- backport: Move expanded adapters docs to API reference (#92115)
- Backport: TypeScript v6 deprecations for baseUrl and moduleResolution (#92130)
- [create-next-app] Skip interactive prompts when CLI flags are provided (#91840)
- next.config.js: Accept an option for serverFastRefresh (#91968)
- Turbopack: enable server HMR for app route handlers (#91466)
- Turbopack: exclude metadata routes from server HMR (#92034)
- Fix CI for glibc linux builds
- Backport: disable bmi2 in qfilter (#92177)
- [backport] Fix CSS HMR on Safari (#92174)
Credits
Huge thanks to @nextjs-bot, @icyJoseph, @ijjk, @gaojude, @wbinnssmith, @lukesandberg, and @bgw for helping!
Original source - Mar 25, 2026
- Date parsed from source:Mar 25, 2026
- First seen by Releasebot:Mar 27, 2026
Next.js Across Platforms: Adapters, OpenNext, and Our Commitments
Next.js runs across platforms and 16.2 brings a stable Adapter API, shared tests, and broader provider collaboration.
Next.js runs across platforms. 16.2 brings a stable Adapter API, shared tests, and a new model of collaboration across providers.
Original source - Mar 21, 2026
- Date parsed from source:Mar 21, 2026
- First seen by Releasebot:Mar 21, 2026
v16.2.1
Next.js ships a backport release focused on bug fixes, tightening docs, adapter outputs, server actions in standalone mode, layout segment optimization, and several Turbopack and metadata handling issues.
Note
This release is backporting bug fixes. It does not include all pending features/changes on canary.
Core Changes
- docs: post release amends (#91715)
- docs: fix broken Activity Patterns demo link in preserving UI state guide (#91698)
- Fix adapter outputs for dynamic metadata routes (#91680)
- Turbopack: fix webpack loader runner layer (#91727)
- Fix server actions in standalone mode with cacheComponents (#91711)
- turbo-persistence: remove Unmergeable mmap advice (#91713)
- Fix layout segment optimization: move app-page imports to server-utility transition (#91701)
- Turbopack: lazy require metadata and handle TLA (#91705)
- [turbopack] Respect {eval:true} in worker_threads constructors (#91666)
Credits
Huge thanks to @icyJoseph, @abhishekmardiya, @ijjk, @mischnic, @unstubbable, @sokra, and @lukesandberg for helping!
Original source - Mar 19, 2026
- Date parsed from source:Mar 19, 2026
- First seen by Releasebot:Mar 20, 2026
v15.5.14
Next.js backports bug fixes with image disk cache support and restored JSON response headers.
Note
This release is backporting bug fixes. It does not include all pending features/changes on canary.
Core Changes
- feat(next/image): add lru disk cache and images.maximumDiskCacheSize (#91660)
- Fix(pages-router): restore Content-Length and ETag for /_next/data/ JSON responses (#90304)
Credits
Huge thanks to @styfle and @lllomh for helping!
Original source - Mar 18, 2026
- Date parsed from source:Mar 18, 2026
- First seen by Releasebot:Mar 19, 2026
v16.2.0
Next.js releases a comprehensive v16.2 update highlighting React upgrades, Turbopack improvements, experimental routing, stricter type checks, and new performance and UX tweaks. It also expands config options, better error pages, and deployment outputs, signaling a broad, user-facing product evolution.
Tip
Check out our Next v16.2
Blog Post to learn more about this release.Core Changes
- Upgrade React from
f93b9fd4-20251217to65eec428-20251218: #87323 - Turbopack: Create junction points instead of symlinks on Windows: #87606
- Turbopack: Symlink handling follow-up: #87637
- Add experimental routing package for resolving adapter routes: #86404
- Ensure outputs are correct with cache components in deployment adapters: #87018
- Move off of deprecated url.parse: #87257
- [strict-route-types] Add
experimental.strictRouteTypesconfig: #87378 - misc: fix type check log for CI envs: #87838
- fix: revalidateTag with profile should not trigger client cache invalidation: #88069
- chore: warn when running tests against stale build: #88001
- Redesign default error pages with cleaner, more user-friendly UI: #87988
- dx: avoid next-env.d.ts change in dev: #88103
- prevent browser cache from using stale RSC responses from previous builds: #86554
- [strict-route-types] Typecheck App Router page props: #87386
- [strict-route-types] Enforce common React Component return types in App Router: #87389
- [strict-route-types] Switch to
satisfieswhen validating page and route modules: #87398 - [strict-route-types] Don't reject
numberinconfig.api.bodyParser.sizeLimitwhen validating route: #87633 - Revert "dx: avoid next-env.d.ts change in dev": #88153
- [strict-route-types] Typecheck pages router routes in absence of App Router: #87628
- [strict-route-types] Ensure cache profiles and routes are type-checked even if .next is excluded: #87768
- add compilation error for taint when not enabled: #88173
- feat(next/image)!: add
images.maximumResponseBodyconfig: #88183 - Add maximum size limit for postponed body parsing: #88175
- metadata: use fixed segment in dynamic routes with static metadata files: #88113
- feat: add --experimental-cpu-prof flag for dev, build, and start: #87946
- Add experimental option to use no-cache instead of no-store in dev: #88182
- fix overlay frames cannot be opened sometimes: #88210
- Handle pnpm-workspace.yaml while searching for monorepo root: #74818
- Add more debug logs to
use cachewrapper: #88219 - Omit unused arguments from
use cachefunction calls: #86920 - Only log
pending revalidates...debug log if applicable: #88221 - fix(next/image): bump [email protected]: #88238
- Disallow javascript urls in router methods and redirects: #88185
- Fix relative same host redirects in node middleware: #88253
- Remove loadConfig from main development process, pass value from child process: #88230
- Update deploy adapters outputs and handler interfaces for node and edge: #88247
- Move Ready in time before handler initialization: #88235
- next/image: support custom cache handlers: #88248
- feat: add Claude Code plugin marketplace with Cache Components skill: #87993
- refactor: consolidate PPR into cacheComponents architecture: #88243
- Turbopack: include fewer traced files for standalone: #88322
- feat(turbopack): add resolve plugin condition variant of Always and Never: #88190
- perf: use length = 0 to clear the logging array: #88244
- Time logs: Show full millisecond instead of 1 decimal: #88313
- [turbopack] Enable inferring module side effects by default: #87216
- Track search string as part of "refresh state": #87203
- Pass RouteTree into navigation function: #87256
- Read from segment cache unknown routes: #87293
- Pass loading boundary as part of RSC data: #87825
- Revert "refactor: consolidate PPR into cacheComponents architecture ( #88243 )": #88421
- fix: support TypeScript
noUncheckedSideEffectImportsfor CSS imports: #88199 - Don't import typescript at runtime: #88321
- fix: use RDC for server action requests: #88129
- Warn when overriding Cache-Control header on
/_next/routes: #88353 - [prebuilt-skew-protection] feat: adding in automatic deploymentId: #88012
- Revert "[prebuilt-skew-protection] feat: adding in automatic deploymentId": #88449
- Turbopack: Update reqwest, remove experimental system TLS feature: #88290
- Revert "prevent browser cache from using stale RSC responses from pre…: #88457
- Turbopack: retain loader tree order for metadata: #88487
- Turbopack: more dead code: #88505
- fix(build): prevent route handler manifests from inheriting unrelated client components: #88419
- Upgrade React from
65eec428-20251218to3e1abcc8-20260113: #88530 - Better typesafety for
interopDefault: #88486 - keep next-env.d.s unchanged between dev and build: #88428
- Remove sibling caches from CacheNode tree: #87991
- Upgrade React from
3e1abcc8-20260113to4a3d993e-20260114: #88547 - Finish deleting Mutable from router implementation: #88046
- fetch(next/image): reduce maximumResponseBody from 300MB to 50MB: #88588
- [CC] Fix dev validation error from server action bound args: #88600
- Fix incorrect 'Ready in' time for next start: #88589
- feat: server action logging: #88277
- Log browser error and warnings in terminal: #88352
- Upgrade React from
4a3d993e-20260114tobef88f7c-20260116: #88649 - fix: make RedirectType constant properties literal types: #88653
- Turbopack: add support for matching loaders on resource queries: #88644
- fix: capture promisified setImmediate separately: #88346
- fix: setImmediate[util.promisify.custom] access fails in edge runtime: #88685
- Fix
--debug-build-pathsbracket escaping for glob patterns: #88660 - Add negation pattern support to
--debug-build-paths: #88654 - Only filter next config if experimental flag is enabled: #88733
- [Devtool Indicator] Fix cross alignment: #88664
- Turbopack: don't use build id for pages router client-side manifests: #88641
- Allow inspecting server with
next start --inspect: #88744 - Turbopack: Add
--debug-build-pathssupport to filter routes: #88655 - Upgrade React from
bef88f7c-20260116to41b3e9a6-20260119: #88756 - Use rewritten pathname for implicit cache tags: #88732
- Upgrade React from
41b3e9a6-20260119tod2908752-20260119: #88774 - Add experimental_gesturePush to App Router: #88776
- Rename
rewroteURLtorewrittenPathnamein request metadata: #88751 - Simplify
getImplicitTagsto accept pathname instead of url object: #88753 - Add
NEXT_DEPLOYMENT_IDglobal: #86738 - Turbopack: remove deployment id suffix from client reference manifest chunks: #88741
- Inject
<html data-dpl-id>and don't inline it into JS anymore: #88761 - [metadata] match the Metadata and ResolvedMetadata type: #88739
- Reuse bfcache data during Full prefetches: #88606
- Embed static sibling info in route tree: #88692
- Fix
revalidatePathwith params and trailing slash when deployed: #88623 - fix: preserve cache behavior for PPR fallback shells with root params: #88556
- Upgrade React from
d2908752-20260119tob546603b-20260121: #88860 - stabilize browser log forward options: #88857
- [devtools] Wrap long file names of stack frames in the error overlay: #88886
- [devtools] Fix notch coloring of error overlay in forced colors mode: #88892
- Remove
deploymentIdfrom App RouterRenderOptsPartial: #88866 - feat: implement LRU cache with invocation ID scoping for minimal mode response cache: #88509
- [prebuilt-skew-protection] feat: adding in automatic deploymentId: #88496
- [devtool] Add hydration diff indicator for diff lines: #88919
- Revert "[prebuilt-skew-protection] feat: adding in automatic deploymentId": #88942
- [turbopack] add task type infromation to the print_cache_item_size feature: #88925
- Upgrade React from
b546603b-20260121to24d8716e-20260123: #88963 - Turbopack: add
?dpl=to all asset urls returned by Turbopack: #88828 - feat(next-codemod): add agents-md command for AI coding agents: #88961
- Update font data: #88975
- Improve agents-md prompt to force doc retrieval: #88997
- [Reapply] Add
useEffectEventto disallowed React APIs in Server Components: #88985 - Apply fixes for onBuildComplete and route module: #88831
- Rename
renderOpts.nextExporttoisBuildTimePrerendering: #88951 - docs: fix typos in
README.mds: #89022 - refactor: consume global-error from loader tree: #88437
- Fix chunk loading when using
__turbopack_load_by_url__with query: #88899 - [mcp] change the mcp endpoint response to JSON: #88911
- Reapply "[turbopack] Add bundling support for worker_threads" ( #88725 ): #88967
- fix: ensure LRU cache items have minimum size of 1 to prevent unbounded growth: #89040
- Upgrade React from
24d8716e-20260123to8c34556c-20260126: #89066 - Use null-prototype objects in server actions manifests: #89069
- Re-enable types-and-precompiled: #89070
- Apply segment changes to adapters outputs: #89072
- Improve no response route handler error: #89036
- Limit number of server action arguments to 1000: #89068
- [prebuilt-skew-protection] feat: adding in automatic deploymentId: #88958
- Decouple route stale time from segment-level data: #88834
- Decouple route and segment cache lifecycles: #88989
- [ci] Silence
baseline-browser-mappingwarnings: #89175 - [Cache Components] Prevent streaming fetch calls from hanging in dev: #89171
- React types update: #89110
- [nextjs] feat: removing length requirement: #89173
- add GPTBot to matcher for known bots: #89188
- Ensure
.mdlicenses are included in vendored packages: #89201 - Switch development log item format as JSON: #89168
- IsolatedDevBuild flag removal: #89167
- fix: coerce HEAD to GET for internal images: #84180
- Upgrade React from
10680271-20260126to230772f9-20260128: #89250 - Upgrade
tarused to extract SWC binary : #89158 - Sort prerender manifest routes: #89246
- Track vary params for segments without server-side param access: #88998
- Optimistic routing: client-side route prediction: #88965
- Keep pages/404.js to be able to dynamically render it anyway: #89263
- fix: fully static pages should e...
- Mar 18, 2026
- Date parsed from source:Mar 18, 2026
- First seen by Releasebot:Mar 18, 2026
Next.js 16.2: AI Improvements
Next.js releases AI improvements with 16.2, featuring AI-ready create-next-app, browser log forwarding, dev server lock file handling, and experimental Agent DevTools.
AI improvements shipping with Next.js 16.2
- Agent-ready create-next-app: Scaffold AI-ready projects out of the box
- Browser Log Forwarding: Forward browser errors to the terminal for agent-powered debugging
- Dev Server Lock File: Actionable error messages when a second dev server tries to start
- Experimental Agent DevTools: Give AI agents terminal access to React DevTools and Next.js diagnostics
- Mar 18, 2026
- Date parsed from source:Mar 18, 2026
- First seen by Releasebot:Mar 18, 2026
Turbopack: What's New in Next.js 16.2
Next.js releases Turbopack updates in 16.2 with Fast Refresh, WASM Workers, Subresource Integrity, dynamic import tree-shaking, and 200+ fixes.
Turbopack improvements shipping with Next.js 16.2
- Server Fast Refresh: Fine-grained server-side hot reloading
- Web Worker Origin: Increasing support for WASM libraries in Workers
- Subresource Integrity Support: Subresource Integrity for JavaScript files
- Tree Shaking of Dynamic Imports: Unused exports removed from dynamic import()
- Performance Improvements and Bug Fixes: Over 200 changes and bug fixes
- Mar 18, 2026
- Date parsed from source:Mar 18, 2026
- First seen by Releasebot:Mar 18, 2026
Next.js 16.2
Next.js releases 16.2 with faster startup and rendering, a redesigned default error page, Turbopack boosts, and AI enhancements.
Next.js 16.2 is now available
Highlights include:
- Faster Time-to-URL: ~400% faster next dev startup
- Faster Rendering: ~50% faster rendering
- New Default Error Page: Redesigned built-in 500 page
- Turbopack: Faster builds, SRI support, Server Fast Refresh, and 200+ bug fixes
- AI Improvements: AGENTS.md in create-next-app, browser log forwarding, and next-browser (experimental)
Curated by the Releasebot team
Releasebot is an aggregator of official product update announcements from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.
Similar to Next.js with recent updates:
- Claude Code updates339 release notes · Latest Jun 6, 2026
- Claude updates94 release notes · Latest Jun 2, 2026
- Codex updates178 release notes · Latest Jun 4, 2026
- Anthropic updates45 release notes · Latest Jun 3, 2026
- ChatGPT updates174 release notes · Latest Jun 4, 2026
- OpenAI updates96 release notes · Latest Jun 4, 2026