chore(deps): update dependency wrangler to v3.25.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
wrangler (source)	3.24.0 -> 3.25.0

---

Release Notes

cloudflare/workers-sdk (wrangler)

v3.25.0

Compare Source

Minor Changes

• #​4815 030360d6 Thanks @​jonesphillip! - feature: adds support for configuring Sippy with Google Cloud Storage (GCS) provider.

  Sippy (https://developers.cloudflare.com/r2/data-migration/sippy/) now supports Google Cloud Storage.
  This change updates the wrangler r2 sippy commands to take a provider (AWS or GCS) and appropriate configuration arguments.
  If you don't specify --provider argument then the command will enter an interactive flow for the user to set the configuration.
  Note that this is a breaking change from the previous behaviour where you could configure AWS as the provider without explictly specifying the --provider argument.
  (This breaking change is allowed in a minor release because the Sippy feature and wrangler r2 sippy commands are marked as beta.)

Patch Changes

• #​4841 10396125 Thanks @​rozenmd! - fix: replace D1's dashed time-travel endpoints with underscored ones

  D1 will maintain its d1/database/${databaseId}/time-travel/* endpoints until GA, at which point older versions of wrangler will start throwing errors to users, asking them to upgrade their wrangler version to continue using Time Travel via CLI.

• #​4656 77b0bce3 Thanks @​petebacondarwin! - fix: ensure upstream_protocol is passed to the Worker

  In wrangler dev it is possible to set the upstream_protocol,
  which is the protocol under which the User Worker believes it has been
  requested, as recorded in the request.url that can be used for
  forwarding on requests to the origin.

  Previously, it was not being passed to wrangler dev in local mode.
  Instead it was always set to http.

  Note that setting upstream_protocol to http is not supported in
  wrangler dev remote mode, which is the case since Wrangler v2.0.

  This setting now defaults to https in remote mode (since that is the only option),
  and to the same as local_protocol in local mode.

  Fixes #​4539

• #​4810 6eb2b9d1 Thanks @​gabivlj! - fix: Cloudchamber command shows json error message on load account if --json specified

  If the user specifies a json option, we should see a more detailed error on why loadAccount failed.

• #​4820 b01c1548 Thanks @​mrbbot! - fix: show up-to-date sources in DevTools when saving source files

  Previously, DevTools would never refresh source contents after opening a file, even if it was updated on-disk. This could cause issues with step-through debugging as breakpoints set in source files would map to incorrect locations in bundled Worker code. This change ensures DevTools' source cache is cleared on each reload, preventing outdated sources from being displayed.

• Updated dependencies [8166eefc]:

  • [email protected]

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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