[dependabot]

Bumps jdx/mise-action from 5.2.2 to 5.2.4.

Release notes

Sourced from jdx/mise-action's releases.

v5.2.4: Reuse cached signed checksums when restoring mise

Jobs that restore mise from the cache no longer have to download its signed checksums from GitHub on every run, so a network failure at that step no longer fails a job that otherwise restored correctly.

Fixed

• Restoring a cached mise no longer needs a network download of the checksums. The action checks the cached mise binary against the signed SHASUMS256.txt and its .minisig. Before this release it downloaded both files from GitHub on every run, even when the cache restored correctly. When that download failed, for example after repeated curl errors, the job failed. Now, once the signature checks out, the action saves both files as SHASUMS256-<version>.txt and .minisig in <mise_dir>/bin, which is part of the mise cache. On later runs it reads them from the restored cache and checks the minisign signature again before using them. If the files are missing, corrupt or tampered with, the action downloads them as it did before. There are no new inputs. (#708 by @​jdx)
  • Caches saved by earlier versions don't contain these files. The main cache is only saved on a cache miss, so runs keep downloading the checksums until the cache is saved again or its key changes.

Full Changelog: jdx/mise-action@v5.2.3...v5.2.4

v5.2.3: Faster cache key computation in large workspaces

The cache key no longer comes from searching the whole workspace for mise config files. In repos that already contain node_modules or vendor/bundle, this removes a delay of several minutes in "Restoring mise cache".

Fixed

• "Restoring mise cache" no longer takes minutes after installing dependencies. To build the cache key, the action used to match about 25 **/… glob patterns. That meant it walked every subdirectory of the workspace, including node_modules and vendor/bundle, before checking the cache at all. When the action ran after a step like pnpm install or ruby/setup-ruby with bundler-cache: true, this could take 3–7 minutes. The action now looks for mise config files the same way mise does: only in the working directory and each parent directory up to the workspace root. It checks for mise.toml, .mise.toml, .config/mise/…, conf.d fragments, .tool-versions, and their local, env-specific and .lock variants. The step also logs Hashed mise config files in N.Ns. (#703 by @​jdx and @​corsicanec82)
  • If you set a custom cache_key that doesn't use {{file_hash}} or {{default}}, the action no longer hashes config files at all.
  • Config files in subdirectories, such as monorepo sub-projects, no longer affect the cache key. mise only loads them with --monorepo.
  • Cache keys change, so the first run after you upgrade will miss the cache.

New Contributors

• @​corsicanec82 made their first contribution in 91e7f82 (#703)

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

Changelog

Sourced from jdx/mise-action's changelog.

5.2.4 - 2026-10-26

🐛 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

---

Commits

• 6be3c7e chore: release v5.2.4 (#709)
• 40dafec fix(cache): reuse signed checksums saved with a cached mise (#708)
• ed63289 chore(deps): lock file maintenance (#707)
• 82a612c chore: release v5.2.3 (#704)
• 2d0418b chore(deps): update dependency hk to latest (#705)
• e891dde chore(deps): update jdx/mise-action action to v5.2.0 (#706)
• 91e7f82 fix(cache): hash mise config files without walking the workspace (#703)
• 9a35c22 chore(deps): update github actions (#701)
• See full diff in compare view

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)