Skip to content
Cloudflare Docs

Wrangler

Subscribe to RSS

2025-04-24

4.13.1

Patch Changes

2025-04-23

4.13.0

Minor Changes

  • #8640 5ce70bd Thanks @kentonv! - Add support for defining props on a Service binding.

    In your configuration file, you can define a service binding with props:

    {
    "services": [
        {
            "binding": "MY_SERVICE",
            "service": "some-worker",
            "props": { "foo": 123, "bar": "value" }
        }
    ]
}

    These can then be accessed by the callee:

    import { WorkerEntrypoint } from "cloudflare:workers";

export default class extends WorkerEntrypoint {
    fetch() {
        return new Response(JSON.stringify(this.ctx.props));
    }
}

  • #8771 0cfcfe0 Thanks @dario-piotrowicz! - feat: add config.keep_names option

    Adds a new option to Wrangler to allow developers to opt out of esbuild's keep_names option (https://esbuild.github.io/api/#keep-names). By default, Wrangler sets this to true

    This is something developers should not usually need to care about, but sometimes keep_names can create issues, and in such cases they will be now able to opt-out.

    Example wrangler.jsonc:

    {
    "name": "my-worker",
    "main": "src/worker.ts",
    "keep_names": false
}

Patch Changes

2025-04-22

4.12.1

Patch Changes

2025-04-22

3.114.7

Patch Changes

  • #8955 b7eba92 Thanks @workers-devprod! - When Wrangler encounters an error, if the Bun runtime is detected it will now warn users that Wrangler does not officially support Bun.

  • #8928 8bcb257 Thanks @dario-piotrowicz! - fix redirected config env validation breaking wrangler pages commands

    a validation check has recently been introduced to make wrangler error on deploy commands when an environment is specified and a redirected configuration is in use (the reason being that redirected configurations should not include any environment), this check is problematic with pages commands where the "production" environment is anyways set by default, to address this the validation check is being relaxed here on pages commands

2025-04-17

4.12.0

Minor Changes

  • #8316 69864b4 Thanks @gnekich! - introduce callback-host and callback-port param for wrangler login command

Patch Changes

2025-04-15

4.11.1

Patch Changes

2025-04-15

4.11.0

Minor Changes

Patch Changes

  • #8885 f2802f9 Thanks @CarmenPopoviciu! - Disambiguate the "No files to upload. Proceeding with deployment..." message

  • #8924 d2b44a2 Thanks @dario-piotrowicz! - fix redirected config env validation breaking wrangler pages commands

    a validation check has recently been introduced to make wrangler error on deploy commands when an environment is specified and a redirected configuration is in use (the reason being that redirected configurations should not include any environment), this check is problematic with pages commands where the "production" environment is anyways set by default, to address this the validation check is being relaxed here on pages commands

  • Updated dependencies [f5413c5]:

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