Update cloudflare/wrangler-action action to v3 #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.0.0->v3.14.1Release Notes
cloudflare/wrangler-action (cloudflare/wrangler-action)
v3.14.1Compare Source
Patch Changes
cd6314aThanks @penalosa! - Usesecret bulkinstead of deprecatedsecret:bulkcommandv3.14.0Compare Source
Minor Changes
4ff07f4Thanks @Maximo-Guk! - Use wrangler outputs for version upload and wrangler deployPatch Changes
e209094Thanks @Maximo-Guk! - Handle failures in createGitHubDeployment and createGitHubJobSummaryv3.13.1Compare Source
Patch Changes
e819570Thanks @Maximo-Guk! - fix: Pages GitHub Deployment not triggeringv3.13.0Compare Source
Minor Changes
#325
cada7a6Thanks @Maximo-Guk! - Add GitHub deployments and job summaries for parity with pages-action#334
9fed19aThanks @Maximo-Guk! - Bump default wrangler version to 3.90.0v3.12.1Compare Source
Patch Changes
59c04629408d58978884fadd18755f1a15f96157Thanks @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.v3.12.0Compare Source
Minor Changes
122ee5cf5b66847e0b6cfa67ecd9e03e38a67a42Thanks @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.v3.11.0Compare Source
Minor Changes
10d5b9c1c1826adaec0a9ee49fdf5b91113508efThanks @Maximo-Guk! - Revert "Add parity with pages-action for pages deploy outputs"v3.10.0Compare Source
Minor Changes
3ec7f8943ef83351f743cfaa8763a9056ef70993Thanks @courtney-sims! - Support id, environment, url, and alias outputs for Pages deploys.v3.9.0Compare Source
Minor Changes
134b5c2a3252d66b8c4d1cddd0b9baaeed6a4daaThanks @Maximo-Guk! - Update wrangler version from 3.13.2 to 3.78.10Patch Changes
47d51f25c113ee9205110728599b43ed6a1e273bThanks @acusti! - fix: Detect existing wrangler install even when wrangler version output is multilinev3.8.0Compare Source
Minor Changes
a1467a0c8f2a058f8d43a4d0c40a55176ed5efe6Thanks @Ambroos! - Addsdeployment-alias-urloutput for Pages deployment aliases (since Wrangler v3.78.0): cloudflare/workers-sdk#6643v3.7.0Compare Source
Minor Changes
66efca2cbb82a5a49df6af2e14c4b58d53b0e266Thanks @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 presentv3.6.1Compare Source
Patch Changes
2d275a8f2d279dc91912c1ff8023af109ef3280cThanks @Maximo-Guk! - Reverts #235 which may have caused the latest version of wrangler to be installed, if no wrangler version was foundv3.6.0Compare Source
Minor Changes
0545ad285acaff2b92053d636ee17fb303b4c5f5Thanks @AdiRishi! - wrangler-action will now re-use existing wrangler installations when availablev3.5.0Compare Source
Minor Changes
#255
31a6263ef3ec73ff2d03cb4c0260379f96f7598cThanks @matthewdavidrodgers! - Stop racing secret uploadsFor 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.1Compare Source
Patch Changes
bbedd8e54f256d36f81f81f1f05b90937d533bb7Thanks @AdiRishi! - Surface inner exception when secret:bulk upload command failsv3.4.0Compare Source
Minor Changes
#213
d13856dfc92816473ebf47f66e263a2668a97896Thanks @GrantBirki! - This change introduces three new GitHub Actions output variables. These variables are as follows:command-output- contains the string results ofstdoutcommand-stderr- contains the string results ofstderrdeployment-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
9aba9c34daabca23a88191a5fe1b81fa721c1f11Thanks @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 than3.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.0was being considered less than3.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.2Compare Source
Patch Changes
#171
76d614fThanks @1000hz! - Fixed issues that caused the action to fail if any secret or var values contained shell metacharacters.#171
473d9cbThanks @1000hz! - BumpedDEFAULT_WRANGLER_VERSIONto 3.13.2v3.3.1Compare Source
Patch Changes
a4509d5Thanks @1000hz! - Fixed the package manager not being inferred based on lockfile when thepackageManagerinput isn't set.v3.3.0Compare Source
Minor Changes
d9a0a00Thanks @simpleauthority! - Added support for Bun as a package managerv3.2.1Compare Source
Patch Changes
528687aThanks @1000hz! - Fixed action failure when nopackageManagerspecified and no lockfile is found. The action now falls back to using npm.v3.2.0Compare Source
Minor Changes
#166
7d7b988Thanks @nix6839! - Support for package managers other than npm, such as pnpm and yarn.fixes #156
v3.1.1Compare Source
Patch Changes
e5251dfThanks @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.0Compare Source
Minor Changes
#154
3f40637Thanks @JacobMGEvans! - feat: Quiet modeSome 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
4132892Thanks @EstebanBorai! - use[email protected]by defaultv3.0.2Compare Source
Patch Changes
#147
58f274bThanks @JacobMGEvans! - Added more error logging when a command fails to executePreviously, 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
58f274bThanks @JacobMGEvans! - Adding ChangesetsVersion 3.0.0
Version 2.0.0
v3.0.1Compare Source
Automating Build & Release
What's Changed
.mjsNew Contributors
Full Changelog: cloudflare/wrangler-action@3.0.0...3.0.1
v3.0.0Compare Source
Additions
commandinput to allow running multiple Wrangler commands.Removals
Changes
Breaking changes
Additional Notes
Configuration
📅 Schedule: Branch creation - "on the first day of the month" (UTC), 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.
This PR was generated by Mend Renovate. View the repository job log.