chore(deps-dev): Bump wrangler from 4.61.0 to 4.131.1

[dependabot]

Bumps wrangler from 4.61.0 to 4.131.1.

Release notes

Sourced from wrangler's releases.

wrangler@4.131.1

Patch Changes

• #15592 945aaa3 Thanks @​WillTaylorDev! - Add a provisioning delay note when custom domain Preview URLs change

  Wrangler now explains that DNS and TLS certificate provisioning may continue after a deploy adds a custom domain or enables its Preview URLs. Stable redeploys don't repeat the note.

  This assumes that a request which matches the stored custom domain state doesn't restart provisioning. The client infers this from the API changeset and current domain record because this repository can't verify the backend behavior.

• #15592 945aaa3 Thanks @​WillTaylorDev! - Clarify production status labels for custom domain routes

  Wrangler now prefixes explicit custom domain production states with production: so they match Preview labels. The updated labels appear in deployed trigger output and WRANGLER_OUTPUT_FILE_PATH.

• #15602 47d906f Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  @​cloudflare/workers-types	^5.20260910.1	^5.20260911.1
  workerd	1.20260910.1	1.20260911.1

• #15592 945aaa3 Thanks @​WillTaylorDev! - Avoid replacement prompts for custom domains already on the Worker

  Wrangler now updates Preview settings without asking to replace a custom domain when that domain already belongs to the deployed Worker. It still asks before replacing domains attached to another Worker.

• #15592 945aaa3 Thanks @​WillTaylorDev! - Explain how to enable Preview URLs when a Preview deployment has none

  wrangler preview now shows URL shapes and configuration snippets for Workers.dev and custom domains. The custom domain snippet preserves every configured route, and the guidance distinguishes missing settings from disabled ones.

  This changes a private beta feature. The warning also makes clear that wrangler deploy publishes code from the current checkout.

• Updated dependencies [47d906f, c2699bf]:

  • miniflare@5.20260911.0-alpha

wrangler@4.131.0

Minor Changes

• #15480 36aed7f Thanks @​skepticfx! - Add Durable Object-managed Containers to top-level container configuration

  Wrangler now accepts scheduling_policy: "durable_object" in the top-level containers array and creates its namespace-backed application after the Worker upload resolves the Durable Object namespace ID. The namespace ID is also the application ID, so repeated deploys idempotently ensure the same application without name-based lookup, modification, or a Containers rollout.

  Durable Object-managed entries accept class_name, scheduling_policy, an optional name, and an optional named images map. Scheduler-only fields are rejected. Each image provides either a local dockerfile or a digest-pinned managed-registry image. Wrangler builds or resolves each image, waits while Cloudflare prepares it for the Containers runtime, and uploads the resulting references with the Worker version for access through ctx.container.images and env.EXPERIMENTAL_CLOUDFLARE_CONTAINER_IMAGES. Local development support for these entries is deferred to a follow-up.

  Existing scheduler-backed entries and Durable Object migrations continue to work unchanged.

  With --containers-rollout=none, existing Workers retain their deployed Container metadata and image binding even when local containers is omitted or empty; local scheduler edits are also ignored. The upload stops if the deployed versions cannot be recovered. Existing Workers for Platforms dispatch scripts reject this flag before upload because their API does not expose enough metadata to preserve Container associations safely. First deployments can still skip Container preparation and rollout. Without this flag, removing managed Containers, including by omitting containers entirely, clears the experimental image binding even with keep_vars.

  versions deploy validates the selected versions before changing traffic and creates their Durable Object-managed applications only after deployment succeeds. Both deploy and versions deploy report partial completion if application creation fails afterward, with instructions to retry the same command.

... (truncated)

Commits

• 00ae21f Version Packages (#15599)
• 945aaa3 [wrangler] Improve custom domain Preview deployment feedback (#15592)
• 6cd67de [wrangler] Allow net.createServer in the unenv-preset e2e test (#15601)
• 7d39eed move more things into containers-shared for cf (#15512)
• 41d7366 Version Packages (#15568)
• b605aa6 [wrangler] Correct Pages delegation analytics (#15581)
• 96688b3 fix(deps): bump shell-quote to patch CVE-2026-9277 / CVE-2026-13311 (#15584)
• 24ef86b [wrangler] Handle dynamic retry delays in workflows instances describe (#15569)
• 36aed7f CC-8364 Add top-level Durable Object-managed Containers (#15480)
• f8aea7e Replace remaining preview_defaults references with previews_base_config (...
• Additional commits viewable in compare view

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Wrangler bump drops Node 20

Medium Severity

Bumping wrangler to 4.129.1 crosses 4.87.0, where Wrangler dropped Node 20, while @sentry/cloudflare still declares engines.node as >=20.19.0 and this PR has no changelog or migration note. Unit tests and the Vite plugin import wrangler, and integration tests spawn wrangler dev, so Node 20 CI and local runs can fail. Flagged because the review rules require an explicit callout when minimum Node support is raised or a supported platform is dropped.

Additional Locations (2)

• dev-packages/cloudflare-integration-tests/package.json#L40-L41
• packages/hono/package.json#L111-L112

 

^{Triggered by project rule: PR Review Guidelines for Cursor Bot}

^{Reviewed by Cursor Bugbot for commit 670619e. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d508e80. Configure here.}

[cursor]

Wrangler bump requires Node 22

High Severity

Pinning wrangler to 4.131.1 drops Node 20 support. From 4.87.0 onward, the CLI hard-fails below Node 22, while this repo still pins Node 20.19.5 via Volta and CI node-version-file. Cloudflare integration tests spawn wrangler dev, so those jobs (and local runs) will crash on the default toolchain without a Node upgrade or a pin at 4.86.0.

Additional Locations (2)

• packages/cloudflare/package.json#L76-L77
• packages/hono/package.json#L111-L112

 

^{Triggered by project rule: PR Review Guidelines for Cursor Bot}

^{Reviewed by Cursor Bugbot for commit d508e80. Configure here.}

[JPeer264]

closing this for now until we have Node v24 locally

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.