Skip to content

chore(deps): bump the cloudflare group with 2 updates - #122

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/cloudflare-cc2f35db11
Open

chore(deps): bump the cloudflare group with 2 updates#122
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/cloudflare-cc2f35db11

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 21, 2026

Copy link
Copy Markdown
Contributor

Bumps the cloudflare group with 2 updates: @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

@​opennextjs/cloudflare@​1.20.5

Patch Changes

@​opennextjs/cloudflare@​1.20.4

Patch Changes

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

1.20.5

Patch Changes

1.20.4

Patch Changes

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

Updates wrangler from 4.131.1 to 4.134.0

Release notes

Sourced from wrangler's releases.

wrangler@4.134.0

Minor Changes

  • #15684 6874aa9 Thanks @​Ankcorn! - Add support for configuring real-time Issues with observability.issues.enabled

    Wrangler now validates and uploads the Issues setting alongside the existing logs and traces observability options. The experimental configuration format supports the equivalent observability.issues.enabled option.

  • #15681 d96b319 Thanks @​podonnell-dev! - Mark wrangler preview commands as open beta

    Wrangler now labels Preview commands as open beta in help output and command warnings, matching the feature's public availability.

  • #15673 2b39fc2 Thanks @​ghostwriternr! - Support explicit named Container image selection in Wrangler local development

    Wrangler builds or pulls named images configured through Wrangler JSON or TOML and exposes their local tags through ctx.container.images. Pass one of those references to ctx.container.start({ image }) to select the image.

    This extends the experimental Durable Object-managed Containers interface. Named images are opt-in and do not become the Container's default image. A Container without a default image must supply an image or full Container snapshot when starting.

Patch Changes

wrangler@4.133.0

Minor Changes

  • #15600 bac0c6a Thanks @​podonnell-dev! - Add placement configuration for Previews

    You can now configure placement in the previews block. Preview-specific placement overrides the top-level placement configuration for Preview Defaults and deployments.

  • #15600 bac0c6a Thanks @​podonnell-dev! - Improve onboarding guidance for Previews (when previews block is missing from configuration file)

    When a local previews block is absent, Wrangler writes the Preview Base configuration to the local config file. When no Preview Base configuration exists, Wrangler prints a placeholder configuration derived from production bindings and warns against reusing production binding configuration.

Patch Changes

  • #15483 71b6f10 Thanks @​tpmmorris! - Align Local Explorer Workflow instance status requests with production

    Local Explorer and Wrangler local mode now use the production-compatible status request field for pausing, resuming, restarting, and terminating Workflow instances. Direct Local Explorer API consumers must replace the previous action field with status.

    Successful Local Explorer status updates now return the production-compatible instance status and response timestamp instead of the local-only result.success acknowledgement.

... (truncated)

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
chore(deps): bump the cloudflare group with 2 updates
02f5b86 
Bumps the cloudflare group with 2 updates: [@opennextjs/cloudflare](https://github.com/opennextjs/opennextjs-cloudflare/tree/HEAD/packages/cloudflare) and [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler).


Updates `@opennextjs/cloudflare` from 1.15.1 to 1.20.6
- [Release notes](https://github.com/opennextjs/opennextjs-cloudflare/releases)
- [Changelog](https://github.com/opennextjs/opennextjs-cloudflare/blob/main/packages/cloudflare/CHANGELOG.md)
- [Commits](https://github.com/opennextjs/opennextjs-cloudflare/commits/@opennextjs/cloudflare@1.20.6/packages/cloudflare)

Updates `wrangler` from 4.131.1 to 4.134.0
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.134.0/packages/wrangler)

---
updated-dependencies:
- dependency-name: "@opennextjs/cloudflare"
  dependency-version: 1.20.6
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: cloudflare
- dependency-name: wrangler
  dependency-version: 4.134.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: cloudflare
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Sep 21, 2026

Copy link
Copy Markdown
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants