chore(deps): update dependency wrangler to v4.47.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
wrangler (source)	4.45.3 -> 4.47.0

---

Release Notes

cloudflare/workers-sdk (wrangler)

v4.47.0

Compare Source

Minor Changes

• #​11201 5286309 Thanks @​avenceslau! - Add wrangler workflows instances restart command

• #​11214 5cf8a39 Thanks @​penalosa! - Add the experimental wrangler setup command to run autoconfig outside of the deploy flow.

• #​11187 8abc789 Thanks @​dario-piotrowicz! - Add possibility for users to edit their project settings during autoconfig

  When running wrangler deploy --experimental-autoconfig, after the automatic project settings detection Wrangler will now present users the opportunity to customize the auto-detected project's settings

Patch Changes

• #​11143 2d16610 Thanks @​FlorentCollin! - Improve the formatting of the D1 execute command to always show the duration in milliseconds with two decimal places.

• #​11178 63defa2 Thanks @​ascorbic! - Log a more helpful error when attempting to "r2 object put" a non-existent file

• #​11199 70d3d4a Thanks @​penalosa! - Add telemetry to autoconfig

• #​11186 38396ed Thanks @​hoodmane! - Removed warning when deploying a Python worker

• #​11024 cdcecfc Thanks @​devin-ai-integration! - Use the native node:trace_events module when available

  It is enabled when the enable_nodejs_trace_events_module compatibility flag is set.

• #​11195 e85f965 Thanks @​ascorbic! - Ignores .dev.vars if --env-file has been explicitly passed

  Previously, .dev.vars would always be read first, and then any file passed with --env-file would override variables in .dev.vars. This meant there was no way to ignore .dev.vars if you wanted to use a different env file. Now, if --env-file is passed, .dev.vars will be ignored entirely.

• #​11181 88aa707 Thanks @​petebacondarwin! - add more logging around Wrangler authentication to help diagnose issues

• Updated dependencies [dd7d584, 4259256, cdcecfc]:

  • miniflare@​4.20251109.0
  • @​cloudflare/unenv-preset@​2.7.10

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

---

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 09ad6b0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR