chore(deps): update dependency next to v15 [security]

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
next (source)	^14.2.5 → ^15.5.16

---

Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration

CVE-2025-59471 / GHSA-9g9p-9gw9-jx7f

More information

Details

A DoS vulnerability exists in self-hosted Next.js applications that have remotePatterns configured for the Image Optimizer. The image optimization endpoint (/_next/image) loads external images entirely into memory without enforcing a maximum size limit, allowing an attacker to cause out-of-memory conditions by requesting optimization of arbitrarily large images. This vulnerability requires that remotePatterns is configured to allow image optimization from external domains and that the attacker can serve or control a large image on an allowed domain.

Strongly consider upgrading to 15.5.10 and 16.1.5 to reduce risk and prevent availability issues in Next applications.

Severity

• CVSS Score: 5.9 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

References

• https://github.com/vercel/next.js/security/advisories/GHSA-9g9p-9gw9-jx7f
• https://nvd.nist.gov/vuln/detail/CVE-2025-59471
• https://github.com/vercel/next.js/commit/500ec83743639addceaede95e95913398975156c
• https://github.com/vercel/next.js/commit/e5b834d208fe0edf64aa26b5d76dcf6a176500ec
• https://github.com/vercel/next.js/releases/tag/v15.5.10
• https://github.com/vercel/next.js/releases/tag/v16.1.5
• https://github.com/advisories/GHSA-9g9p-9gw9-jx7f

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components

GHSA-h25m-26qc-wcjf

More information

Details

A vulnerability affects certain React Server Components packages for versions 19.0.x, 19.1.x, and 19.2.x and frameworks that use the affected packages, including Next.js 13.x, 14.x, 15.x, and 16.x using the App Router. The issue is tracked upstream as CVE-2026-23864.

A specially crafted HTTP request can be sent to any App Router Server Function endpoint that, when deserialized, may trigger excessive CPU usage, out-of-memory exceptions, or server crashes. This can result in denial of service in unpatched environments.

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

• https://github.com/facebook/react/security/advisories/GHSA-83fc-fqcc-2hmg
• https://github.com/vercel/next.js/security/advisories/GHSA-h25m-26qc-wcjf
• https://nvd.nist.gov/vuln/detail/CVE-2026-23864
• https://vercel.com/changelog/summary-of-cve-2026-23864
• https://github.com/advisories/GHSA-h25m-26qc-wcjf

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Next.js: HTTP request smuggling in rewrites

CVE-2026-29057 / GHSA-ggv3-7p47-pfv8

More information

Details

Summary

When Next.js rewrites proxy traffic to an external backend, a crafted DELETE/OPTIONS request using Transfer-Encoding: chunked could trigger request boundary disagreement between the proxy and backend. This could allow request smuggling through rewritten routes.

Impact

An attacker could smuggle a second request to unintended backend routes (for example, internal/admin endpoints), bypassing assumptions that only the configured rewrite destination/path is reachable. This does not impact applications hosted on providers that handle rewrites at the CDN level, such as Vercel.

Patches

The vulnerability originated in an upstream library vendored by Next.js. It is fixed by updating that dependency’s behavior so content-length: 0 is added only when both content-length and transfer-encoding are absent, and transfer-encoding is no longer removed in that code path.

Workarounds

If upgrade is not immediately possible:

• Block chunked DELETE/OPTIONS requests on rewritten routes at your edge/proxy.
• Enforce authentication/authorization on backend routes per our security guidance.

Severity

• CVSS Score: 6.3 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

References

• https://github.com/vercel/next.js/security/advisories/GHSA-ggv3-7p47-pfv8
• https://github.com/vercel/next.js/commit/dc98c04f376c6a1df76ec3e0a2d07edf4abdabd6
• https://github.com/vercel/next.js/releases/tag/v15.5.13
• https://github.com/vercel/next.js/releases/tag/v16.1.7
• https://nvd.nist.gov/vuln/detail/CVE-2026-29057
• https://github.com/advisories/GHSA-ggv3-7p47-pfv8

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Next.js: Unbounded next/image disk cache growth can exhaust storage

