chore(deps-dev): bump wrangler from 3.22.1 to 3.25.0

[dependabot]

Bumps wrangler from 3.22.1 to 3.25.0.

Release notes

Sourced from wrangler's releases.

[email protected]

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]

[email protected]

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.25.0

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]

3.24.0

Minor Changes

... (truncated)

Commits

• 75f99d7 Version Packages (#4826)
• 1039612 [D1] replace D1's dashed time-travel endpoints with underscored ones (#4841)
• 030360d Added support for configuring Sippy with GCS provider in Wrangler (#4815)
• 6eb2b9d cloudchamber: add internal module insertion (#4810)
• b01c154 [wrangler] fix: reset inspector execution contexts on reload (#4820)
• 77b0bce fix: ensure upstream_protocol is passed to the Worker (#4656)
• a979d9e Version Packages (#4781)
• 5e25935 Gradual Rollouts versions upload (experimental) command (#4744)
• c3e410c chore: bump undici versions to 5.28.2 (#4768)
• f4f1dc6 make sure getBindingsProxy supports .dev.vars files (#4796)
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)