fix(deps): upgrade npm packages

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@cloudflare/workers-types	4.20251014.0 -> 4.20251107.0
wrangler (source)	4.44.0 -> 4.46.0

---

Release Notes

cloudflare/workerd (@​cloudflare/workers-types)

v4.20251107.0

Compare Source

v4.20251106.1

Compare Source

cloudflare/workers-sdk (wrangler)

v4.46.0

Compare Source

Minor Changes

• #​11183 240ebeb Thanks @​dario-piotrowicz! - expose experimental_getDetailsForAutoConfig and experimental_runAutoConfig APIs that provide respectively the autoconfig detection and execution functionalities

• #​11180 53b0fce Thanks @​penalosa! - Detect non-framework static sites

• #​11162 c3ed531 Thanks @​dario-piotrowicz! - add a remoteBindings option to getPlatformProxy to allow the disabling of remote bindings

• #​11164 305d7bf Thanks @​penalosa! - Implement experimental autoconfig flow for static sites

• #​10605 b55a3c7 Thanks @​emily-shen! - Add command to configure credentials for non-Cloudflare container registries

  Note this is a closed/experimental command that will not work without the appropriate account-level capabilities.

• #​11078 5d7c4c2 Thanks @​simonha9! - Add jurisdiction support to d1 db creation via command-line argument

Patch Changes

• #​11160 05440a1 Thanks @​dario-piotrowicz! - Allows auto-update of the local Wrangler configuration file to match remote configuration when running wrangler deploy --env <TARGET_ENV>

  When running wrangler deploy, with --x-remote-diff-check and after cancelling the deployment due to destructive changes present in the local config file, Wrangler offers to update the Wrangler configuration file to match the remote configuration. This wasn't however enabled when a target environment was specified (via the --env|-e flag). Now this will also apply when an environment is targeted.

• #​11162 c3ed531 Thanks @​dario-piotrowicz! - Update the description of the --local flag for the wrangler dev command to clarify that it disables remote bindings, also un-deprecate and un-hide it

• #​11162 c3ed531 Thanks @​dario-piotrowicz! - Fix bindings with remote: true being logged as remote when run via wrangler dev --local

• Updated dependencies [1ae020d]:

  • miniflare@​4.20251105.0

v4.45.4

Compare Source

Patch Changes

• #​11133 8ffbd17 Thanks @​petebacondarwin! - Reduce the amount of arguments being passed in metrics capture.

  Now the argument values that are captured come from an allow list,
  and can be marked as ALLOW (capture the real value) or REDACT (capture as "").

• #​11033 77ed7e2 Thanks @​dario-piotrowicz! - Offer to update the local Wrangler configuration file to match remote configuration when running wrangler deploy

  When running wrangler deploy, with --x-remote-diff-check, Wrangler will display the difference between local and remote configuration.
  If there would be a destructive change to the remote configuration, the user is given the option to cancel the deployment.
  In the case where the user does cancel deployment, Wrangler will now also offer to update the local Wrangler configuration file to match the remote configuration.

• #​11139 bb00f9d Thanks @​devin-ai-integration! - Updated cron trigger documentation links and improved error message to include instructions for testing cron triggers locally

• #​11135 ed666a1 Thanks @​penalosa! - Implement tail-based logging for wrangler dev remote mode, behind the --x-tail-tags flag. This will become the default in the future.

• #​11149 22f25fd Thanks @​penalosa! - Add no-op autoconfig logic behind an experimental flag

• Updated dependencies [90a2566, 14f60e8]:

  • @​cloudflare/unenv-preset@​2.7.9
  • miniflare@​4.20251011.2

v4.45.3

Patch Changes

• #​11117 6822aaf Thanks @​emily-shen! - fix: show local/remote status before D1 command confirmations

  D1 commands (execute, export, migrations apply, migrations list, delete, time-travel) now display whether they're running against local or remote databases before showing confirmation prompts. This prevents confusion about which database will be affected by the operation.

• #​11077 bce8142 Thanks @​petebacondarwin! - Ensure that process.env is case-insensitive on Windows

  The object that holds the environment variables in process.env does not care about the case of its keys
  in Windows. For example, process.env.SystemRoot and process.env.SYSTEMROOT will refer to the same value.

  Previously, when merging fields from .env files we were replacing this native object with a vanilla
  JavaScript object, that is case-insensitive, and so sometimes environment variables appeared to be missing
  when in reality they just had different casing.

v4.45.2

Patch Changes

• #​11097 55657eb Thanks @​penalosa! - Extract internal APIs into a new @cloudflare/workers-utils package

• #​11118 d47f166 Thanks @​zebp! - Fix validation of the persist field of observability logs and traces configuration

v4.45.1

Compare Source

Patch Changes

• #​10959 d0208fe Thanks @​devin-ai-integration! - Fixed conflict between --env and --expires flags in wrangler r2 object put.

  --e now aliases --env only, and NOT --expires.

• #​10915 dbe51c1 Thanks @​devin-ai-integration! - Fixed self-bindings (service bindings to the same worker) showing as [not connected] in wrangler dev. Self-bindings now correctly show as [connected] since a worker is always available to itself.

• #​10913 d4f2daf Thanks @​devin-ai-integration! - Fixed duplicate warning messages appearing during wrangler dev when configuration changes or state transitions occur

v4.45.0

Compare Source

Minor Changes

• #​11030 1a8088a Thanks @​penalosa! - Enable automatic resource provisioning by default in Wrangler. This is still an experimental feature, but we're turning on the flag by default to make it easier for people to test it and try it out. You can disable the feature using the --no-x-provision flag. It currently works for R2, D1, and KV bindings.

  To use this feature, add a binding to your config file without a resource ID:

  {
  	"kv_namespaces": [{ "binding": "MY_KV" }],
  	"d1_databases": [{ "binding": "MY_DB" }],
  	"r2_buckets": [{ "binding": "MY_R2" }],
  }

  wrangler dev will automatically create these resources for you locally, and when you next run wrangler deploy Wrangler will call the Cloudflare API to create the requested resources and link them to your Worker. They'll stay linked across deploys, and you don't need to add the resource IDs to the config file for future deploys to work. This is especially good for shared templates, which now no longer need to include account-specific resource ID when adding a binding.

Patch Changes

• #​11037 4bd4c29 Thanks @​danielrs! - Better Wrangler subdomain defaults warning.

  Improves the warnings that we show users when either worker_dev or preview_urls are missing.

• #​10927 31e1330 Thanks @​dom96! - Implements python_modules.excludes wrangler config field

  [python_modules]
  excludes = ["**/*.pyc", "**/__pycache__"]

• #​10741 2f57345 Thanks @​penalosa! - Remove obsolete --x-remote-bindings flag

• Updated dependencies [ca6c010]:

  • miniflare@​4.20251011.1

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.