CVE-2026-27980 / GHSA-3x4c-7xq6-9pq8

More information

Details

Summary

The default Next.js image optimization disk cache (/_next/image) did not have a configurable upper bound, allowing unbounded cache growth.

Impact

An attacker could generate many unique image-optimization variants and exhaust disk space, causing denial of service. Note that this does not impact platforms that have their own image optimization capabilities, such as Vercel.

Patches

Fixed by adding an LRU-backed disk cache with images.maximumDiskCacheSize, including eviction of least-recently-used entries when the limit is exceeded. Setting maximumDiskCacheSize: 0 disables disk caching.

Workarounds

If upgrade is not immediately possible:

• Periodically clean .next/cache/images.
• Reduce variant cardinality (e.g., tighten values for images.localPatterns, images.remotePatterns, and images.qualities)

Severity

• CVSS Score: 6.9 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

• https://github.com/vercel/next.js/security/advisories/GHSA-3x4c-7xq6-9pq8
• https://github.com/vercel/next.js/commit/39eb8e0ac498b48855a0430fbf4c22276a73b4bd
• https://github.com/vercel/next.js/releases/tag/v16.1.7
• https://nvd.nist.gov/vuln/detail/CVE-2026-27980
• https://github.com/advisories/GHSA-3x4c-7xq6-9pq8

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Next.js has a Denial of Service with Server Components

GHSA-q4gf-8mx6-v5v3

More information

Details

A vulnerability affects certain React Server Components packages for versions 19.x and frameworks that use the affected packages, including Next.js 13.x, 14.x, 15.x, and 16.x using the App Router. The issue is tracked upstream as CVE-2026-23869. You can read more about this advisory our this changelog.

A specially crafted HTTP request can be sent to any App Router Server Function endpoint that, when deserialized, may trigger excessive CPU usage. This can result in denial of service in unpatched environments.

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

• https://github.com/vercel/next.js/security/advisories/GHSA-q4gf-8mx6-v5v3
• https://vercel.com/changelog/summary-of-cve-2026-23869
• https://github.com/advisories/GHSA-q4gf-8mx6-v5v3

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Next.js vulnerable to cache poisoning in React Server Component responses

CVE-2026-44576 / GHSA-wfc6-r584-vfw7

More information

Details

Impact

Applications using React Server Components can be vulnerable to cache poisoning when shared caches do not correctly partition response variants. Under affected conditions, an attacker can cause an RSC response to be served from the original URL and poison shared cache entries so later visitors receive component payloads instead of the expected HTML.

Fix

We now validate and interpret RSC request headers consistently across request classification and rendering, and we enforce the intended cache-busting behavior so RSC payloads are not unexpectedly served from the original URL.

Workarounds

If you cannot upgrade immediately, ensure your CDN or reverse proxy keys on the relevant RSC request headers and honors Vary, or disable shared caching for affected App Router and RSC responses.

Severity

• CVSS Score: 5.4 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L

References

• https://github.com/vercel/next.js/security/advisories/GHSA-wfc6-r584-vfw7
• https://github.com/vercel/next.js/releases/tag/v15.5.16
• https://github.com/vercel/next.js/releases/tag/v16.2.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-44576
• https://github.com/advisories/GHSA-wfc6-r584-vfw7

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades

CVE-2026-44578 / GHSA-c4j6-fc7j-m34r

More information

Details

Impact

Self-hosted applications using the built-in Node.js server can be vulnerable to server-side request forgery through crafted WebSocket upgrade requests. An attacker can cause the server to proxy requests to arbitrary internal or external destinations, which may expose internal services or cloud metadata endpoints. Vercel-hosted deployments are not affected.

Fix

We now apply the same safety checks to WebSocket upgrade handling that already existed for normal HTTP requests, so upgrade requests are only proxied when routing has explicitly marked them as safe external rewrites.

Workarounds

If you cannot upgrade immediately, do not expose the origin server directly to untrusted networks. If WebSocket upgrades are not required, block them at your reverse proxy or load balancer, and restrict origin egress to internal networks and metadata services where possible.

Severity

