8000 Update dependency wrangler to v3.111.0 by renovate[bot] · Pull Request #61 · tuist/handbook · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Update dependency wrangler to v3.111.0 #61

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 3, 2025

Conversation

renovate[bot]
Copy link
Contributor
@renovate renovate bot commented Feb 13, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
wrangler (source) 3.108.1 -> 3.111.0 age adoption passing confidence

Release Notes

cloudflare/workers-sdk (wrangler)

v3.111.0

Compare Source

Minor Changes
Patch Changes

v3.110.0

Compare Source

Minor Changes
  • #​8253 6dd1e23 Thanks @​CarmenPopoviciu! - Add --cwd global argument to the wrangler CLI to allow changing the current working directory before running any command.
Patch Changes

v3.109.3

Compare Source

Patch Changes

v3.109.2

Compare Source

Patch Changes

v3.109.1

Compare Source

Patch Changes

v3.109.0

Compare Source

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]:

    • miniflare@3.20250204.1

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update dependency wrangler to v3.109.0 Update dependency wrangler to v3.109.1 Feb 14, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x-lockfile branch 2 times, most recently from 929be1d to 6e8a787 Compare February 18, 2025 23:38
@renovate renovate bot changed the title Update dependency wrangler to v3.109.1 Update dependency wrangler to v3.109.2 Feb 18, 2025
@renovate renovate bot changed the title Update dependency wrangler to v3.109.2 Update dependency wrangler to v3.109.3 Feb 24, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x-lockfile branch 2 times, most recently from 093b8e3 to 6369ef0 Compare February 25, 2025 23:05
@renovate renovate bot changed the title Update dependency wrangler to v3.109.3 Update dependency wrangler to v3.110.0 Feb 25, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x-lockfile branch from 6369ef0 to 9600fbc Compare February 27, 2025 10:59
@renovate renovate bot changed the title Update dependency wrangler to v3.110.0 Update dependency wrangler to v3.111.0 Feb 27, 2025
@pepicrft pepicrft merged commit 85240ec into main Mar 3, 2025
3 checks passed
@renovate renovate bot deleted the renovate/wrangler-3.x-lockfile branch March 3, 2025 10:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
0