chore(deps): update all patch dependencies - #474
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/all-patch
branch
10 times, most recently
from
July 30, 2026 02:53
1d3add2 to
6ee90c6
Compare
renovate
Bot
force-pushed
the
renovate/all-patch
branch
10 times, most recently
from
August 8, 2026 05:07
dbf2807 to
a863000
Compare
renovate
Bot
force-pushed
the
renovate/all-patch
branch
5 times, most recently
from
August 17, 2026 21:27
09bd2ae to
4a026d2
Compare
renovate
Bot
force-pushed
the
renovate/all-patch
branch
from
August 18, 2026 03:46
4a026d2 to
cb604b8
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
v2.9.1→v2.9.2v7.0.0→v7.0.1v4.2.1→v4.2.56.0.45→6.0.46Release Notes
Swatinem/rust-cache (Swatinem/rust-cache)
v2.9.2Compare Source
What's Changed
$CARGO_HOME/binon restore instead of relying oncargo installmetadata by @clechasseur in #325New Contributors
Full Changelog: Swatinem/rust-cache@v2.9.1...v2.9.2
actions/checkout (actions/checkout)
v7.0.1Compare Source
jdx/mise-action (jdx/mise-action)
v4.2.5: : Resilient mise downloads with automatic retriesCompare Source
A small patch release that makes setup more resilient to transient network failures when downloading mise.
Fixed
Retry mise downloads after transient failures (#597 by @jdx)
The download helpers previously made a single
curlorwgetattempt, so a transient GitHub release-asset HTTP or TLS failure would abort setup before mise or any user command could run (see #596).Downloads now run through a retry wrapper that makes up to five attempts with a 2s pause between failures, logging a warning on each retry. This applies consistently to binary, checksum, signature, and version fetches. Checksum and minisign verification still run only after a successful download — never inside the retry loop — so integrity guarantees are unchanged.
Full Changelog: jdx/mise-action@v4.2.4...v4.2.5
v4.2.4: : Reliable locking detection under forced colorCompare Source
A small patch release that fixes locking-support detection when workflows force colored output.
Fixed
Detect
mise install --lockedreliably under forced color (#580 by @scop)When colored output was forced globally (for example via
CLICOLOR_FORCE=1), ANSI escape codes inmise install --helpprevented the action from matching--lockedin the help text, so locking support was reported as unavailable even on versions of mise that supported it.The help probe now runs with
NO_COLOR=1in its environment, which overridesCLICOLOR_FORCEand guarantees plain-text output for the feature detection — regardless of the surrounding workflow's color settings.Full Changelog: jdx/mise-action@v4.2.3...v4.2.4
v4.2.3: : Restore mise PATH propagationCompare Source
A patch release that restores mise's PATH propagation to subsequent workflow steps — without reintroducing the full-PATH snapshot behavior that v4.2.1 fixed.
Fixed
Export mise PATH entries to subsequent steps (#575) by @jdx
v4.2.1 stopped exporting the complete
PATHreturned bymise env --jsonintoGITHUB_ENV, which correctly prevented snapshotting the runner's environment into subsequent steps. However, that also dropped mise-produced PATH entries — tool shims,[env] _.pathdirectories, and similar — that workflows relied on after the setup step. See #565.The action now computes only the prefix that mise prepended to the existing
PATHand forwards those directories individually throughGITHUB_PATH. This preserves mise's configured ordering, composes cleanly with PATH changes from other actions, and never persists the runner's fullPATHthroughGITHUB_ENV. The dotenv fallback path (used with older mise versions) also stripsPATH=lines and re-derives additions frommise env --json.A new
export_pathinput (defaulttrue) lets workflows keep regularenvexports while opting out of PATH changes:Full Changelog: jdx/mise-action@v4.2.2...v4.2.3
v4.2.2: : Zstd tar fallback for older runnersCompare Source
A small patch release that fixes archive selection on runners with an older
tarand corrects a stale default in the README.Fixed
Verify
tarsupports Zstd before picking.tar.zst(#569 by @JackMyers001The action previously chose the
.tar.zstmise archive wheneverzstd --versionsucceeded, then extracted it withtar --zstd. On RHEL 8-compatible runners that shipzstd1.4.4 alongside GNUtar1.30, the--zstdoption isn't recognized and installation failed.Detection now runs both checks:
If either fails, the action falls back to the
.tar.gzarchive. No configuration change is required — existing workflows on affected runners just start working again. Fixes #568.Documentation
cache_key_prefixexample in the README to reflect the current default ofmise-v1(previously documented asmise-v0) (#570 by @muzimuzhi).New Contributors
Full Changelog: jdx/mise-action@v4.2.1...v4.2.2
WillBooster/one-way-git-sync (one-way-git-sync)
v6.0.46Compare Source
Bug Fixes
Configuration
📅 Schedule: (in timezone Asia/Tokyo)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.