• CVSS Score: 8.6 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

References

• https://github.com/vercel/next.js/security/advisories/GHSA-c4j6-fc7j-m34r
• https://github.com/vercel/next.js/releases/tag/v15.5.16
• https://github.com/vercel/next.js/releases/tag/v16.2.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-44578
• https://github.com/advisories/GHSA-c4j6-fc7j-m34r

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Next.js vulnerable to cache poisoning via collisions in React Server Component cache-busting

CVE-2026-44582 / GHSA-vfv6-92ff-j949

More information

Details

Impact

React Server Component responses can be vulnerable to cache poisoning in deployments that rely on shared caches with insufficient response partitioning. In affected conditions, collisions in the _rsc cache-busting value can allow an attacker to poison cache entries so users receive the wrong response variant for a given URL.

Fix

We strengthened the _rsc cache-busting mechanism to make practical collisions significantly harder and to better separate response variants that should not share cache entries.

Workarounds

If you cannot upgrade immediately, ensure intermediary caches correctly honor Vary for RSC-related request headers, or disable shared caching for affected RSC responses until you can deploy a patched release.

Severity

• CVSS Score: 3.7 / 10 (Low)
• Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

References

• https://github.com/vercel/next.js/security/advisories/GHSA-vfv6-92ff-j949
• https://github.com/vercel/next.js/releases/tag/v15.5.16
• https://github.com/vercel/next.js/releases/tag/v16.2.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-44582
• https://github.com/advisories/GHSA-vfv6-92ff-j949

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Next.js vulnerable to cross-site scripting in App Router applications using CSP nonces

CVE-2026-44581 / GHSA-ffhc-5mcf-pf4q

More information

Details

Impact

App Router applications that rely on CSP nonces can be vulnerable to stored cross-site scripting when deployed behind shared caches. In affected versions, malformed nonce values derived from request headers could be reflected into rendered HTML in an unsafe way, allowing an attacker to poison cached responses and cause script execution for later visitors.

Fix

We now reject or ignore malformed nonce values before they are embedded into HTML and apply stricter nonce sanitization so request-derived nonce data cannot break out of the intended attribute context.

Workarounds

If you cannot upgrade immediately, strip inbound Content-Security-Policy request headers from untrusted traffic.

Severity

• CVSS Score: 4.7 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N

References

• https://github.com/vercel/next.js/security/advisories/GHSA-ffhc-5mcf-pf4q
• https://github.com/vercel/next.js/releases/tag/v15.5.16
• https://github.com/vercel/next.js/releases/tag/v16.2.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-44581
• https://github.com/advisories/GHSA-ffhc-5mcf-pf4q

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Next.js Vulnerable to Denial of Service with Server Components

GHSA-8h8q-6873-q5fj

More information

Details

A vulnerability affects certain React Server Components packages for versions 19.x and frameworks that use the affected packages, including Next.js 13.x, 14.x, 15.x, and 16.x using the App Router. The issue is tracked upstream as CVE-2026-23870.

A specially crafted HTTP request can be sent to any App Router Server Function endpoint that, when deserialized, may trigger excessive CPU usage. This can result in denial of service in unpatched environments.

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

• https://github.com/facebook/react/security/advisories/GHSA-rv78-f8rc-xrxh
• https://github.com/vercel/next.js/security/advisories/GHSA-8h8q-6873-q5fj
• https://github.com/vitejs/vite-plugin-react/security/advisories/GHSA-w94c-4vhp-22gx
• https://nvd.nist.gov/vuln/detail/CVE-2026-23870
• https://github.com/advisories/GHSA-8h8q-6873-q5fj

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Next.js has cross-site scripting in beforeInteractive scripts with untrusted input

CVE-2026-44580 / GHSA-gx5p-jg67-6x7h

More information

Details

Impact

Applications that use beforeInteractive scripts together with untrusted content can be vulnerable to cross-site scripting. In affected versions, serialized script content was not escaped safely before being embedded into the document, which could allow attacker-controlled input to break out of the intended script context and execute arbitrary JavaScript in a visitor's browser.

Fix

