Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 1, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
cloudflare/wrangler-action action major 2.0.0 -> v3.6.1

Release Notes

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

v3.6.1

Compare Source

Patch Changes

v3.6.0

Compare Source

Minor Changes

v3.5.0

Compare Source

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

Compare Source

Patch Changes

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

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

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

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 wrangler@3.5.1 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
New Contributors

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


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.

@renovate renovate bot force-pushed the renovate/cloudflare-wrangler-action-3.x branch 2 times, most recently from 7557d83 to 7ee0006 Compare August 11, 2023 01:26
@renovate renovate bot force-pushed the renovate/cloudflare-wrangler-action-3.x branch from 7ee0006 to 0419902 Compare August 17, 2023 18:55
@renovate renovate bot force-pushed the renovate/cloudflare-wrangler-action-3.x branch 3 times, most recently from a498e15 to 94568f1 Compare August 31, 2023 16:31
@renovate renovate bot force-pushed the renovate/cloudflare-wrangler-action-3.x branch from 94568f1 to 03cd9fe Compare October 2, 2023 15:24
@renovate renovate bot force-pushed the renovate/cloudflare-wrangler-action-3.x branch 3 times, most recently from 22d27bb to 5f5003c Compare October 11, 2023 19:40
@renovate renovate bot force-pushed the renovate/cloudflare-wrangler-action-3.x branch from 5f5003c to cb380e6 Compare October 24, 2023 19:52
@renovate renovate bot force-pushed the renovate/cloudflare-wrangler-action-3.x branch from cb380e6 to d37f00a Compare December 19, 2023 20:06
@renovate renovate bot force-pushed the renovate/cloudflare-wrangler-action-3.x branch from d37f00a to 4bbea73 Compare January 9, 2024 19:54
@renovate renovate bot force-pushed the renovate/cloudflare-wrangler-action-3.x branch from 4bbea73 to 0ba62ad Compare May 1, 2024 13:19
@renovate renovate bot force-pushed the renovate/cloudflare-wrangler-action-3.x branch from 0ba62ad to a05c2a6 Compare May 23, 2024 17:01
@renovate renovate bot force-pushed the renovate/cloudflare-wrangler-action-3.x branch from a05c2a6 to fc43291 Compare May 24, 2024 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants