Skip to content

chore(deps): update all patch dependencies - #474

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/all-patch
Aug 18, 2026
Merged

chore(deps): update all patch dependencies#474
renovate[bot] merged 1 commit into
mainfrom
renovate/all-patch

Conversation

@renovate

@renovate renovate Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change Age Confidence
Swatinem/rust-cache action patch v2.9.1v2.9.2 age confidence
actions/checkout action patch v7.0.0v7.0.1 age confidence
jdx/mise-action action patch v4.2.1v4.2.5 age confidence
one-way-git-sync devDependencies patch 6.0.456.0.46 age confidence

Release Notes

Swatinem/rust-cache (Swatinem/rust-cache)

v2.9.2

Compare Source

What's Changed
New Contributors

Full Changelog: Swatinem/rust-cache@v2.9.1...v2.9.2

actions/checkout (actions/checkout)

v7.0.1

Compare Source

jdx/mise-action (jdx/mise-action)

v4.2.5: : Resilient mise downloads with automatic retries

Compare 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 curl or wget attempt, 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 color

Compare Source

A small patch release that fixes locking-support detection when workflows force colored output.

Fixed
Detect mise install --locked reliably under forced color (#​580 by @​scop)

When colored output was forced globally (for example via CLICOLOR_FORCE=1), ANSI escape codes in mise install --help prevented the action from matching --locked in 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=1 in its environment, which overrides CLICOLOR_FORCE and 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 propagation

Compare 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 PATH returned by mise env --json into GITHUB_ENV, which correctly prevented snapshotting the runner's environment into subsequent steps. However, that also dropped mise-produced PATH entries — tool shims, [env] _.path directories, 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 PATH and forwards those directories individually through GITHUB_PATH. This preserves mise's configured ordering, composes cleanly with PATH changes from other actions, and never persists the runner's full PATH through GITHUB_ENV. The dotenv fallback path (used with older mise versions) also strips PATH= lines and re-derives additions from mise env --json.

A new export_path input (default true) lets workflows keep regular env exports while opting out of PATH changes:

- uses: jdx/mise-action@v4
  with:
    export_path: false # keep env vars, skip mise PATH additions

Full Changelog: jdx/mise-action@v4.2.2...v4.2.3

v4.2.2: : Zstd tar fallback for older runners

Compare Source

A small patch release that fixes archive selection on runners with an older tar and corrects a stale default in the README.

Fixed
Verify tar supports Zstd before picking .tar.zst (#​569 by @​JackMyers001

The action previously chose the .tar.zst mise archive whenever zstd --version succeeded, then extracted it with tar --zstd. On RHEL 8-compatible runners that ship zstd 1.4.4 alongside GNU tar 1.30, the --zstd option isn't recognized and installation failed.

Detection now runs both checks:

zstd --version
tar --zstd --version

If either fails, the action falls back to the .tar.gz archive. No configuration change is required — existing workflows on affected runners just start working again. Fixes #​568.

Documentation
  • Update the cache_key_prefix example in the README to reflect the current default of mise-v1 (previously documented as mise-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.46

Compare Source

Bug Fixes

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

  • Branch creation
    • "after 5am on Saturday"
  • Automerge
    • At any time (no schedule defined)

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


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/all-patch branch 10 times, most recently from 1d3add2 to 6ee90c6 Compare July 30, 2026 02:53
@renovate
renovate Bot force-pushed the renovate/all-patch branch 10 times, most recently from dbf2807 to a863000 Compare August 8, 2026 05:07
@renovate
renovate Bot force-pushed the renovate/all-patch branch 5 times, most recently from 09bd2ae to 4a026d2 Compare August 17, 2026 21:27
@renovate
renovate Bot force-pushed the renovate/all-patch branch from 4a026d2 to cb604b8 Compare August 18, 2026 03:46
@renovate
renovate Bot merged commit 3a20ee2 into main Aug 18, 2026
2 checks passed
@renovate
renovate Bot deleted the renovate/all-patch branch August 18, 2026 12:01
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.

0 participants