v3.11.0

Minor Changes

• #309 10d5b9c1c1826adaec0a9ee49fdf5b91113508ef Thanks @Maximo-Guk! - Revert "Add parity with pages-action for pages deploy outputs"

v3.10.0

Minor Changes

• #303 3ec7f8943ef83351f743cfaa8763a9056ef70993 Thanks @courtney-sims! - Support id, environment, url, and alias outputs for Pages deploys.

v3.9.0

Minor Changes

• #298 134b5c2a3252d66b8c4d1cddd0b9baaeed6a4daa Thanks @Maximo-Guk! - Update wrangler version from 3.13.2 to 3.78.10

Patch Changes

• #278 47d51f25c113ee9205110728599b43ed6a1e273b Thanks @acusti! - fix: Detect existing wrangler install even when wrangler version output is multiline

v3.8.0

Minor Changes

• #291 a1467a0c8f2a058f8d43a4d0c40a55176ed5efe6 Thanks @Ambroos! - Adds deployment-alias-url output for Pages deployment aliases (since Wrangler v3.78.0): cloudflare/workers-sdk#6643

v3.7.0

Minor Changes

• #271 66efca2cbb82a5a49df6af2e14c4b58d53b0e266 Thanks @Maximo-Guk! - This unreverts #235 ensuring wrangler-action will re-use existing wrangler installations, thanks @AdiRishi! and ensures we don't automatically install wrangler when checking if it present

v3.6.1

Patch Changes

• #265 2d275a8f2d279dc91912c1ff8023af109ef3280c Thanks @Maximo-Guk! - Reverts #235 which may have caused the latest version of wrangler to be installed, if no wrangler version was found

v3.6.0

Minor Changes

• #235 0545ad285acaff2b92053d636ee17fb303b4c5f5 Thanks @AdiRishi! - wrangler-action will now re-use existing wrangler installations when available

v3.5.0

Minor Changes

• #255 31a6263ef3ec73ff2d03cb4c0260379f96f7598c Thanks @matthewdavidrodgers! - Stop racing secret uploads

  For up to date versions of wrangler, secrets are uploaded via the 'secret:bulk' command, which batches updates in a single API call.

  For versions of wrangler without that capability, the action falls back to the single 'secret put' command for each secret. It races all these with a Promise.all()

  Unfortunately, the single secret API cannot handle concurrency - at best, these calls have to wait on one another, holding requests open all the while. Often it times out and errors.

  This fixes the legacy secret upload errors by making these calls serially instead of concurrently.

v3.4.1

Patch Changes

• #227 bbedd8e54f256d36f81f81f1f05b90937d533bb7 Thanks @AdiRishi! - Surface inner exception when secret:bulk upload command fails

v3.4.0

Minor Changes

• #213 d13856dfc92816473ebf47f66e263a2668a97896 Thanks @GrantBirki! - This change introduces three new GitHub Actions output variables. These variables are as follows:

  • command-output - contains the string results of stdout
  • command-stderr - contains the string results of stderr
  • deployment-url - contains the string results of the URL that was deployed (ex: https://<your_pages_site>.pages.dev)

  These output variables are intended to be used by more advanced workflows that require the output results or deployment url from Wrangler commands in subsequent workflow steps.

Patch Changes

• #216 9aba9c34daabca23a88191a5fe1b81fa721c1f11 Thanks @Cherry! - Fixes issues with semver comparison, where version parts were treated lexicographically instead of numerically.

  Bulk secret uploading was introduced in wrangler 3.4.0, and this action tries to check if the version used is greater than 3.4.0, and then if so, using the new bulk secret API which is faster. Due to a bug in the semver comparison, 3.19.0 was being considered less than 3.4.0, and then using an older and slower method for uploading secrets.

  Now the semver comparison is fixed, the faster bulk method is used for uploading secrets when available.