Skip to content

build(deps): bump jdx/mise-action from 5.1.1 to 5.2.8 - #50

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/jdx/mise-action-5.2.8
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/jdx/mise-action-5.2.8

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor

Bumps jdx/mise-action from 5.1.1 to 5.2.8.

Release notes

Sourced from jdx/mise-action's releases.

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

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

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

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

v5.2.6: Fix step hanging after a failed cache restore

The action now exits as soon as its work is done. Before this release, a cache restore that failed during the download could leave the step running for up to ten minutes after setup had finished.

Fixed

  • A failed cache restore no longer leaves the step hanging. If the mise cache download failed partway through, for example with getaddrinfo EAI_AGAIN, the action logged a warning, installed the tools and saved the cache, then stopped producing output. The step stayed in progress until the job was cancelled or a timer inside @actions/cacheactions/toolkit#2470Error objects now mark the step as failed with their message. Before, they caused an unhandled rejection. (#718 by @​jdx and @​kjanat, fixes #717)

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

v5.2.5: Bundled packslip verifier updated to 1.11.0; README examples use v5

This release updates the packslip library that the action uses to verify downloaded mise releases, and updates the README examples to use the current major versions.

... (truncated)

Changelog

Sourced from jdx/mise-action's changelog.

Changelog


5.2.9 - 2026-11-14

🐛 Bug Fixes


5.2.8 - 2026-11-12

🐛 Bug Fixes

  • (windows) install mise when MISE_DATA_DIR is on another drive (#732) by @​jdx in #732

5.2.7 - 2026-11-06

🐛 Bug Fixes

  • retry transient download failures with backoff and report the HTTP status (#722) by @​jdx in #722

5.2.6 - 2026-11-02

🐛 Bug Fixes

  • exit after run and post so a failed cache restore can't hang the step (#718) by @​jdx in #718

5.2.5 - 2026-10-31

🔍 Other Changes


5.2.4 - 2026-10-27

🐛 Bug Fixes

  • (cache) reuse signed checksums saved with a cached mise (#708) by @​jdx in #708

5.2.3 - 2026-10-24

🐛 Bug Fixes

  • (cache) hash mise config files without walking the workspace (#703) by @​jdx in #703

... (truncated)

Commits
  • d5574b5 chore: release v5.2.8 (#733)
  • cff84f4 fix(windows): install mise when MISE_DATA_DIR is on another drive (#732)
  • 72890a1 chore(deps): lock file maintenance (#729)
  • b44d12e chore: release v5.2.7 (#723)
  • 95feee8 fix(deps): update dependency packslip to v1.11.2 (#726)
  • 7dd01dc chore(deps): update jdx/mise-action action to v5.2.4 (#725)
  • ba4db83 chore(deps): update dependency hk to latest (#724)
  • 382c35d fix: retry transient download failures with backoff and report the HTTP statu...
  • f5be966 chore: release v5.2.6 (#719)
  • 2187bd8 chore(deps): lock file maintenance (#720)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [jdx/mise-action](https://github.com/jdx/mise-action) from 5.1.1 to 5.2.8.
- [Release notes](https://github.com/jdx/mise-action/releases)
- [Changelog](https://github.com/jdx/mise-action/blob/main/CHANGELOG.md)
- [Commits](jdx/mise-action@2d8d4ca...d5574b5)

---
updated-dependencies:
- dependency-name: jdx/mise-action
  dependency-version: 5.2.8
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants