-
Notifications
You must be signed in to change notification settings - Fork 0
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.12.1 #20
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/cloudflare-wrangler-action-3.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.2.0
chore(deps): update cloudflare/wrangler-action action to v3.2.1
Oct 10, 2023
renovate
bot
force-pushed
the
renovate/cloudflare-wrangler-action-3.x
branch
from
October 10, 2023 16:18
5eab43b
to
cc6852c
Compare
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.2.1
chore(deps): update cloudflare/wrangler-action action to v3.3.0
Oct 10, 2023
renovate
bot
force-pushed
the
renovate/cloudflare-wrangler-action-3.x
branch
from
October 10, 2023 21:35
cc6852c
to
66932ef
Compare
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.3.0
chore(deps): update cloudflare/wrangler-action action to v3.3.1
Oct 11, 2023
renovate
bot
force-pushed
the
renovate/cloudflare-wrangler-action-3.x
branch
from
October 11, 2023 16:43
66932ef
to
e43692d
Compare
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.3.1
chore(deps): update cloudflare/wrangler-action action to v3.3.2
Oct 24, 2023
renovate
bot
force-pushed
the
renovate/cloudflare-wrangler-action-3.x
branch
from
October 24, 2023 21:45
e43692d
to
d29ef18
Compare
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.3.2
chore(deps): update cloudflare/wrangler-action action to v3.4.0
Dec 19, 2023
renovate
bot
force-pushed
the
renovate/cloudflare-wrangler-action-3.x
branch
from
December 19, 2023 19:26
d29ef18
to
737f160
Compare
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.4.0
chore(deps): update cloudflare/wrangler-action action to v3.4.1
Jan 9, 2024
renovate
bot
force-pushed
the
renovate/cloudflare-wrangler-action-3.x
branch
from
January 9, 2024 19:17
737f160
to
34d2d88
Compare
renovate
bot
force-pushed
the
renovate/cloudflare-wrangler-action-3.x
branch
from
May 1, 2024 10:48
34d2d88
to
4197ef1
Compare
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.4.1
chore(deps): update cloudflare/wrangler-action action to v3.5.0
May 1, 2024
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.5.0
chore(deps): update cloudflare/wrangler-action action to v3.6.0
May 23, 2024
renovate
bot
force-pushed
the
renovate/cloudflare-wrangler-action-3.x
branch
2 times, most recently
from
May 24, 2024 15:57
2702120
to
e32f05a
Compare
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.6.0
chore(deps): update cloudflare/wrangler-action action to v3.6.1
May 24, 2024
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.6.1
chore(deps): update cloudflare/wrangler-action action to v3.7.0
Jul 2, 2024
renovate
bot
force-pushed
the
renovate/cloudflare-wrangler-action-3.x
branch
from
July 2, 2024 16:15
e32f05a
to
3ec5a99
Compare
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.7.0
chore(deps): update cloudflare/wrangler-action action to v3.8.0
Oct 2, 2024
renovate
bot
force-pushed
the
renovate/cloudflare-wrangler-action-3.x
branch
2 times, most recently
from
October 8, 2024 19:35
c9489eb
to
e8a7078
Compare
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.8.0
chore(deps): update cloudflare/wrangler-action action to v3.9.0
Oct 8, 2024
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.9.0
chore(deps): update cloudflare/wrangler-action action to v3.10.0
Oct 23, 2024
renovate
bot
force-pushed
the
renovate/cloudflare-wrangler-action-3.x
branch
from
October 23, 2024 23:03
e8a7078
to
e887156
Compare
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.10.0
chore(deps): update cloudflare/wrangler-action action to v3.11.0
Oct 24, 2024
renovate
bot
force-pushed
the
renovate/cloudflare-wrangler-action-3.x
branch
from
October 24, 2024 16:48
e887156
to
9a684c1
Compare
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.11.0
chore(deps): update cloudflare/wrangler-action action to v3.12.0
Nov 4, 2024
renovate
bot
force-pushed
the
renovate/cloudflare-wrangler-action-3.x
branch
from
November 4, 2024 16:29
9a684c1
to
698c0f8
Compare
renovate
bot
changed the title
chore(deps): update cloudflare/wrangler-action action to v3.12.0
chore(deps): update cloudflare/wrangler-action action to v3.12.1
Nov 6, 2024
renovate
bot
force-pushed
the
renovate/cloudflare-wrangler-action-3.x
branch
from
November 6, 2024 19:41
698c0f8
to
aee04b9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
v3.1.1
->v3.12.1
Release Notes
cloudflare/wrangler-action (cloudflare/wrangler-action)
v3.12.1
Compare Source
Patch Changes
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.v3.12.0
Compare Source
Minor Changes
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.v3.11.0
Compare Source
Minor Changes
10d5b9c1c1826adaec0a9ee49fdf5b91113508ef
Thanks @Maximo-Guk! - Revert "Add parity with pages-action for pages deploy outputs"v3.10.0
Compare Source
Minor Changes
3ec7f8943ef83351f743cfaa8763a9056ef70993
Thanks @courtney-sims! - Support id, environment, url, and alias outputs for Pages deploys.v3.9.0
Compare Source
Minor Changes
134b5c2a3252d66b8c4d1cddd0b9baaeed6a4daa
Thanks @Maximo-Guk! - Update wrangler version from 3.13.2 to 3.78.10Patch Changes
47d51f25c113ee9205110728599b43ed6a1e273b
Thanks @acusti! - fix: Detect existing wrangler install even when wrangler version output is multilinev3.8.0
Compare Source
Minor Changes
a1467a0c8f2a058f8d43a4d0c40a55176ed5efe6
Thanks @Ambroos! - Addsdeployment-alias-url
output for Pages deployment aliases (since Wrangler v3.78.0): cloudflare/workers-sdk#6643v3.7.0
Compare Source
Minor Changes
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 presentv3.6.1
Compare Source
Patch Changes
2d275a8f2d279dc91912c1ff8023af109ef3280c
Thanks @Maximo-Guk! - Reverts #235 which may have caused the latest version of wrangler to be installed, if no wrangler version was foundv3.6.0
Compare Source
Minor Changes
0545ad285acaff2b92053d636ee17fb303b4c5f5
Thanks @AdiRishi! - wrangler-action will now re-use existing wrangler installations when availablev3.5.0
Compare Source
Minor Changes
#255
31a6263ef3ec73ff2d03cb4c0260379f96f7598c
Thanks @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.1
Compare Source
Patch Changes
bbedd8e54f256d36f81f81f1f05b90937d533bb7
Thanks @AdiRishi! - Surface inner exception when secret:bulk upload command failsv3.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 ofstdout
command-stderr
- contains the string results ofstderr
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 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.0
was 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.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! - BumpedDEFAULT_WRANGLER_VERSION
to 3.13.2v3.3.1
Compare Source
Patch Changes
a4509d5
Thanks @1000hz! - Fixed the package manager not being inferred based on lockfile when thepackageManager
input isn't set.v3.3.0
Compare Source
Minor Changes
d9a0a00
Thanks @simpleauthority! - Added support for Bun as a package managerv3.2.1
Compare Source
Patch Changes
528687a
Thanks @1000hz! - Fixed action failure when nopackageManager
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
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 is behind base branch, 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.