We now HTML-escape serialized beforeInteractive script content before embedding it into the page, preventing attacker-controlled content from breaking out of the inline script boundary.

Workarounds

If you cannot upgrade immediately, do not pass untrusted data into beforeInteractive scripts. If that pattern is unavoidable, sanitize or escape the content before embedding it.

Severity

• CVSS Score: 6.1 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

References

• https://github.com/vercel/next.js/security/advisories/GHSA-gx5p-jg67-6x7h
• https://github.com/vercel/next.js/releases/tag/v15.5.16
• https://github.com/vercel/next.js/releases/tag/v16.2.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-44580
• https://github.com/advisories/GHSA-gx5p-jg67-6x7h

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n

CVE-2026-44573 / GHSA-36qx-fr4f-26g5

More information

Details

Impact

Applications using the Pages Router with i18n configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less /_next/data/<buildId>/<page>.json requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks.

Fix

The matcher logic was updated to perform the same match as it would on a non-i18n data route.

Workarounds

If you cannot upgrade immediately, enforce authorization in the page's server-side data path instead of relying solely on middleware.

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

• https://github.com/vercel/next.js/security/advisories/GHSA-36qx-fr4f-26g5
• https://github.com/vercel/next.js/releases/tag/v15.5.16
• https://github.com/vercel/next.js/releases/tag/v16.2.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-44573
• https://github.com/advisories/GHSA-36qx-fr4f-26g5

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Next.js's Middleware / Proxy redirects can be cache-poisoned

CVE-2026-44572 / GHSA-3g8h-86w9-wvmq

More information

Details

Impact

Next.js uses the x-nextjs-data request header for internal data requests. On affected versions, an external client could send this header on a normal request to a path handled by middleware that returns a redirect.

When that happened, the middleware/proxy could treat the request as a data request and replace the standard Location redirect header with the internal x-nextjs-redirect header. Browsers do not follow x-nextjs-redirect, so the response became an unusable redirect for normal clients.

If the application was deployed behind a CDN or reverse proxy that caches 3xx responses without varying on this header, a single attacker request could poison the cached redirect response for the affected path. Subsequent visitors could then receive a cached redirect response without a Location header, causing a denial of service for that redirect path until the cache entry expired or was purged.

Affected scenarios

This affects applications that:

• use middleware or proxy redirects
• are deployed behind a caching CDN or reverse proxy
• allow 3xx responses on those paths to be cached without differentiating internal data requests from normal requests

Fix

The fix stops trusting x-nextjs-data by itself for middleware redirect handling. A request is now treated as an internal data request only when it is validated as such by internal routing state, preserving legitimate data-request redirect behavior while preventing external header injection from changing normal redirect responses.

Workarounds

Before upgrading, users can reduce risk by:

• configuring the CDN or reverse proxy to vary its cache key on x-nextjs-data for affected responses

Severity

• CVSS Score: 3.7 / 10 (Low)
• Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

References

• https://github.com/vercel/next.js/security/advisories/GHSA-3g8h-86w9-wvmq
• https://github.com/vercel/next.js/releases/tag/v15.5.16
• https://github.com/vercel/next.js/releases/tag/v16.2.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-44572
• https://github.com/advisories/GHSA-3g8h-86w9-wvmq

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Next.js has a Denial of Service in the Image Optimization API

CVE-2026-44577 / GHSA-h64f-5h5j-jqjh

More information

Details

Impact

When self-hosting Next.js with the default image loader, the Image Optimization API fetches local images entirely into memory without enforcing a maximum size limit. An attacker could cause out-of-memory conditions by requesting large local assets from the /_next/image endpoint that match the images.localPatterns configuration (by default, all patterns are allowed).

• If you are using images.localPatterns, only the patterns in that array are impacted.
• If you are using images.unoptimized: true, you are NOT impacted.
• If you are using images.loader: 'custom', you are NOT impacted.
• If you are using Vercel, you are NOT impacted.

Fix

We now apply response size limits consistently to internal image fetches, not just external ones, and fail oversized responses before they can exhaust process memory.

This can be adjusted using the images.maximumResponseBody configuration.

