• #325 cada7a6 Thanks @Maximo-Guk! - Add GitHub deployments and job summaries for parity with pages-action

• #334 9fed19a Thanks @Maximo-Guk! - Bump default wrangler version to 3.90.0

• #319 59c04629408d58978884fadd18755f1a15f96157 Thanks @Maximo-Guk! - Fixes #317: Generate a new output directory with a randomUUID in the tmpDir, so that when the action is executed multiple times, we use the artifacts from that run, opposed to the artifacts from a previous run.

• #312 122ee5cf5b66847e0b6cfa67ecd9e03e38a67a42 Thanks @Maximo-Guk! - This reapplies 303 add parity with pages-action for pages deploy outputs. Thanks @courtney-sims! - Support pages-deployment-id, pages-environment, pages-deployment-alias-url and deployment-url outputs for Pages deploys when wrangler version is >=3.81.0. deployment-alias-url was also deprecated in favour of pages-deployment-alias.

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

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

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

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

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

• #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

• #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

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

• #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.

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

• #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.

• #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.

• #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

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

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

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

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

  fixes #156

• #161 e5251df Thanks @1000hz! - Refactored error handling to stop execution when action fails. Previously, the action would continue executing to completion if one of the steps encountered an error. Fixes #160.

• #154 3f40637 Thanks @JacobMGEvans! - feat: Quiet mode Some of the stderr, stdout, info & groupings can be a little noisy for some users and use cases. This feature allows for a option to be passed 'quiet: true' this would significantly reduce the noise.

  There will still be output that lets the user know Wrangler Installed and Wrangler Action completed successfully. Any failure status will still be output to the user as well, to prevent silent failures.

  resolves #142

• #147 58f274b Thanks @JacobMGEvans! - Added more error logging when a command fails to execute Previously, we prevented any error logs from propagating too far to prevent leaking of any potentially sensitive information. However, this made it difficult for developers to debug their code.

  In this release, we have updated our error handling to allow for more error messaging from pre/post and custom commands. We still discourage the use of these commands for secrets or other sensitive information, but we believe this change will make it easier for developers to debug their code.

  Relates to #137

• #147 58f274b Thanks @JacobMGEvans! - Adding Changesets

• Version 3.0.0

• Version 2.0.0

• Rewritten Wrangler Action in TypeScript.
• Bulk secrets API utilization from Wrangler.
• Added testing for improved reliability.
• Implemented multiline support for the command input to allow running multiple Wrangler commands.
• Now using Node for the Action engine/runner.
• Open discussions with the community on all changes through GitHub Discussions and monitored Issues.

• Removed Docker as a dependency.
• Dropped support for Wrangler v1.

• Fixed CI/CD issues.

• Wrangler v1 is no longer supported.
  • Please update to the latest version of Wrangler.
• Updated default version of Wrangler to v3.4.0

• Major Version Default: DEVX-632
• Rewrite Project Tickets: DEVX-804, DEVX-802, DEVX-800, DEVX-632

• New command input
  • This allows you to specify the Wrangler command you would like to run. For example, if you want to publish the production version of your Worker you may run publish --env=production.
  • This opens up other possibilities too like publishing a Pages project: pages publish <directory> --project-name=<name>.
• New accountId input
  • This allows you to specify your account ID.

• Removed publish input (refer to Breaking changes).

-- no changes --

• publish has been removed.
  • You should instead do `command: