tools(deps): bump wrangler from 3.22.4 to 3.26.0 in /tools

[dependabot]

Bumps wrangler from 3.22.4 to 3.26.0.

Release notes

Sourced from wrangler's releases.

wrangler@3.26.0

Minor Changes

• #4847 6968e11f Thanks @​dario-piotrowicz! - feature: expose new (no-op) caches field in getBindingsProxy result

  Add a new caches field to the getBindingsProxy result, such field implements a no operation (no-op) implementation of the runtime caches

  Note: Miniflare exposes a proper caches mock, we will want to use that one in the future but issues regarding it must be ironed out first, so for the time being a no-op will have to do

Patch Changes

• #4860 b92e5ac0 Thanks @​Sibirius! - fix: allow empty strings in secret:bulk upload

  Previously, the secret:bulk command would fail if any of the secrets in the secret.json file were empty strings and they already existed remotely.

• #4869 fd084bc0 Thanks @​jculvey! - feature: Expose AI bindings to getBindingsProxy.

  The getBindingsProxy utility function will now contain entries for any AI bindings specified in wrangler.toml.

• #4880 65da40a1 Thanks @​petebacondarwin! - fix: do not attempt login during dry-run

  The "standard pricing" warning was attempting to make an API call that was causing a login attempt even when on a dry-run. Now this warning is disabled during dry-runs.

  Fixes #4723

• #4819 6a4cb8c6 Thanks @​magnusdahlstrand! - fix: Use appropriate logging levels when parsing headers and redirects in wrangler pages dev.

• Updated dependencies [1e424ff2, 749fa3c0]:

  • miniflare@3.20240129.0

wrangler@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

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.26.0

Minor Changes

• #4847 6968e11f Thanks @​dario-piotrowicz! - feature: expose new (no-op) caches field in getBindingsProxy result

  Add a new caches field to the getBindingsProxy result, such field implements a no operation (no-op) implementation of the runtime caches

  Note: Miniflare exposes a proper caches mock, we will want to use that one in the future but issues regarding it must be ironed out first, so for the time being a no-op will have to do

Patch Changes

• #4860 b92e5ac0 Thanks @​Sibirius! - fix: allow empty strings in secret:bulk upload

  Previously, the secret:bulk command would fail if any of the secrets in the secret.json file were empty strings and they already existed remotely.

• #4869 fd084bc0 Thanks @​jculvey! - feature: Expose AI bindings to getBindingsProxy.

  The getBindingsProxy utility function will now contain entries for any AI bindings specified in wrangler.toml.

• #4880 65da40a1 Thanks @​petebacondarwin! - fix: do not attempt login during dry-run

  The "standard pricing" warning was attempting to make an API call that was causing a login attempt even when on a dry-run. Now this warning is disabled during dry-runs.

  Fixes #4723

• #4819 6a4cb8c6 Thanks @​magnusdahlstrand! - fix: Use appropriate logging levels when parsing headers and redirects in wrangler pages dev.

• Updated dependencies [1e424ff2, 749fa3c0]:

  • miniflare@3.20240129.0

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

... (truncated)

Commits

• 300d427 Version Packages (#4854)
• 65da40a Exclude standardPricingWarning from dryrun (#4880)
• fd084bc [wrangler] Support ai bindings in getBindingsProxy (#4869)
• 6968e11 expose no-op caches in getBindingsProxy (#4847)
• b92e5ac [wrangler] Allow empty strings in secret:bulk (#4860)
• 6a4cb8c [wranger] fix: createMetadataObject to use logging levels (#4265) (#4819)
• fbd2a4c fix/introduce no-unused-vars and no-shadow eslint rules and also include c3.t...
• 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)
• 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)

[dependabot]

Superseded by #55.