Skip to content
Cloudflare Docs

Wrangler

Subscribe to RSS

2025-04-14

3.114.6

Patch Changes

  • #8783 7bcf352 Thanks @petebacondarwin! - Improve error message when request to obtain membership info fails

    Wrangler now informs user that specific permission might be not granted when fails to obtain membership info. The same information is provided when Wrangler is unable to fetch user's email.

  • #8866 db673d6 Thanks @edmundhung! - improve error message when redirected config contains environments

    this change improves that validation error message that users see when a redirected config file contains environments, by:

    • cleaning the message formatting and displaying the offending environments in a list
    • prompting the user to report the issue to the author of the tool which has generated the config

  • #8600 91cf028 Thanks @workers-devprod! - add validation to redirected configs in regards to environments

    add the following validation behaviors to wrangler deploy commands, that relate to redirected configs (i.e. config files specified by .wrangler/deploy/config.json files):

    • redirected configs are supposed to be already flattened configurations without any environment (i.e. a build tool should generate redirected configs already targeting specific environments), so if wrangler encounters a redirected config with some environments defined it should error
    • given the point above, specifying an environment (--env=my-env) when using redirected configs is incorrect, so these environments should be ignored and a warning should be presented to the user

2025-04-10

4.10.0

Minor Changes

Patch Changes

2025-04-09

3.114.5

Patch Changes

2025-04-08

4.9.1

Patch Changes

2025-04-08

4.9.0

Minor Changes

Patch Changes

  • #8809 09464a6 Thanks @dario-piotrowicz! - improve error message when redirected config contains environments

    this change improves that validation error message that users see when a redirected config file contains environments, by:

    • cleaning the message formatting and displaying the offending environments in a list
    • prompting the user to report the issue to the author of the tool which has generated the config

  • #8829 62df08a Thanks @cmackenzie1! - Add option --cors-origin none to remove CORS settings on a pipeline

  • Updated dependencies [afd93b9, 930ebb2]:

2025-04-07

4.8.0

Minor Changes

Patch Changes

  • #8780 4e69fb6 Thanks @cmackenzie1! - - Rename wrangler pipelines show to wrangler pipelines get

    • Replace --enable-worker-binding and --enable-http with --source worker and --source http (or --source http worker for both)
    • Remove --file-template and --partition-template flags from wrangler pipelines create|update
    • Add pretty output for wrangler pipelines get <pipeline>. Existing output is available using --format=json.
    • Clarify the minimums, maximums, and defaults (if unset) for wrangler pipelines create commands.

  • #8596 75b454c Thanks @dario-piotrowicz! - add validation to redirected configs in regards to environments

    add the following validation behaviors to wrangler deploy commands, that relate to redirected configs (i.e. config files specified by .wrangler/deploy/config.json files):

    • redirected configs are supposed to be already flattened configurations without any environment (i.e. a build tool should generate redirected configs already targeting specific environments), so if wrangler encounters a redirected config with some environments defined it should error
    • given the point above, specifying an environment (--env=my-env) when using redirected configs is incorrect, so these environments should be ignored and a warning should be presented to the user

  • #8795 d4c1171 Thanks @GregBrimble! - feat: Unhide wrangler pages functions build command.

    This is already documented for Pages Plugins and by officially documenting it, we can ease the transition to Workers Assets for users of Pages Functions.

  • Updated dependencies [93267cf, ec7e621]:

2025-04-04

4.7.2

Patch Changes

  • #8763 2650fd3 Thanks @garrettgu10! - R2 data catalog URIs now separate account ID and warehouse name with a slash rather than an underscore

  • #8341 196f51d Thanks @kotkoroid! - Improve error message when request to obtain membership info fails

    Wrangler now informs user that specific permission might be not granted when fails to obtain membership info. The same information is provided when Wrangler is unable to fetch user's email.

  • Updated dependencies [e0efb6f, 0a401d0]:

2025-04-04

4.7.1

