FRONTEND
Next.js v16.2.7
RESUMEN
> [!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 - [backport] Patch `playwright-core` to resolve `_finishedPromise` on `requestFailed` - [backport] F
Descripción Detallada
> [!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 - [backport] Patch `playwright-core` to resolve `_finishedPromise` on `requestFailed` - [backport] Fix dev mode hydration failure when page is served from HTTP cache - [backport] Fix catch-all `router.query` corruption with `basePath` + `rewrites` - [backport] Encode non-ASCII characters in cache tags at construction - [backport] Fix server action forwarding loop with middleware rewrites - [backport] Turbopack: switch from base40 to base38 hash encoding - [ci] Disable hanging node 24 typescript tests on 16.2 backport branch - [backport] Fix "type: module" in project dir when using standalone or adapters - [backport] Propagate adapter preferred regions - [16.2.x] Don't drop `FormData` entries - [backport] feat(turbopack): add LocalPathOrProjectPath PostCSS config resolution Credits Huge thanks to @eps1lon, @icyJoseph, @unstubbable, @mischnic, @bgw, @timneutkens, and @lukesandberg for helping!
Explicación con IA
Genera un resumen en lenguaje claro de los cambios de este release.
Releases Relacionados
FRONTEND
Next.js v16.2.9
Empty release to ensure `next@latest` points at a stable release. Next.js only allows publishing with Trusted Publishing enabled. In order to fix NPM dist-tags, we have to release a new version. Updating dist-tags is not possible with Trusted Publishing.
FRONTEND
Next.js v16.2.8
Release with no changes in an attempt to fix `next@latest` pointing at a prerelease version.
FRONTEND