fix(deps): update dependency next to v15 [security] - autoclosed

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
next (source)	13.5.3 → 15.5.15

GitHub Vulnerability Alerts

CVE-2024-34351

Impact

A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions by security researchers at Assetnote. If the Host header is modified, and the below conditions are also met, an attacker may be able to make requests that appear to be originating from the Next.js application server itself.

Prerequisites

• Next.js (<14.1.1) is running in a self-hosted* manner.
• The Next.js application makes use of Server Actions.
• The Server Action performs a redirect to a relative path which starts with a /.

* Many hosting providers (including Vercel) route requests based on the Host header, so we do not believe that this vulnerability affects any Next.js applications where routing is done in this manner.

Patches

This vulnerability was patched in #​62561 and fixed in Next.js 14.1.1.

Workarounds

There are no official workarounds for this vulnerability. We recommend upgrading to Next.js 14.1.1.

Credit

Vercel and the Next.js team thank Assetnote for responsibly disclosing this issue to us, and for working with us to verify the fix. Thanks to:

Adam Kues - Assetnote
Shubham Shah - Assetnote

CVE-2025-48068

Summary

A low-severity vulnerability in Next.js has been fixed in version 15.2.2. This issue may have allowed limited source code exposure when the dev server was running with the App Router enabled. The vulnerability only affects local development environments and requires the user to visit a malicious webpage while npm run dev is active.

Because the mitigation is potentially a breaking change for some development setups, to opt-in to the fix, you must configure allowedDevOrigins in your next config after upgrading to a patched version. Learn more.

Learn more: https://vercel.com/changelog/cve-2025-48068

Credit

Thanks to sapphi-red and Radman Siddiki for responsibly disclosing this issue.

CVE-2025-57752

A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. When images returned from API routes vary based on request headers (such as Cookie or Authorization), these responses could be incorrectly cached and served to unauthorized users due to a cache key confusion bug.

All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled.

More details at Vercel Changelog

CVE-2025-55173

A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. The issue allowed attacker-controlled external image sources to trigger file downloads with arbitrary content and filenames under specific configurations. This behavior could be abused for phishing or malicious file delivery.

All users relying on images.domains or images.remotePatterns are encouraged to upgrade and verify that external image sources are strictly validated.

More details at Vercel Changelog

CVE-2025-57822

A vulnerability in Next.js Middleware has been fixed in v14.2.32 and v15.4.7. The issue occurred when request headers were directly passed into NextResponse.next(). In self-hosted applications, this could allow Server-Side Request Forgery (SSRF) if certain sensitive headers from the incoming request were reflected back into the response.

All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the next() function.

More details at Vercel Changelog

CVE-2025-32421

Summary
We received a responsible disclosure from Allam Rachid (zhero) for a low-severity race-condition vulnerability in Next.js. This issue only affects the Pages Router under certain misconfigurations, causing normal endpoints to serve pageProps data instead of standard HTML.

Learn more here

Credit
Thank you to Allam Rachid (zhero) for the responsible disclosure. This research was rewarded as part of our bug bounty program.

GHSA-mwv6-3258-q52c

A vulnerability affects certain React packages for versions 19.0.0, 19.0.1, 19.1.0, 19.1.1, 19.1.2, 19.2.0, and 19.2.1 and frameworks that use the affected packages, including Next.js 15.x and 16.x using the App Router. The issue is tracked upstream as CVE-2025-55184.

A malicious HTTP request can be crafted and sent to any App Router endpoint that, when deserialized, can cause the server process to hang and consume CPU. This can result in denial of service in unpatched environments.

GHSA-5j59-xgg2-r9c4

It was discovered that the fix for CVE-2025-55184 in React Server Components was incomplete and did not fully mitigate denial-of-service conditions across all payload types. As a result, certain crafted inputs could still trigger excessive resource consumption.

This vulnerability affects React versions 19.0.2, 19.1.3, and 19.2.2, as well as frameworks that bundle or depend on these versions, including Next.js 13.x, 14.x, 15.x, and 16.x when using the App Router. The issue is tracked upstream as CVE-2025-67779.

A malicious actor can send a specially crafted HTTP request to a Server Function endpoint that, when deserialized, causes the React Server Components runtime to enter an infinite loop. This can lead to sustained CPU consumption and cause the affected server process to become unresponsive, resulting in a denial-of-service condition in unpatched environments.

CVE-2025-59471

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.

GHSA-h25m-26qc-wcjf

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.

CVE-2025-29927

Impact

It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.

Patches

• For Next.js 15.x, this issue is fixed in 15.2.3
• For Next.js 14.x, this issue is fixed in 14.2.25
• For Next.js 13.x, this issue is fixed in 13.5.9
• For Next.js 12.x, this issue is fixed in 12.3.5
• For Next.js 11.x, consult the below workaround.

Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability.

Workaround

If patching to a safe version is infeasible, we recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application.

Credits

• Allam Rachid (zhero;)
• Allam Yasser (inzo_)

CVE-2026-29057

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.

CVE-2026-27980

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)

CVE-2024-46982

Impact

By sending a crafted HTTP request, it is possible to poison the cache of a non-dynamic server-side rendered route in the pages router (this does not affect the app router). When this crafted request is sent it could coerce Next.js to cache a route that is meant to not be cached and send a Cache-Control: s-maxage=1, stale-while-revalidate header which some upstream CDNs may cache as well.

To be potentially affected all of the following must apply:

• Next.js between 13.5.1 and 14.2.9
• Using pages router
• Using non-dynamic server-side rendered routes e.g. pages/dashboard.tsx not pages/blog/[slug].tsx

The below configurations are unaffected:

• Deployments using only app router
• Deployments on Vercel are not affected

Patches

This vulnerability was resolved in Next.js v13.5.7, v14.2.10, and later. We recommend upgrading regardless of whether you can reproduce the issue or not.

Workarounds

There are no official or recommended workarounds for this issue, we recommend that users patch to a safe version.

Credits

• Allam Rachid (zhero_)
• Henry Chen

CVE-2024-47831

Impact

The image optimization feature of Next.js contained a vulnerability which allowed for a potential Denial of Service (DoS) condition which could lead to excessive CPU consumption.

Not affected:

• The next.config.js file is configured with images.unoptimized set to true or images.loader set to a non-default value.
• The Next.js application is hosted on Vercel.

Patches

This issue was fully patched in Next.js 14.2.7. We recommend that users upgrade to at least this version.

Workarounds

Ensure that the next.config.js file has either images.unoptimized, images.loader or images.loaderFile assigned.

Credits

Brandon Dahler (brandondahler), AWS
Dimitrios Vlastaras

CVE-2024-51479

Impact

If a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed.

Patches

This issue was patched in Next.js 14.2.15 and later.

If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version.

Workarounds

There are no official workarounds for this vulnerability.

Credits

We'd like to thank tyage (GMO CyberSecurity by IERAE) for responsible disclosure of this issue.

CVE-2024-56332

Impact

A Denial of Service (DoS) attack allows attackers to construct requests that leaves requests to Server Actions hanging until the hosting provider cancels the function execution.

Note: Next.js server is idle during that time and only keeps the connection open. CPU and memory footprint are low during that time.

Deployments without any protection against long running Server Action invocations are especially vulnerable. Hosting providers like Vercel or Netlify set a default maximum duration on function execution to reduce the risk of excessive billing.

This is the same issue as if the incoming HTTP request has an invalid Content-Length header or never closes. If the host has no other mitigations to those then this vulnerability is novel.

This vulnerability affects only Next.js deployments using Server Actions.

Patches

This vulnerability was resolved in Next.js 14.2.21, 15.1.2, and 13.5.8. We recommend that users upgrade to a safe version.

Workarounds

There are no official workarounds for this vulnerability.

Credits

Thanks to the PackDraw team for responsibly disclosing this vulnerability.

GHSA-q4gf-8mx6-v5v3

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.

---

Release Notes

