Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 4, 2025

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
next (source) 15.0.316.0.0 age confidence

GitHub Vulnerability Alerts

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.

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

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

GHSA-9qr9-h5gf-34mp

A vulnerability affects certain React packages1 for versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 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-55182.

Fixed in:
React: 19.0.1, 19.1.2, 19.2.1
Next.js: 15.0.5, 15.1.9, 15.2.6, 15.3.6, 15.4.8, 15.5.7, 16.0.7, 15.6.0-canary.58, 16.1.0-canary.12+

The vulnerability also affects experimental canary releases starting with 14.3.0-canary.77. Users on any of the 14.3 canary builds should either downgrade to a 14.x stable release or 14.3.0-canary.76.

All users of stable 15.x or 16.x Next.js versions should upgrade to a patched, stable version immediately.

1 The affected React packages are:

  • react-server-dom-parcel
  • react-server-dom-turbopack
  • react-server-dom-webpack

GHSA-w37m-7fhw-fmv9

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

A malicious HTTP request can be crafted and sent to any App Router endpoint that can return the compiled source code of Server Functions. This could reveal business logic, but would not expose secrets unless they were hardcoded directly into Server Function code.

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.

CVE-2025-59472

A denial of service vulnerability exists in Next.js versions with Partial Prerendering (PPR) enabled when running in minimal mode. The PPR resume endpoint accepts unauthenticated POST requests with the Next-Resume: 1 header and processes attacker-controlled postponed state data. Two closely related vulnerabilities allow an attacker to crash the server process through memory exhaustion:

  1. Unbounded request body buffering: The server buffers the entire POST request body into memory using Buffer.concat() without enforcing any size limit, allowing arbitrarily large payloads to exhaust available memory.

  2. Unbounded decompression (zipbomb): The resume data cache is decompressed using inflateSync() without limiting the decompressed output size. A small compressed payload can expand to hundreds of megabytes or gigabytes, causing memory exhaustion.

Both attack vectors result in a fatal V8 out-of-memory error (FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory) causing the Node.js process to terminate. The zipbomb variant is particularly dangerous as it can bypass reverse proxy request size limits while still causing large memory allocation on the server.

To be affected, an application must run with experimental.ppr: true or cacheComponents: true configured along with the NEXT_PRIVATE_MINIMAL_MODE=1 environment variable.

Strongly consider upgrading to 15.6.0-canary.61 or 16.1.5 to reduce risk and prevent availability issues in Next applications.


Release Notes

vercel/next.js (next)

v16.0.0

Compare Source

v15.5.11

Compare Source

v15.5.10

Compare Source

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 to check dev indicator option when its obj: #​82629
  • Upgrade React from f1222f76-20250812 to 379a083b-20250813: #​82642
  • feat(next/image): warn when images.localPatterns is undefined and src has query: #​82627
  • Turbopack: add turbo_tasks::spawn: #​82634
  • Fix fetch logging after revalidation via server action: #​82643
  • Fix request type in typed route validator: #​82644
  • fix: use .js extension for relative imports: #​82669
  • feat: add RouteContext type for app router route handlers: #​82670
  • Add additional handling for build-complete: #​82671
  • fix: Combine the hrtime tuple to get a better seconds representation: #​82687
  • test: migrate manifest tests to snapshot testing with normalizeManifest utility: #​82675
  • perf(router): replace LRU cache with optimized doubly-linked list implementation: #​82633
  • Turbopack: use a source content regexp for the react compiler: #​82631
  • Upgrade React from 379a083b-20250813 to a96a0f39-20250815: #​82691
  • fix: memory leak from cloneResponse: #​82678
  • Turbopack: Fix logic in HMR logging code that could emit a NaN build time: #​82389
  • fix: use turbopack.root value for outputFileTracingRoot to have consistent tracing root: #​82653
  • fix: return plain text 404 for invalid static asset paths: #​75111
  • Turbopack: show timing event for database compaction: #​82369
  • chore(test): update sharp api test: #​82740
  • [type] dynamic skip generating unused types: #​82755
Example Changes
  • Add Prisma ORM example to Next.js examples: #​75290
  • chore: Update with-supabase example to use getClaims(): #​81383
  • docs: Improve Content Security Policy documentation: #​80580
