Bump wrangler from 3.108.1 to 3.109.0

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Bumps wrangler from 3.108.1 to 3.109.0.

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

• #8120 3fb801f Thanks @​sdnts! - Add a new update subcommand for Queues to allow updating Queue settings

• #8120 3fb801f Thanks @​sdnts! - Allow overriding message retention duration when creating Queues

• #8026 542c6ea Thanks @​penalosa! - Add --outfile to wrangler deploy for generating a worker bundle.

  This is an advanced feature that most users won't need to use. When set, Wrangler will output your built Worker bundle in a Cloudflare specific format that captures all information needed to deploy a Worker using the Worker Upload API

• #8026 542c6ea Thanks @​penalosa! - Add a wrangler check startup command to generate a CPU profile of your Worker's startup phase.

  This can be imported into Chrome DevTools or opened directly in VSCode to view a flamegraph of your Worker's startup phase. Additionally, when a Worker deployment fails with a startup time error Wrangler will automatically generate a CPU profile for easy investigation.

  Advanced usage:

  • --args: to customise the way wrangler check startup builds your Worker for analysis, provide the exact arguments you use when deploying your Worker with wrangler deploy. For instance, if you deploy your Worker with wrangler deploy --no-bundle, you should use wrangler check startup --args="--no-bundle" to profile the startup phase.
  • --worker-bundle: if you don't use Wrangler to deploy your Worker, you can use this argument to provide a Worker bundle to analyse. This should be a file path to a serialised multipart upload, with the exact same format as the API expects: https://developers.cloudflare.com/api/resources/workers/subresources/scripts/methods/update/

Patch Changes

• #8112 fff677e Thanks @​penalosa! - When reporting errors to Sentry, Wrangler will now include the console output as additional metadata

• #8120 3fb801f Thanks @​sdnts! - Check bounds when overriding delivery delay when creating Queues

• #7950 4db1fb5 Thanks @​cmackenzie1! - Add local binding support for Worker Pipelines

• #8119 1bc60d7 Thanks @​penalosa! - Output correct config format from wrangler d1 create. Previously, this command would always output TOML, regardless of the config file format

• #8130 1aa2a91 Thanks @​emily-shen! - Include default values for wrangler types --path and --x-include-runtime in telemetry

  User provided strings are still left redacted as always.

• #8061 35710e5 Thanks @​emily-shen! - fix: respect WRANGLER_LOG in wrangler dev

  Previously, --log-level=debug was the only way to see debug logs in wrangler dev, which was unlike all other commands.

• Updated dependencies [4db1fb5]:

  • [email protected]

Changelog

Sourced from wrangler's changelog.

3.109.0

Minor Changes

• #8120 3fb801f Thanks @​sdnts! - Add a new update subcommand for Queues to allow updating Queue settings

• #8120 3fb801f Thanks @​sdnts! - Allow overriding message retention duration when creating Queues

• #8026 542c6ea Thanks @​penalosa! - Add --outfile to wrangler deploy for generating a worker bundle.

  This is an advanced feature that most users won't need to use. When set, Wrangler will output your built Worker bundle in a Cloudflare specific format that captures all information needed to deploy a Worker using the Worker Upload API

• #8026 542c6ea Thanks @​penalosa! - Add a wrangler check startup command to generate a CPU profile of your Worker's startup phase.

  This can be imported into Chrome DevTools or opened directly in VSCode to view a flamegraph of your Worker's startup phase. Additionally, when a Worker deployment fails with a startup time error Wrangler will automatically generate a CPU profile for easy investigation.

  Advanced usage:

  • --args: to customise the way wrangler check startup builds your Worker for analysis, provide the exact arguments you use when deploying your Worker with wrangler deploy. For instance, if you deploy your Worker with wrangler deploy --no-bundle, you should use wrangler check startup --args="--no-bundle" to profile the startup phase.
  • --worker-bundle: if you don't use Wrangler to deploy your Worker, you can use this argument to provide a Worker bundle to analyse. This should be a file path to a serialised multipart upload, with the exact same format as the API expects: https://developers.cloudflare.com/api/resources/workers/subresources/scripts/methods/update/

Patch Changes

• #8112 fff677e Thanks @​penalosa! - When reporting errors to Sentry, Wrangler will now include the console output as additional metadata

• #8120 3fb801f Thanks @​sdnts! - Check bounds when overriding delivery delay when creating Queues

• #7950 4db1fb5 Thanks @​cmackenzie1! - Add local binding support for Worker Pipelines

• #8119 1bc60d7 Thanks @​penalosa! - Output correct config format from wrangler d1 create. Previously, this command would always output TOML, regardless of the config file format

• #8130 1aa2a91 Thanks @​emily-shen! - Include default values for wrangler types --path and --x-include-runtime in telemetry

  User provided strings are still left redacted as always.

• #8061 35710e5 Thanks @​emily-shen! - fix: respect WRANGLER_LOG in wrangler dev

  Previously, --log-level=debug was the only way to see debug logs in wrangler dev, which was unlike all other commands.

• Updated dependencies [4db1fb5]:

  • [email protected]

Commits

• 35504e9 Version Packages (#8107)
• 1aa2a91 feat: allowlist some types defaults (#8130)
• 542c6ea Support profiling the startup phase of a Worker (#8026)
• 3fb801f feat: Add a queues update subcommand (#8120)
• 1bc60d7 Render correct config format from wrangler d1 create (#8119)
• 4db1fb5 Add Worker Pipelines Binding to Miniflare (#7950)
• fff677e Enable Sentry Console integration (#8112)
• 35710e5 fix: respect WRANGLER_LOG in dev (#8061)
• 0c7d60a refactor: wrangler deploy to usecreateCommand (#7943)
• See full diff 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)