chore(deps-dev): bump wrangler from 4.112.0 to 4.147.0

[dependabot]

Bumps wrangler from 4.112.0 to 4.147.0.

Release notes

Sourced from wrangler's releases.

wrangler@4.147.0

Minor Changes

• #15928 7f57b1c Thanks @​ichernetsky-cf! - Allow "us" as a jurisdiction for Container applications

  Container placement constraints now accept constraints.jurisdiction: "us" in Wrangler and typed Cloudflare configuration. This makes the US jurisdiction available alongside "eu" and "fedramp".

Patch Changes

• #15974 7f700ef Thanks @​martinezjandrew! - Fix wrangler containers list to report live instances

  The LIVE INSTANCES column now reports each application's active runtime instances instead of its configured instance count, matching the Cloudflare dashboard. JSON output continues to expose the configured count through the existing instances field.

• #15980 90e6a1b Thanks @​martinezjandrew! - Accept Durable Object application IDs in Containers commands

  wrangler containers instances and wrangler containers delete now accept the 32-character hexadecimal application IDs returned for Durable Object-backed applications, in addition to legacy dashed UUIDs.

• #15871 6a4b0fe Thanks @​tw4! - Retry transient API failures in wrangler workflows instances list and wrangler workflows instances describe

  Previously, a single temporary 5xx response or dropped connection made these read-only commands exit with an error, even though the next request would have succeeded. They now use Wrangler's existing bounded API retry handling. The read that resolves --id latest is retried too, which also benefits the other wrangler workflows instances commands that accept latest; the mutating requests they make afterwards are not retried. Persistent failures are still reported after the retries are exhausted, and under --json any retry notices are written to stderr so stdout stays valid JSON.

• Updated dependencies []:

  • miniflare@5.20261001.0-alpha

wrangler@4.146.0

Minor Changes

• #15777 464a582 Thanks @​Naapperas! - Support the new Workflows createBatch() API in local development

  Local Workflows bindings now accept object-form batches that create instances from a count or a list of instance options. The result includes handles for created instances and indexed per-instance errors, matching the runtime API while preserving the deprecated array form.

• #15639 aee2842 Thanks @​hugo-vicente11! - Add --allowed-mail to the experimental wrangler tunnel quick-start command

  The option forwards exact email addresses, comma-separated lists, and wildcard domains to cloudflared. It can be specified more than once to combine multiple recipient rules.

  Email-protected tunnels require cloudflared 2026.9.2 or later. Wrangler checks the selected binary before starting the tunnel and reports an upgrade error when it is incompatible.

Patch Changes

• #15992 b8e7cc3 Thanks @​zebp! - Mark wrangler artifacts commands as open beta

  Artifacts has entered open beta, so the wrangler artifacts commands no longer display a "private beta" label in help output and warnings.

• #15984 9d7b08e Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  @​cloudflare/workers-types	^5.20260930.2	^5.20261001.1

... (truncated)

Commits

• 64c1337 Version Packages (#15996)
• 6a4b0fe [wrangler] Retry transient failures in workflows instances list and describe ...
• 7f700ef CC-8799: report active instead of configured instances in containers list (#1...
• 90e6a1b CC-8800: accept durable object app ids in container commands (#15980)
• b4954c1 Version Packages (#15983)
• b8e7cc3 [wrangler] Mark Artifacts commands as open beta (#15992)
• aee2842 [wrangler] Support email-protected Quick Tunnels (#15639)
• efd67e6 [wrangler] Keep colons in wrangler tail --header filter values (#15959)
• 89061a4 Version Packages (#15957)
• 4a5ab6c Preserve existing secret bindings during Worker deployments (#15964)
• Additional commits viewable in compare view

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[greptile-apps]

Confidence Score: 4/5

[High risk] Bumps the build and deployment tool to a newer version.

The PR appears safe to merge, with a non-blocking generated-types and CI-ordering concern.

Findings

1.  Generated Worker types are stale ▶

Fix with agent prompt

### Issue 1
package.json:32
This Wrangler upgrade also changes the resolved workerd version, but the committed `worker-configuration.d.ts` still names the old version. CI type-checks before running `wrangler types`, so it does not check application code against the types generated by the upgrade. Regenerating the committed types and type-checking after generation would keep the checked types aligned with the new toolchain.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

This PR updates Wrangler from 4.112.0 to 4.147.0 and refreshes its locked local-runtime dependencies. The generated Worker types have not been updated to match the new workerd version.

_{Reviews (1) · Last reviewed commit: "chore(deps-dev): bump wrangler from 4.11..."}

[greptile-apps]

Generated Worker types are stale

This Wrangler upgrade also changes the resolved workerd version, but the committed worker-configuration.d.ts still names the old version. CI type-checks before running wrangler types, so it does not check application code against the types generated by the upgrade. Regenerating the committed types and type-checking after generation would keep the checked types aligned with the new toolchain.

Prompt To Fix With AI

This is a comment left during a code review.
Path: package.json
Line: 32

Comment:
**Generated Worker types are stale**

This Wrangler upgrade also changes the resolved workerd version, but the committed `worker-configuration.d.ts` still names the old version. CI type-checks before running `wrangler types`, so it does not check application code against the types generated by the upgrade. Regenerating the committed types and type-checking after generation would keep the checked types aligned with the new toolchain.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.