Misc Changes
  • Update Rspack development test manifest: #​81603
  • Allow beforePageLoad to be async: #​81650
  • Docs: POC: #​81419
  • chore(bot): update comment: #​81672
  • Fix build-native.ts on Windows: #​81673
  • Update Rspack development test manifest: #​81660
  • Update Rspack production test manifest: #​81661
  • Add create release branch workflow: #​81687
  • fix patch-next by adding missing script: #​81430
  • Turbopack: Generalize ImportedBinding effect creation to avoid as much special-casing of SimpleAssignTarget: #​81653
  • docs: Update redirects i18n documentation for App Router: #​81347
  • Include use-cache test suite in the Cache Components tests: #​81610
  • Improve error message for sync server functions: #​81705
  • [lint] keep lint-stage use faster linting: #​81710
  • [test] Fix app-static deploy test: #​81712
  • Fix: createRouterAct "reject" config: #​81720
  • Update Rspack development test manifest: #​81702
  • Update Rspack production test manifest: #​81701
  • Add an e2e test for the css serving issue: #​81683
  • chore: update username from 'nebrelbug' to 'bgub': #​81734
  • Turbopack: consistently name runtime chunk: #​81769
  • Turbopack: include more details in panic: #​81773
  • fix(turbopack) Adjust the way catchall routes are handled when a more specific parallel route exists: #​81634
  • Add trigger for v0 sync workflow: #​81645
  • Update Rspack production test manifest: #​81746
  • Update Rspack development test manifest: #​81747
  • Turbopack: Split DynamicEqHash trait into smaller traits in a separate re-usable crate: #​81741
  • [turbopack] Reuse shared Promise for loaded chunks: #​81755
  • Add VSCode tasks to show TypeScript compilation errors in problems view: #​81799
  • Turbopack: remove unneeded manifests for API routes: #​81536
  • [turbopack] use require to load chunks in our node runtime: #​81738
  • Turbopack: fix unhelpful error message when deleting folder fails: #​81718
  • Remove experimental.strictNextHead: #​81882
  • Remove some random commas: #​81875
  • Turbopack: Add cache for reqwest clients: #​81742
  • Update Rspack development test manifest: #​81878
  • Update Rspack production test manifest: #​81879
  • Turbopack: Track variable usage inside of visit_assign_target_pat: #​81654
  • Turbopack: Replace current_value set/restore mutation pattern with a safer with_pat_value helper: #​81696
  • Docs: Document global-not-found: #​81803
  • [router-act] Fixes related to segment inlining: #​81896
  • [test] Add dedicated test for error when client functions are called from server components: #​81930
  • Fix an issue in how css references are collected under next build --turbopack: #​81704
  • Turbopack: Update notify-rs crate, remove workaround for fixed bug: #​81909
  • Update Rspack development test manifest: [#​81913](htt

Configuration

📅 Schedule: Branch creation - "" (UTC), 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.

@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 9446945 to 58236c1 Compare March 21, 2025 16:13
@renovate renovate bot changed the title fix(deps): update dependency next to v15.1.2 [security] fix(deps): update dependency next to v15.2.3 [security] Mar 21, 2025
@renovate renovate bot changed the title fix(deps): update dependency next to v15.2.3 [security] fix(deps): update dependency next to v15.2.3 [security] - autoclosed May 22, 2025
@renovate renovate bot closed this May 22, 2025
@renovate renovate bot deleted the renovate/npm-next-vulnerability branch May 22, 2025 22:46
@renovate renovate bot changed the title fix(deps): update dependency next to v15.2.3 [security] - autoclosed fix(deps): update dependency next to v15.2.3 [security] May 24, 2025
@renovate renovate bot reopened this May 24, 2025
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from d95765e to 58236c1 Compare May 24, 2025 21:35
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 58236c1 to fe35189 Compare August 31, 2025 09:22
@renovate renovate bot changed the title fix(deps): update dependency next to v15.2.3 [security] fix(deps): update dependency next to v15.4.7 [security] Aug 31, 2025
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from fe35189 to cbf6d00 Compare October 21, 2025 09:05
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from cbf6d00 to e768163 Compare November 10, 2025 16:59
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from e768163 to d4a162c Compare December 31, 2025 17:00
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from d4a162c to ce6330c Compare January 28, 2026 21:44
@renovate renovate bot changed the title fix(deps): update dependency next to v15.4.7 [security] fix(deps): update dependency next to v16 [security] Jan 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants