[renovate]

This PR contains the following updates:

Package	Type	Update	Change
jdx/mise-action	action	patch	v5.2.6 → v5.2.8

---

Release Notes

jdx/mise-action

v5.2.8: : Fix mise install on Windows when MISE_DATA_DIR is on another drive

Compare Source

On Windows, the action can now install mise when MISE_DATA_DIR is on a different drive from the temporary directory. Before this fix, the install failed with EXDEV: cross-device link not permitted.

Fixed

• Installing mise on Windows no longer fails when MISE_DATA_DIR is on another drive. On hosted windows-2025 runners, the workspace and RUNNER_TEMP are on D:, but the action downloaded mise to os.tmpdir() on C:. If MISE_DATA_DIR pointed into the workspace, moving mise.exe into place failed:

  ##[error]EXDEV: cross-device link not permitted, rename 'C:\Users\RUNNER~1\AppData\Local\Temp\mise-action-…\extract\mise\bin\mise.exe' -> 'D:\a\…\tool-cache\mise\bin\mise.exe'
  

  The action now downloads to RUNNER_TEMP when that variable is set and the directory exists. Otherwise it falls back to the system temp directory. If moving mise.exe, mise-shim.exe or a raw mise binary still crosses drives, the action copies the file and then deletes the original. This also covers self-hosted runners where RUNNER_TEMP is on a different drive from the data directory. Setups that use the default data directory were not affected. If you set TEMP and TMP to ${{ runner.temp }} to work around this, you can remove those settings. (#​732 by @​jdx and @​HengYangDS, fixes #​730)

New Contributors

• @​HengYangDS made their first contribution in cff84f4

Full Changelog: jdx/mise-action@v5.2.7...v5.2.8

v5.2.7: : Retry failed mise downloads with backoff and show the HTTP status

Compare Source

When the action can't download mise, the log now shows the HTTP status and host for each failed attempt. Retries wait longer between attempts, so a short GitHub outage is less likely to fail the job.

Fixed

• Download failures now show what went wrong, and brief outages are retried for longer. Before this release, a failed mise download logged only The process '/usr/bin/curl' failed with exit code 22 and retried five times with a fixed 2-second wait. From that message you couldn't tell a rate limit from a missing asset or a server error. Each failed attempt now logs the HTTP status and the host that answered:

  Download attempt 1/6 failed: Could not download github.com/…/mise-v2026.10.21-linux-x64.tar.zst (HTTP 503 from github.com). Retrying in 3.4 seconds.
  

  The wait between attempts doubles from about 2s up to a 30s cap, with random jitter, so the five retries cover roughly a minute. Only transient failures are retried: connection errors and timeouts, and HTTP 408, 429 and 5xx responses. A 404, any other 4xx, or a local file-write error fails at once. The log shows only the host and file name of each URL, never signed query strings or curl/wget stderr. Partial files are deleted before the next attempt. wget now runs with --tries=1, so its own 20-retry default no longer stacks on top of the action's retries. This applies to every download the action makes: the release archive, checksums and the packslip bundle. Checksum and signature verification are unchanged, and there are no new inputs. (#​722 by @​jdx, fixes #​721)

Changed

• packslip, which the action uses to verify downloaded mise releases, is updated from 1.11.0 to 1.11.2. This version includes upstream hardening of its verifier checks. (#​726)

Full Changelog: jdx/mise-action@v5.2.6...v5.2.7

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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 was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 66%. Comparing base (a6fc3b5) to head (b9e8c1c).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@         Coverage Diff          @@
##           main   #1775   +/-   ##
====================================
  Coverage    66%     66%           
====================================
  Files        23      23           
  Lines      3565    3565           
====================================
  Hits       2355    2355           
  Misses     1210    1210           

Flag	Coverage Δ
examples	39% <ø> (ø)
tests	65% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.