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.

v3.3.2

Patch Changes

• #171 76d614f Thanks @1000hz! - Fixed issues that caused the action to fail if any secret or var values contained shell metacharacters.

• #171 473d9cb Thanks @1000hz! - Bumped DEFAULT_WRANGLER_VERSION to 3.13.2

v3.3.1

Patch Changes

• #193 a4509d5 Thanks @1000hz! - Fixed the package manager not being inferred based on lockfile when the packageManager input isn't set.

v3.3.0

Minor Changes

• #188 d9a0a00 Thanks @simpleauthority! - Added support for Bun as a package manager

v3.2.1

Patch Changes

• #190 528687a Thanks @1000hz! - Fixed action failure when no packageManager specified and no lockfile is found. The action now falls back to using npm.

v3.2.0

Minor Changes

• #166 7d7b988 Thanks @nix6839! - Support for package managers other than npm, such as pnpm and yarn.

  fixes #156