vercel/next.js (next)

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 segment data routes: #​82033
• Turbopack: write tasks doesn't need to be session dependent, as effects will restore: #​78727
• [sourcemaps] Fully sourcemap stacks on the Server: #​81904
• fix(Rspack): use loaderContext.utils.contextify to replace ModuleFilenameHelpers.createFilename: #​82104
• next/root-params: #​80255
• fix(next/image): fix image-optimizer.ts headers: #​82114
• Upgrade React from 19baee81-20250725 to eaee5308-20250728: #​82120
• Fix validateRSCRequestHeaders incorrect redirect: #​82119
• fix(next/image): improve and simplify detect-content-type: #​82118
• [CacheComponents] Use fallback params when validating dynamic routes in dev: #​82069
• Extract getDynamicParam to a shared module: #​82137
• Fix i18n fallback: false collision: #​82136
• [segment explorer] normalize path when running inside monorepo: #​82146
• [segment explorer] windows compatibility: #​82147
• Upgrade React from eaee5308-20250728 to 9be531cd-20250729: #​82159
• Ensure setAssetPrefix updates config instance: #​82160
• Revert "Fix tracing of server actions imported by client components (#​78968): #​82161
• Remove useMDXComponents argument: #​80871
• Fix RSC hash validation for middleware external rewrites: #​82176
• @next/codemod: update docs url in README: #​82135
• @next/codemod: Add experimental.turbo to turbopack codemod for Next.js configs: #​82134
• refactor: lowercase app router header values: #​82169
• Strip internals from NextRequest types: #​82172
• allow root params access in private caches: #​82125
• [devtool] bump base-ui to 1.0.0-beta.2: #​82206
• Upgrade @​vercel og: #​82201
• Upgrade React from 9be531cd-20250729 to 9784cb37-20250730: #​82207
• Fix: the unexpected clearing of symbolic link directories: #​82191
• [next-dev] Set TURBOPACK env before loading config: #​82162
• fix: display multiple lockfile warn if neither outputFileTracingRoot or turbopack.root option is provided: #​82164
• Revert "Initial MCP implementation (#​81770)": #​82217
• Revert "Upgrade @​vercel og (#​82201)": #​82219
• Fix: Don't bail out of prefetch if head is missing: #​82216
• Upgrade React from 9784cb37-20250730 to c260b38d-20250731: #​82247
• [Cache Components] Runtime prefetching: #​81088
• Parse dynamic params on the client: #​82185
• Mark bun builtin modules as external (fixes #​75220): #​77616
• Turbopack: Compact only at the end for short sessions: #​82224
• feat: add fallback root params support for prefetch segment data routes: #​82282
• feat: add route context to prerender error messages: #​82283
• feat: automatically generate route types: #​81396
• [Cache Components] Reset PrerenderStore after generating RSC payload: #​82286
• Include eslint-plugin-react-hooks in React sync: #​82294
• [devtools] Remove unnecessary cascading update: #​82295
• Turbopack: name the module factory function: #​73553
• Update font data: #​82292
• fix: next/root-params erroring when rerendering after action: #​82326
• Remove params from segment path: #​82249
• Upgrade React from c260b38d-20250731 to be11cb5c-20250804: #​82339
• fix: OTel root span should indicate error status on exceptions: #​82212
• [Cache Components] Allow span creation while prerendering: #​82350
• feat(turbopack): improve compile-time define value to support more data types and expr evaluation: #​81042
• [Pages] fix: _error page's req.url can be overwritten to dynamic param on minimal mode: #​82347
• [Pages] fix: use asPath for query-only navigation with useRouter: #​82236
• loader tree: add special segment name to virtual parallel route segments: #​82383
• fix: add ?dpl to fonts in /_next/static/media: #​82384
• Upgrade React from be11cb5c-20250804 to 7deda941-20250804: #​82373
• [devtools] Make state read-only in types: #​82396
• Add experimental clientParamParsing feature flag: #​82393
• add unstable_isUnrecognizedActionError: #​78933
• [Cache Components] give the "seconds" profile a 30s staleTime: #​82332
• Represent "virtual" segments like route groups: #​82422
• [Segment Cache]: fix infinite prefetching when staleTime is 0: #​82388
• Remove param values from static route tree: #​82376
• [Cache Components] Only validate the shell on SSR render: #​82381
• fix: static not-found missing in prerender manifest: #​82199
• Turbopack: Share entrypoint template logic between Turbopack/webpack: #​82385
• Add path to Image documentation: #​82329
• [errors] revamp graceful degrade error boundary: #​82474
• Fix: Do not force BLOCKING_STATIC_RENDER for DOM bots: #​82427
• Update build-complete for adapter API: #​82452
• fix: swc tracing: #​82470
• Upgrade React from 7deda941-20250804 to 3958d5d8-20250807: #​82447
• Delete abandoned segment parsing code: #​82458
• Upgrade React from 3958d5d8-20250807 to f1e70b5e-20250811: #​82534
• Upgrade React from f1e70b5e-20250811 to ac7820a9-20250811: #​82543
• fix(next/image): use image-size pkg as additional format detector: #​82538
• fix: add ?dpl to fonts in /_next/static/media part 2: #​82488
• Fix: Disambiguate Mediapartners-Google user agent: #​82536
• Fix: Allow dynamic rendering when root layout is wrapped in Suspense: #​82378
• wrap devtools stories in context providers: #​82345
• [devtools] Remove unused componentStackFrames field: #​82395
• [Deprecation Warnings]: add amp deprecation warning: #​82551
• fix(next/image): handle empty buffer and experimental flag for skipMetadata: #​82569
• fix: amp deprecation warning should assert on user config: #​82572
• fix: Prevent duplicate file entries in modulesCode: #​82550
• feat: Turbopack typed links: #​81528
• Upgrade React from ac7820a9-20250811 to 1dc3bdea-20250812: #​82575
• [Runtime prefetch] resolve runtime APIs in a separate task: #​82475
• Clean up unused code in restart server button: #​82409
• chore: Update babel types and do some light cleanup of babel loader: #​82486
• [Cache Components] Avoid cache misses when resuming a cached page: #​82578
• chore: Remove unused Map support from next/dynamic transform: #​82487
• [Deprecation Warnings]: add unstable_rootParams deprecation warning: #​82582
• Turbopack: set window.next.turbopack instead: #​82580
• fix router handling when setting a location response header: #​82588
• Fix: Resolve PPR resume mismatch by search params: #​82587
• Upgrade React from 1dc3bdea-20250812 to f1222f76-20250812: #​82595
• [devtools] Move ShadowRoot into context: #​82296
• Remove React 17 logic from Pages Router static generation: #​82604
• [Segment Cache] Optimistic prefetch for search params: #​82586
• Handle badged console calls when dimming console output: #​81889
• run config deprecation checks only on user-provided configuration: #​82613
• [devtools] Remove unused code: #​82299
• [turbopack] Update Turbopack build warning message : #​82591
• [Cache Components] Disallow sync access of cookies & headers at runtime: #​82564
• feat: type guard file generation: #​81400
• fix: find root dir on fs root: #​82590
• fix: use in operator t

---

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 is behind base branch, 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.

[safedep]

SafeDep Report Summary

Package Details

Package	Malware	Vulnerability	Risky License	Report
@emnapi/runtime @ 1.9.2 pnpm-lock.yaml				🔗
@img/colour @ 1.1.0 pnpm-lock.yaml				🔗
@img/sharp-darwin-arm64 @ 0.34.5 pnpm-lock.yaml				🔗
@img/sharp-darwin-x64 @ 0.34.5 pnpm-lock.yaml				🔗
@img/sharp-libvips-darwin-arm64 @ 1.2.4 pnpm-lock.yaml				🔗
@img/sharp-libvips-darwin-x64 @ 1.2.4 pnpm-lock.yaml				🔗
@img/sharp-libvips-linux-arm @ 1.2.4 pnpm-lock.yaml				🔗
@img/sharp-libvips-linux-arm64 @ 1.2.4 pnpm-lock.yaml				🔗
@img/sharp-libvips-linux-ppc64 @ 1.2.4 pnpm-lock.yaml				🔗
@img/sharp-libvips-linux-riscv64 @ 1.2.4 pnpm-lock.yaml				🔗
@img/sharp-libvips-linux-s390x @ 1.2.4 pnpm-lock.yaml				🔗
@img/sharp-libvips-linux-x64 @ 1.2.4 pnpm-lock.yaml				🔗
@img/sharp-libvips-linuxmusl-arm64 @ 1.2.4 pnpm-lock.yaml				🔗
@img/sharp-libvips-linuxmusl-x64 @ 1.2.4 pnpm-lock.yaml				🔗
@img/sharp-linux-arm @ 0.34.5 pnpm-lock.yaml				🔗
@img/sharp-linux-arm64 @ 0.34.5 pnpm-lock.yaml				🔗
@img/sharp-linux-ppc64 @ 0.34.5 pnpm-lock.yaml				🔗
@img/sharp-linux-riscv64 @ 0.34.5 pnpm-lock.yaml				🔗
@img/sharp-linux-s390x @ 0.34.5 pnpm-lock.yaml				🔗
@img/sharp-linux-x64 @ 0.34.5 pnpm-lock.yaml				🔗
@img/sharp-linuxmusl-arm64 @ 0.34.5 pnpm-lock.yaml				🔗
@img/sharp-linuxmusl-x64 @ 0.34.5 pnpm-lock.yaml				🔗
@img/sharp-wasm32 @ 0.34.5 pnpm-lock.yaml				🔗
@img/sharp-win32-arm64 @ 0.34.5 pnpm-lock.yaml				🔗
@img/sharp-win32-ia32 @ 0.34.5 pnpm-lock.yaml				🔗
@img/sharp-win32-x64 @ 0.34.5 pnpm-lock.yaml				🔗
@next/env @ 15.5.15 pnpm-lock.yaml				🔗
@next/swc-darwin-arm64 @ 15.5.15 pnpm-lock.yaml				🔗
@next/swc-darwin-x64 @ 15.5.15 pnpm-lock.yaml				🔗
@next/swc-linux-arm64-gnu @ 15.5.15 pnpm-lock.yaml				🔗
@next/swc-linux-arm64-musl @ 15.5.15 pnpm-lock.yaml				🔗
@next/swc-linux-x64-gnu @ 15.5.15 pnpm-lock.yaml				🔗
@next/swc-linux-x64-musl @ 15.5.15 pnpm-lock.yaml				🔗
@next/swc-win32-arm64-msvc @ 15.5.15 pnpm-lock.yaml				🔗
@next/swc-win32-x64-msvc @ 15.5.15 pnpm-lock.yaml				🔗
@swc/helpers @ 0.5.15 pnpm-lock.yaml				🔗
next @ 15.5.15 pnpm-lock.yaml				🔗
sharp @ 0.34.5 pnpm-lock.yaml				🔗
styled-jsx @ 5.1.6 pnpm-lock.yaml				🔗

View complete scan results →

_{This report is generated by SafeDep Github App}

[github-actions]

📦 Next.js Bundle Analysis for mx-kami

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page	Size (compressed)
global	222.3 KB (🟡 +1.94 KB)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Twenty Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load	% of Budget (350 KB)
/[locale]	42.62 KB	264.92 KB	75.69% (🟢 -0.06%)
/[locale]/[page]	50.74 KB	273.04 KB	78.01% (🟢 -0.08%)
/[locale]/categories/[slug]	4.19 KB	226.49 KB	64.71% (🟢 -0.01%)
/[locale]/favorite/bangumi	7.96 KB	230.26 KB	65.79% (🟢 -0.01%)
/[locale]/favorite/music	5.46 KB	227.76 KB	65.07% (+/- <0.01%)
/[locale]/friends	55.54 KB	277.84 KB	79.38% (🟢 -0.07%)
/[locale]/login	5.39 KB	227.69 KB	65.05% (+/- <0.01%)
/[locale]/notes	403 B	222.69 KB	63.63% (+/- <0.01%)
/[locale]/notes/[id]	73.5 KB	295.8 KB	84.52% (🟢 -0.15%)
/[locale]/notes/topics	2.13 KB	224.42 KB	64.12% (🟢 -0.01%)
/[locale]/notes/topics/[topicSlug]	11.95 KB	234.25 KB	66.93% (🟡 +0.01%)
/[locale]/posts	23.57 KB	245.87 KB	70.25% (🟢 -0.07%)
/[locale]/posts/[category]/[slug]	77.9 KB	300.2 KB	85.77% (🟢 -0.16%)
/[locale]/preview	54.67 KB	276.97 KB	79.14% (🟢 -0.07%)
/[locale]/projects	13.96 KB	236.26 KB	67.50% (🟢 -0.01%)
/[locale]/projects/[id]	49.9 KB	272.2 KB	77.77% (🟢 -0.08%)
/[locale]/recently	95.03 KB	317.33 KB	90.66% (🟢 -0.14%)
/[locale]/says	16.79 KB	239.09 KB	68.31% (🟢 -0.02%)
/[locale]/timeline	12.88 KB	235.18 KB	67.19% (🟢 -0.08%)
/_error	5.99 KB	228.29 KB	65.23% (🟢 -0.02%)

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.