chore(deps): update dependency wrangler to v3.109.0 #534
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.108.1->3.109.0Release Notes
cloudflare/workers-sdk (wrangler)
v3.109.0Compare Source
Minor Changes
#8120
3fb801fThanks @sdnts! - Add a newupdatesubcommand for Queues to allow updating Queue settings#8120
3fb801fThanks @sdnts! - Allow overriding message retention duration when creating Queues#8026
542c6eaThanks @penalosa! - Add--outfiletowrangler deployfor 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
542c6eaThanks @penalosa! - Add awrangler check startupcommand 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 waywrangler check startupbuilds your Worker for analysis, provide the exact arguments you use when deploying your Worker withwrangler deploy. For instance, if you deploy your Worker withwrangler deploy --no-bundle, you should usewrangler 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
fff677eThanks @penalosa! - When reporting errors to Sentry, Wrangler will now include the console output as additional metadata#8120
3fb801fThanks @sdnts! - Check bounds when overriding delivery delay when creating Queues#7950
4db1fb5Thanks @cmackenzie1! - Add local binding support for Worker Pipelines#8119
1bc60d7Thanks @penalosa! - Output correct config format fromwrangler d1 create. Previously, this command would always output TOML, regardless of the config file format#8130
1aa2a91Thanks @emily-shen! - Include default values for wrangler types --path and --x-include-runtime in telemetryUser provided strings are still left redacted as always.
#8061
35710e5Thanks @emily-shen! - fix: respectWRANGLER_LOGinwrangler devPreviously,
--log-level=debugwas the only way to see debug logs inwrangler dev, which was unlike all other commands.Updated dependencies [
4db1fb5]: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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.