chore(deps): bump the cloudflare group across 1 directory with 2 updates

[dependabot]

Bumps the cloudflare group with 1 update in the / directory: @opennextjs/cloudflare.

Updates @opennextjs/cloudflare from 1.15.1 to 1.20.5

Release notes

Sourced from @​opennextjs/cloudflare's releases.

@​opennextjs/cloudflare@​1.20.5

Patch Changes

• #1374 64a69ec Thanks @​conico974! - chore: bump @opennextjs/aws to 4.1.3

  See details at https://github.com/opennextjs/opennextjs-aws/releases/tag/v4.1.3

@​opennextjs/cloudflare@​1.20.4

Patch Changes

• #1365 bf52109 Thanks @​vicb! - chore: bump @opennextjs/aws to 4.1.2

  See details at https://github.com/opennextjs/opennextjs-aws/releases/tag/v4.1.2

@​opennextjs/cloudflare@​1.20.3

Patch Changes

• #1361 8c31fbc Thanks @​vicb! - chore: bump @opennextjs/aws to 4.1.1

  See details at https://github.com/opennextjs/opennextjs-aws/releases/tag/v4.1.1

• #1359 65e4487 Thanks @​vicb! - chore: bump the Next.js peer dependency to 15.5.24 / 16.3.3

• #1359 65e4487 Thanks @​vicb! - fix: patch the Turbopack wasm helpers that Next.js 16.3 emits in the chunks

  Until Next.js 16.2 the Turbopack wasm loaders were named loadWebAssembly and loadWebAssemblyModule functions living in [turbopack]_runtime.js, which the adapter rewrote to resolve the chunk through a static import(). Next.js 16.3 emits them on demand in the chunks instead ([turbopack-wasm]/node/loadWasm.ts), so the existing patch silently stopped matching and WebAssembly.compileStreaming - which workerd does not implement - survived into the Worker.

  Every wasm backed import then threw TypeError: WebAssembly.compileStreaming is not a function at runtime, most visibly breaking Prisma with the workerd client runtime.

  The chunks emitted by Turbopack are now patched as well, for both the server and the Node.js middleware bundles.

• #1309 56dfacc Thanks @​ScienHAC! - feature: support Node.js middleware (proxy.ts)

  Next.js 16 replaces middleware.ts with proxy.ts which always runs on the Node.js runtime.

  The Node.js middleware is now bundled into a Workers compatible middleware/handler.mjs: the OpenNext config manifests are inlined at build time (as for the edge middleware) and the middleware compiled by Next.js is statically bundled instead of being loaded from the filesystem at runtime (workerd can not access the filesystem nor load modules at runtime).

  The support is experimental and requires the nodejs_compat compatibility flag.

• #1359 65e4487 Thanks @​vicb! - fix: do not load the instrumentation hook from the Node.js middleware bundle

... (truncated)

Changelog

Sourced from @​opennextjs/cloudflare's changelog.

1.20.5

Patch Changes

• #1374 64a69ec Thanks @​conico974! - chore: bump @opennextjs/aws to 4.1.3

  See details at https://github.com/opennextjs/opennextjs-aws/releases/tag/v4.1.3

1.20.4

Patch Changes

• #1365 bf52109 Thanks @​vicb! - chore: bump @opennextjs/aws to 4.1.2

  See details at https://github.com/opennextjs/opennextjs-aws/releases/tag/v4.1.2

1.20.3

Patch Changes

• #1361 8c31fbc Thanks @​vicb! - chore: bump @opennextjs/aws to 4.1.1

  See details at https://github.com/opennextjs/opennextjs-aws/releases/tag/v4.1.1

• #1359 65e4487 Thanks @​vicb! - chore: bump the Next.js peer dependency to 15.5.24 / 16.3.3

• #1359 65e4487 Thanks @​vicb! - fix: patch the Turbopack wasm helpers that Next.js 16.3 emits in the chunks

  Until Next.js 16.2 the Turbopack wasm loaders were named loadWebAssembly and loadWebAssemblyModule functions living in [turbopack]_runtime.js, which the adapter rewrote to resolve the chunk through a static import(). Next.js 16.3 emits them on demand in the chunks instead ([turbopack-wasm]/node/loadWasm.ts), so the existing patch silently stopped matching and WebAssembly.compileStreaming - which workerd does not implement - survived into the Worker.

  Every wasm backed import then threw TypeError: WebAssembly.compileStreaming is not a function at runtime, most visibly breaking Prisma with the workerd client runtime.

  The chunks emitted by Turbopack are now patched as well, for both the server and the Node.js middleware bundles.

• #1309 56dfacc Thanks @​ScienHAC! - feature: support Node.js middleware (proxy.ts)

  Next.js 16 replaces middleware.ts with proxy.ts which always runs on the Node.js runtime.

  The Node.js middleware is now bundled into a Workers compatible middleware/handler.mjs: the OpenNext config manifests are inlined at build time (as for the edge middleware) and the middleware compiled by Next.js is statically bundled instead of being loaded from the filesystem at runtime (workerd can not access the filesystem nor load modules at runtime).

  The support is experimental and requires the nodejs_compat compatibility flag.

... (truncated)

Commits

• 0d57305 Version Packages (#1375)
• 64a69ec Bump @​opennextjs/aws to 4.1.3 (#1374)
• 0622a45 Version Packages (#1367)
• 877c0b4 chore: bumps @cloudflare/workers-types (#1366)
• bf52109 bump @​opennextjs/aws to 4.1.2 (#1365)
• 9c3b797 Version Packages (#1358)
• 65e4487 chore: bump Next.js to 15.5.24 and 16.3.3 (#1359)
• 8c31fbc bump @opennextjs/aws to 4.1.1 (#1361)
• 56dfacc feat: support Node.js middleware (proxy.ts) (#1309)
• da4b7fc Version Packages (#1307)
• Additional commits viewable in compare view

Updates wrangler from 4.122.0 to 4.127.1

Release notes

Sourced from wrangler's releases.

wrangler@4.127.1

Patch Changes

• #15383 eb01850 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  @​cloudflare/workers-types	^5.20260826.1	^5.20260827.1
  workerd	1.20260826.1	1.20260827.1

• #15393 e1df91a Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  @​cloudflare/workers-types	^5.20260827.1	^5.20260828.1
  workerd	1.20260827.1	1.20260828.1

• Updated dependencies [eb01850, e1df91a, b23de74, 015550a, 015550a, 015550a, 3650d29, b23de74]:

  • miniflare@5.20260828.0-alpha

wrangler@4.127.0

Minor Changes

• #15356 fe265f8 Thanks @​rubuy-74! - Add support for configuring a per-workflow max concurrency limit via workflows[].concurrency.limit in your Wrangler config.

  The limit is the maximum number of Workflow instances that can run concurrently. It is validated as a positive integer and persisted on deploy; the ceiling is enforced server-side. Concurrency is ignored in local development.

  {
    "workflows": [
      {
        "binding": "MY_WORKFLOW",
        "name": "my-workflow",
        "class_name": "MyWorkflow",
        "concurrency": { "limit": 10 }
      }
    ]
  }

Patch Changes

• #15367 412c79e Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

... (truncated)

Commits

• f808554 Version Packages (#15385)
• b903a09 Pin @netlify/build-info to 10.5.1 and update pnpm patch (#14808)
• 3650d29 Rename Worker target fields from workerName to worker (#15373)
• a831498 Version Packages (#15372)
• fe265f8 [wrangler] Add per-workflow concurrency limit config (#15356)
• 92874f6 WC-5857 [wrangler] Upload preview deployments as multipart form data (#15375)
• e9df120 Support multiple named Workers in the build output (#15371)
• 5377aae Version Packages (#15354)
• e56d2e6 Revert "Version Packages" (#15355)
• d765e10 Version Packages (#15291)
• Additional commits viewable in compare view

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[royalpinto007]

Dependabot bump is failing lint/test/format - likely a breaking peer change. Please check CI log.