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

[dependabot]

Bumps the cloudflare group with 2 updates in the / directory: @opennextjs/cloudflare and wrangler.

Updates @opennextjs/cloudflare from 1.15.1 to 1.20.6

Release notes

Sourced from @​opennextjs/cloudflare's releases.

@​opennextjs/cloudflare@​1.20.6

Patch Changes

• #1378 7a990e7 Thanks @​vicb! - Bump Next to 16.3.4 and @opennextjs/aws to 4.1.4

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

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

... (truncated)

Changelog

Sourced from @​opennextjs/cloudflare's changelog.

1.20.6

Patch Changes

• #1378 7a990e7 Thanks @​vicb! - Bump Next to 16.3.4 and @opennextjs/aws to 4.1.4

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

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)

... (truncated)

Commits

• a63350a Version Packages (#1379)
• 7a990e7 chore: bump Next and @​opennextjs/aws (#1378)
• 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)
• Additional commits viewable in compare view

Updates wrangler from 4.136.0 to 4.142.0

Release notes

Sourced from wrangler's releases.

wrangler@4.142.0

Minor Changes

• #15856 4c2993b Thanks @​Naapperas! - Support Workflows declared in exports on ctx.exports in local development

  A Workflow declared in a Worker's exports is now available on ctx.exports in wrangler dev, the Vite plugin and the Vitest plugin, with the same API as a Workflow binding:

  const instance = await ctx.exports.MyWorkflow.create({
    params: { name: "World" },
  });

  ctx.exports and workflows bindings with the same Workflow name share their instances, including instances created before the Workflow was declared in exports. Two Workers can't export the same Workflow name, and a binding to an exported Workflow must refer to the Worker and class that export it. getPlatformProxy() ignores Workflows declared in exports, since it doesn't run the Worker's code.

  wrangler workflows commands run with --local also work with Workflows declared only in exports, without a workflows binding.

  In the Vitest plugin, introspectWorkflow() and introspectWorkflowInstance() still need a Workflow binding, and now explain how to add one when passed a Workflow from ctx.exports. Instances created through ctx.exports are introspected too. A workflows binding whose script_name is the Worker's own name now resolves to the Worker itself again.

Patch Changes

• #15891 8dc53ae Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  @​cloudflare/workers-types	^5.20260925.1	^5.20260926.1
  workerd	1.20260925.1	1.20260926.1

• Updated dependencies [8dc53ae, 4c2993b]:

  • miniflare@5.20260926.0-alpha

wrangler@4.141.0

Minor Changes

• #15658 8280086 Thanks @​jqmmes! - Add Durable Objects code update strategies to Worker deployments

  Use --durable-objects-code-update-mode immediate with wrangler deploy, wrangler versions deploy, and wrangler rollback to update code without waiting for active instances to hibernate. Use --durable-objects-code-update-mode deferred 30s to set a maximum delay, or configure durable_objects.code_update_strategy with mode and max_delay. When unset, the strategy defaults to deferred with a 5-minute maximum delay; delays cannot exceed 24 hours and must use millisecond precision.

• #15800 bd56b98 Thanks @​Refaerds! - Add Browser Run as an event source for Queue subscriptions

  You can now create Queue subscriptions with --source browserRun.

Patch Changes

• #15864 ee2b200 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

... (truncated)

Commits

• f96458c Version Packages (#15882)
• 4c2993b Emit new Worker config for same-worker Workflows (#15856)
• 8d61ca8 Version Packages (#15867)
• 8280086 [wrangler] Add Durable Objects hibernation timeout option (#15658)
• 805af2f [wrangler] Log ProxyWorker request error details at debug level (#15207)
• bd56b98 [wrangler] Add browserRun event source type for queue subscriptions (#15800)
• 72056b7 [wrangler] Clean up retired Container image binding tests (#15787)
• 84c819f Version Packages (#15857)
• 8f7916c [deploy-helpers] Containers support for Worker Preview deployments in the Bui...
• c59dae6 Version Packages (#15828)
• 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.