chore(deps): update cloudflare/wrangler-action action to v3 - autoclosed

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudflare/wrangler-action	action	major	1.3.0 -> v3.4.1

---

Release Notes

cloudflare/wrangler-action (cloudflare/wrangler-action)

v3.4.1

Compare Source

Patch Changes

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

v3.4.0

Compare Source

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

Compare Source

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

Compare Source

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

Compare Source

Minor Changes

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

v3.2.1

Compare Source

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

Compare Source

Minor Changes

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

  fixes #​156

v3.1.1

Compare Source

Patch Changes

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

v3.1.0

Compare Source

Minor Changes

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

• #​157 4132892 Thanks @​EstebanBorai! - use [email protected] by default

v3.0.2

Compare Source

Patch Changes

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

v3.0.1

Compare Source

Automating Build & Release

What's Changed

• Artifacts are now ESM supported with .mjs
• Update publish to deploy by @​lrapoport-cf in https://github.com/cloudflare/wrangler-action/pull/124
• Automatically add issues to workers-sdk GH project by @​lrapoport-cf in https://github.com/cloudflare/wrangler-action/pull/127
• Automate Action Release by @​JacobMGEvans in https://github.com/cloudflare/wrangler-action/pull/128

New Contributors

• @​lrapoport-cf made their first contribution in https://github.com/cloudflare/wrangler-action/pull/124

Full Changelog: cloudflare/wrangler-action@3.0.0...3.0.1

v3.0.0

Compare Source

Additions

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

Removals

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

Changes

• Fixed CI/CD issues.

Breaking changes

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

Additional Notes

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

---

v2.0.0

Compare Source

Additions

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

Removals

• Removed publish input (refer to Breaking changes).

Changes

-- no changes --

Breaking changes

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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6ec26ca

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR