Skip to content

Wrangler

2024-09-06

3.75.0

Minor Changes

  • #6603 a197460 Thanks @taylorlee! - feature: log version preview url when previews exist

    The version upload API returns a field indicating whether a preview exists for that version. If a preview exists and workers.dev is enabled, wrangler will now log the full URL on version upload.

    This does not impact wrangler deploy, which only prints the workers.dev route of the latest deployment.

  • #6550 8d1d464 Thanks @Pedr0Rocha! - feature: add RateLimit type generation to the ratelimit unsafe binding.

Patch Changes

  • #6615 21a09e0 Thanks @RamIdeas! - chore: avoid potential double-install of create-cloudflare

    When wrangler init delegates to C3, it did so via npm create cloudflare@2.5.0. C3's v2.5.0 was the first to include auto-update support to avoid npx's potentially stale cache. But this also guaranteed a double install for users who do not have 2.5.0 cached. Now, wrangler delegates via npm create cloudflare@^2.5.0 which should use the latest version cached on the user's system or install and use the latest v2.x.x.

  • #6603 a197460 Thanks @taylorlee! - chore: fix version upload log order

    Previously deploy prints: upload timings deploy timings current version id

    while version upload prints: worker version id upload timings

    This change makes version upload more similar to deploy by printing version id after upload, which also makes more sense, as version ID can only be known after upload has finished.

2024-09-03

3.74.0

Minor Changes

Patch Changes

2024-08-30

3.73.0

Minor Changes

  • #6571 a7e1bfe Thanks @penalosa! - feat: Add deployment http targets to wrangler deploy logs, and add url to pages deploy logs

  • #6497 3bd833c Thanks @WalshyDev! - chore: move wrangler versions ..., wrangler deployments ..., wrangler rollback and wrangler triggers ... out of experimental and open beta. These are now available to use without the --x-versions flag, you can continue to pass this however without issue to keep compatibility with all the usage today.

    A few of the commands had an output that wasn't guarded by --x-versions those have been updated to use the newer output, we have tried to keep compatibility where possible (for example: wrangler rollback will continue to output "Worker Version ID:" so users can continue to grab the ID). If you wish to use the old versions of the commands you can pass the --no-x-versions flag. Note, these will be removed in the future so please work on migrating.

  • #6586 72ea742 Thanks @penalosa! - feat: Inject a 404 response for browser requested favicon.ico files when loading the /__scheduled page for scheduled-only Workers

  • #6497 3bd833c Thanks @WalshyDev! - feat: update wrangler deploy to use the new versions and deployments API. This should have zero user-facing impact but sets up the most used command to deploy Workers to use the new recommended APIs and move away from the old ones. We will still call the old upload path where required (e.g. Durable Object migration or Service Worker format).

Patch Changes

2024-08-27

3.72.3

Patch Changes

2024-08-22

3.72.2

Patch Changes

2024-08-20

3.72.1

Patch Changes

  • #6530 d0ecc6a Thanks @WalshyDev! - fix: fixed wrangler versions upload printing bindings twice

  • #6502 a9b4f25 Thanks @garvit-gupta! - fix: Fix Vectorize List MetadataIndex Http Method

  • #6508 56a3de2 Thanks @petebacondarwin! - fix: move the Windows C++ redistributable warning so it is only shown if there is an actual access violation

    Replaces #6471, which was too verbose.

    Fixes #6170

2024-08-16

3.72.0

Minor Changes

  • #6479 3c24d84 Thanks @petebacondarwin! - feat: allow HTTPS custom certificate paths to be provided by a environment variables

    As well as providing paths to custom HTTPS certificate files, it is now possible to use WRANGLER_HTTPS_KEY_PATH and WRANGLER_HTTPS_CERT_PATH environment variables.

    Specifying the file paths at the command line overrides specifying in environment variables.

    Fixes #5997

Patch Changes