Patch Changes

2025-04-03

3.114.4

Patch Changes

2025-04-02

4.7.0

Minor Changes

Patch Changes

  • #8720 8df60b5 Thanks @lukevalenta! - Fix logic to derive resource name from binding by replacing all underscores with dashes

  • #8697 ec1f813 Thanks @emily-shen! - fix: stop getPlatformProxy crashing when internal DOs are present

    Internal DOs still do not work with getPlatformProxy, but warn instead of crashing.

  • #8737 624882e Thanks @garvit-gupta! - fix: General improvements for the R2 catalog commands

2025-03-28

4.6.0

Minor Changes

Patch Changes

2025-03-27

4.5.1

Patch Changes

2025-03-26

4.5.0

Minor Changes

Patch Changes

  • #8435 8e3688f Thanks @emily-shen! - fix: include assets binding when printing summary of bindings

  • #8675 f043b74 Thanks @vicb! - Bump @cloudflare/unenv-preset to 2.3.1

    Use the workerd native implementation of createSecureContext and checkServerIdentity from node:tls. The functions have been implemented in cloudflare/workerd#3754.

2025-03-26

4.4.1

Patch Changes

2025-03-26

3.114.3

Patch Changes

2025-03-22

4.4.0

Minor Changes

Patch Changes

2025-03-20

4.3.0

Minor Changes

  • #8258 9adbd50 Thanks @knickish! - Enable the creation of MySQL Hypedrive configs via the Wrangler CLI.

  • #8353 c4fa349 Thanks @jbwcloudflare! - Add new command to purge a Queue

    This new command can be used to delete all existing messages in a Queue

  • #8461 86ab0ca Thanks @GregBrimble! - Add a 'allowTrailingCommas: true' option to improve IDE experience of 'wrangler.jsonc?'

  • #8550 5ae12a9 Thanks @vicb! - Bump @cloudflare/unenv-preset to 2.2.0

    Use the workerd native implementation for node:tls

Patch Changes

2025-03-19

4.2.0

Minor Changes

  • #8477 fd9dff8 Thanks @gabivlj! - wrangler deploy includes container configuration when uploading the script

Patch Changes

2025-03-17

4.1.0

Minor Changes

  • #8337 1b2aa91 Thanks @Ltadrian! - Add mTLS configuration fields to Hyperdrive command

    hyperdrive create test123 ... --ca-certificate-uuid=CA_CERT_UUID --mtls-certificate-uuid=MTLS_CERT_UUID

Patch Changes

2025-03-17

3.114.2

Patch Changes

2025-03-13

4.0.0

We've released the next major version of Wrangler — wrangler@4.0.0. Wrangler v4 is a major release focused on updates to underlying systems and dependencies, along with improvements to keep Wrangler commands consistent and clear.

You can run the following command to install it in your projects:

Unlike previous major versions of Wrangler, which were foundational rewrites and rearchitectures — Version 4 of Wrangler includes a much smaller set of changes. If you use Wrangler today, your workflow is very unlikely to change.

A detailed migration guide is available and if you find a bug or hit a roadblock when upgrading to Wrangler v4, open an issue on the cloudflare/workers-sdk repository on GitHub.

Going forward, we'll continue supporting Wrangler v3 with bug fixes and security updates until Q1 2026, and with critical security updates until Q1 2027, at which point it will be out of support.

The full changelog is available at https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/CHANGELOG.md#400

2025-03-13

2.21.3

Patch Changes

  • #8393 c4653081c Thanks @penalosa! - Deprecate Wrangler v2. Since the release of Wrangler v3 in 2023, we’ve seen great adoption, and today over 95% of active Wrangler usage is with v3.

    As such, Wrangler v2 is now deprecated, and no new features or bug fixes are being published for v2. We strongly recommend you upgrade to the latest version of Wrangler to receive continued support. We have a migration guide to make this process easy! If you encounter any difficulties, please let us know by filing an issue.