Workarounds

If you cannot upgrade immediately, avoid routing large local assets through /_next/image, disable image optimization for large or untrusted local files, or block image optimization access to those assets at the edge.

You can disable using the images.localPatterns: [] configuration. This will still allow fetching remote images (which is not impacted).

Severity

• CVSS Score: 5.9 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

References

• https://github.com/vercel/next.js/security/advisories/GHSA-h64f-5h5j-jqjh
• https://github.com/vercel/next.js/releases/tag/v15.5.16
• https://github.com/vercel/next.js/releases/tag/v16.2.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-44577
• https://github.com/advisories/GHSA-h64f-5h5j-jqjh

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

vercel/next.js (next)

v15.5.16

Compare Source

v15.5.15

Compare Source

Please refer the following changelogs for more information about this security release:

https://vercel.com/changelog/summary-of-cve-2026-23869

v15.5.14

Compare Source

v15.5.13

Compare Source

v15.5.12

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

• fix unlock in publish-native

This is a re-release of v15.5.11 applying the turbopack changes.

v15.5.11

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• Tracing: Fix memory leak in span map (#​85529)
• fix: ensure LRU cache items have minimum size of 1 to prevent unbounded growth (#​89134)
• Turbopack: fix NFT tracing of sharp 0.34 (#​82340)
• Turbopack: support pattern into exports field (#​82757)
• NFT tracing fixes (#​84155 and #​85323)
• Turbopack: validate CSS without computing all paths (#​83810)
• feat: implement LRU cache with invocation ID scoping for minimal mode response cache (#​89129)

Credits

Huge thanks to @​timneutkens, @​mischnic, @​ztanner, and @​wyattjoh for helping!

v15.5.10

Compare Source

Please refer the following changelogs for more information about this security release:

• https://vercel.com/changelog/summaries-of-cve-2025-59471-and-cve-2025-59472
• https://vercel.com/changelog/summary-of-cve-2026-23864

v15.5.9

Compare Source

v15.5.8

Compare Source

v15.5.7

Compare Source

v15.5.6

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• Turbopack: don't define process.cwd() in node_modules #​83452

Credits

Huge thanks to @​mischnic for helping!

v15.5.5

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• Split code-frame into separate compiled package (#​84238)
• Add deprecation warning to Runtime config (#​84650)
• fix: unstable_cache should perform blocking revalidation during ISR revalidation (#​84716)
• feat: experimental.middlewareClientMaxBodySize body cloning limit (#​84722)
• fix: missing next/link types with typedRoutes (#​84779)

Misc Changes

• docs: early October improvements and fixes (#​84334)

Credits

Huge thanks to @​devjiwonchoi, @​ztanner, and @​icyJoseph for helping!

v15.5.4

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• fix: ensure onRequestError is invoked when otel enabled (#​83343)
• fix: devtools initial position should be from next config (#​83571)
• [devtool] fix overlay styles are missing (#​83721)
• Turbopack: don't match dynamic pattern for node_modules packages (#​83176)
• Turbopack: don't treat metadata routes as RSC (#​82911)
• [turbopack] Improve handling of symlink resolution errors in track_glob and read_glob (#​83357)
• Turbopack: throw large static metadata error earlier (#​82939)
• fix: error overlay not closing when backdrop clicked (#​83981)
• Turbopack: flush Node.js worker IPC on error (#​84077)

Misc Changes

• [CNA] use linter preference (#​83194)
• CI: use KV for test timing data (#​83745)
• docs: september improvements and fixes (#​83997)

Credits

Huge thanks to @​yiminghe, @​huozhi, @​devjiwonchoi, @​mischnic, @​lukesandberg, @​ztanner, @​icyJoseph, @​leerob, @​fufuShih, @​dwrth, @​aymericzip, @​obendev, @​molebox, @​OoMNoO, @​pontasan, @​styfle, @​HondaYt, @​ryuapp, @​lpalmes, and @​ijjk for helping!

v15.5.3

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• fix: validation return types of pages API routes (#​83069)
• fix: relative paths in dev in validator.ts (#​83073)
• fix: remove satisfies keyword from type validation to preserve old TS compatibility (#​83071)

Credits

Huge thanks to @​bgub for helping!

v15.5.2

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• fix: disable unknownatrules lint rule entirely (#​83059)
• revert: add ?dpl to fonts in /_next/static/media (#​83062)

Credits

Huge thanks to @​bgub and @​ztanner for helping!

v15.5.1

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• fix: aliased navigations should apply scroll handling (#​82900)
• Turbopack: fix invalid NFT entry with file behind symlink (#​82887)
• fix: typesafe linking to route handlers and pages API routes (#​82858)
• fix: change "noUnknownAtRules" to "warn" for Biome (#​82974)
• fix: add path normalization to getRelativePath for Windows (#​82918)
• feat: add typesafety with config.typedRoutes to redirect() and permanentRedirect() (#​82860)
• fix: avoid importing types that will be unused (#​82856)
• fix: update the config.api.responseLimit type (#​82852)
• fix: update validation return types (#​82854)

Credits

Huge thanks to @​bgub, @​mischnic, and @​ztanner for helping!

v15.5.0

Compare Source

Core Changes

• Use and enforce exhaustive switch statements for work unit store: #​81577
• Enable @typescript-eslint/switch-exhaustiveness-check rule: #​81583
• [dynamicIO] use RSC dynamicness to control partial vs complete PPR result: #​81627
• [dynamicIO] Do not use React.unstable_postpone(): #​81652
• feat: new detachable panel UI: #​81483
• Turbopack: content-hash PageLoaderAsset: #​81450
• [segment explorer] fix content overflow styling: #​81649
• Improve reliability of owner stacks for async I/O errors: #​81501
• fix(router): Prevent redirect loop on root data requests with basePath: #​81096
• Ensure custom NextServer config is honored: #​81681
• Fix before interactive incorrectly render css: #​81146
• perf: memorize exclude function in webpack config: #​81525
• Also enforce experimental features when there's no next config file: #​81679
• feat(next/image): warn when images.qualities is undefined: #​81690
• feat(build): optimize filterUniqueParamsCombinations to generate sub-combinations: #​81321
• Update NextAdapter type and re-export: #​81692
• upgrade to path-to-regexp@​6.3.0: #​80123
• [metadata] replace for initial body icon case: #​81688
• [segment explorer] remove dev panel ui flag: #​81670
• Simplify running test apps locally with ppr or dynamicIO enabled: #​81668
• [turbopack] Return cached Promise from __turbopack_load_by_url__ : #​81663
• Upgrade React from 97cdd5d3-20250710 to 2f0e7e57-20250715: #​81678
• Delete unused renderToString function: #​81707
• Discard prerendered route handler data from FS cache after revalidation: #​81611
• Upgrade React from 2f0e7e57-20250715 to d85ec5f5-20250716: #​81708
• Ignore pending revalidations during prerendering: #​81621
• [turbopack] Clear chunk cache on HMR instead of creating new next-server VM: #​81664
• fix: rootParams should throw in client when fallbackParams are not present: #​81711
• perf(build): optimize buildAppStaticPaths performance and add helper function: #​81386
• Turbopack: Support string without options for @​next/mdx: #​81713
• [Segment Cache] Support dynamic head prefetching: #​81677
• [sourcemaps] Consistent cursor columns: #​81375
• fix: revert client segment route changes for sub shell generation: #​81731
• fix: pages router metadata bugs with React 19: #​81733
• Improve error handling for headers/cookies/draftMode in 'use cache': #​81716
• [devtool] fix duplicate rendered indicator on server: #​81729
• [devtool] enable segment explorer by default: #​81737
• [turbopack] Stop exposing globals from Turbopack runtime: #​81727
• Remove unnecessary await: #​81761
• [chore] bump zod to latest v3: #​81757
• feat(turbopack): Log anonymized internal error (panic) information to telemetry: #​81272
• fix: revert client segment route changes for sub shell generation: #​81740
• bugfix: static resources staleTime should be renewed once refetched: #​81771
• [devtool] move font styling to global.css: #​81782
• [devtool] copy decoded info of error details: #​81735
• fix(build): add sourcePage context for PPR dynamic route lambda creation: #​81781
• refactor: rename experimental.dynamicIO to experimental.cacheComponents: #​81562
• Properly handle hanging promise rejections during prerendering: #​81754
• Upgrade React from d85ec5f5-20250716 to dffacc7b-20250717: #​81767
• Refactor: Get rid of overly generic getExpectedRequestStore function: #​81791
• [devtool] migrate css reset to global.css: #​81783
• [dev-tools] Robust shortcut detection: #​81756
• [segment explorer] hide for pages router: #​81813
• [devtool] fix scrollbar styling: #​81814
• fix(ppr): ensure fallback route params trigger dynamic resume: #​81812
• [devtools] restart server pending state: #​80858
• Turbopack: fix dist dir on Windows: #​81758
• fix: remove boundary sentinel from RSC responses: #​81857
• [sourcemaps] Try VM for retrieving source maps first: #​81869
• [devtools] save user config inside .next/cache: #​81807
• Server: Remove unused code: #​81886
• refactor: encapsulate content type within RenderResult: #​81861
• refactor: handle null RenderResult responses gracefully: #​81895
• Upgrade React from dffacc7b-20250717 to e9638c33-20250721: #​81899
• chore(devtools): sync todos to linear: #​81901
• Introduce 'use cache: private': #​81816
• chore(deps): update browserslist: #​81851
• Remove web-server from edge-ssr-app: #​81389
• Stabilize node middleware support: #​81907
• Add run-turbopack-compiler trace span: #​81917
• fix: support calling onClose multiple times in edge-ssr-app: #​81911
• fix: logging the correct process for listened port: #​81903
• Build: Include rewrites in manifest generation: #​81894
• Routing: Clean up some code: #​81932
• [sourcemaps] Ensure codeframe when calling Client Functions from Server: #​81918
• [segment explorer] missing file suggestion: #​81617
• [turbopack] Always print trace labels in headers: #​81728
• Revert "[metadata] use https protocol for schema urls": #​81934
• Upgrade React from e9638c33-20250721 to 7513996f-20250722: #​81940
• Upgrade to swc v33: #​81750
• Remove extra base-server code: #​81944
• Turbopack: flatten sourceInfo to avoid objects, reorder args, compress node.js entry: #​81545
• Fix dynamicParams false layout case in dev: #​81990
• Initial MCP implementation: #​81770
• Fix: Unresolved param in x-nextjs-rewritten-query: #​81991
• Turbopack: Add an option to use system TLS certificates (fixes #​79060, fixes #​79059): #​81818
• Turbopack: Remove unused proxy option in turbo-tasks-fetch, lightly document HTTP_PROXY/HTTPS_PROXY environment variables: #​81905
• Upgrade React from 7513996f-20250722 to edac0dde-20250723: #​81984
• [devtools] Cleanup folder structure: #​82012
• [devtools] Fix "open in editor" for locations in stackframes: #​82013
• [Segment Cache] Fix: Key by rewritten search: #​81986
• Upgrade vercel og and remove yoga type patching: #​81937
• [perf] cache load config results: #​80570
• Turbopack: use prototype for turbopack context for better runtime performance: #​81547
• [reactcompiler] Test with latest RC: #​82002
• [devtools] Fix various exhaustive-deps violations: #​82010
• [devtools] Apply React Compiler to Next.js DevTools source: #​82004
• Upgrade React from edac0dde-20250723 to 3d14fcf0-20250724: #​82020
• Adjusted the warning message to be more descriptive: #​82054
• Track fallback params on workUnitStore: #​82003
• Fix API stripping JSON incorrectly: #​82061
• Upgrade React from 3d14fcf0-20250724 to 19baee81-20250725: #​82063
• use FetchStrategy to control prefetching behavior everywhere: #​82032
• [Segment Cache] set fetchStrategy on segments from a dynamic request: #​82059
• Revert "Upgrade vercel og and remove yoga type patching (#​81937)": #​82066
• Optimize segme

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4342ab5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR