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)
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/cache fired after 10 minutes. That timer is left running when a download fails (actions/toolkit#2470), and it kept the Node process alive. The action now exits explicitly after both the main step and the post step finish. It waits up to 5 seconds for log output to flush, then exits. The exit code set by any earlier failure is kept. Errors that aren't Error objects now mark the step as failed with their message. Before, they caused an unhandled rejection. (#718 by @jdx and @kjanat, fixes #717)
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.
Changed
packslip updated from 1.8.0 to 1.11.0. The action uses packslip to check a downloaded mise binary against the signed packslip.sigstore.json that ships with mise releases from 2026.9.3 onward. The new version runs extra checks on the signed statement: the identity it declares must match the certificate that signed it, and the certificate must belong to the github.com/jdx/mise repository. GitHub and GitLab repository names now match regardless of letter case. The action still asks for the same identity, issuer and tag as before, and there are no new inputs. (#715)
The README examples now use jdx/mise-action@v5 and actions/checkout@v7. (#710 by @deining)
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.
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.
The cache key now includes mise conf.d/*.toml config fragments, so changing one of them invalidates the cache.
Fixed
Editing a conf.d fragment now invalidates the cache. mise can load config from single-file fragments in conf.d/ directories, but the action didn't hash those files when it built the cache key. As a result, adding or changing tools in a fragment could restore an outdated cache. The cache key now also hashes conf.d/*.toml files under .config/mise/, .mise/ and mise/. If your repo already uses these fragments, the cache will miss once after you upgrade. (#698 by @rileymichael)
The action now refuses to install mise 2026.9.3 or later if the release's signed packslip is missing. This closes a gap where verification could be downgraded to the weaker checksum check.
Fixed
A missing packslip no longer weakens the check on recent mise releases. v5.2.0 started checking the mise binary against the release's signed packslip.sigstore.json. If that file wasn't found, though, the action quietly fell back to the minisign-signed SHASUMS256 checksums. Anyone who could hide the file could force the weaker check. Every mise release from 2026.9.3 on includes a packslip, so for those versions a missing bundle now stops the install with an error like this:
mise v2026.10.11 must ship a signed packslip, but https://github.com/jdx/mise/releases/download/v2026.10.11/packslip.sigstore.json was not found
Releases before 2026.9.3 don't include a packslip, so they're still checked against the signed checksums. A version string that isn't three dot-separated numbers also requires a packslip. If you set the sha256 input, it still takes precedence over both checks. A packslip that fails verification still never falls back to the checksums. (#695 by @jdx)
The default cache key now rolls over every 30 days, so long-lived caches pick up newer mise releases. The action also checks the downloaded mise binary against the release's signed packslip, and it runs mise install --monorepo automatically in monorepos. Existing caches miss once after you upgrade, because the default cache key format has changed.
Added
The cache is rebuilt every 30 days by default. GitHub never evicts a cache that keeps getting hits. Before this release, an active repo could keep the same mise binary and tools for months, until a config file changed. The default cache key now includes a period suffix (-p<N>), so the cache is rebuilt from scratch at least once per period. All repos roll over on the same calendar boundary. Use the new cache_max_age_days input to change the period, or set it to 0 to keep the old key that never expires. Custom cache_key templates can use the new {{cache_period}} variable, which {{default}} already includes. A custom key that doesn't use it behaves as before. On self-hosted runners that keep mise data between runs, you may also need auto_update: true to pick up a newer mise. (#689 by @jdx, fixes #688)
Throttled cache restores and saves can be retried. Before this release, when GitHub's cache service returned HTTP 429, the action gave up right away: a restore counted as a miss and a save was skipped. The new cache_restore_retry_budget and cache_save_retry_budget inputs set how long the action may wait. Each retry waits for the Retry-After value plus some random jitter. Once the budget runs out, the action falls back to the old behavior. Retries apply to the main cache, the post-step save and the binary cache. Real cache misses and reservation conflicts are never retried. Both budgets default to 0s (no retries). @actions/cache doesn't report 429 errors directly, so the action detects throttling from its warning messages. If those messages change in a future @actions/cache release, throttling won't be detected and nothing will be retried. (#692 by @jdx, fixes #691)
The latest mise binary can fall back to a second download source. When the action downloads the latest mise version, it can fall back between GitHub and mise.jdx.dev if the first source fails. The fetch_from_github setting decides which source it tries first. Pinned versions and minimum_release_age installs are only downloaded from GitHub. The binary is still checked against the signed checksums for the resolved version, whichever source it came from. (#692 by @jdx)
The mise binary is checked against its signed packslip. If a mise release includes packslip.sigstore.json, the action checks the downloaded binary against it. The bundle must be signed by mise's release workflow for that exact tag. After a successful check, the log shows Verified <asset> against the signed packslip. If the check fails, the install stops instead of falling back to a weaker check. Releases without a packslip use the existing minisign and SHASUMS256 check. An explicit sha256 input still takes precedence. (#693 by @jdx)
Monorepo-aware installs. If your mise config sets [monorepo].config_roots, the action now adds --monorepo to mise install, so tools configured anywhere in the monorepo get installed. Repos without that setting aren't affected. To opt out, set monorepo: false. (#679 by @zeitlinger)
Fixed
Tool directories that mise moves to the front of PATH are now exported. The action used to find mise's PATH changes by comparing mise's PATH with the runner's. If a tool's bin directory was already on the runner's PATH, such as ~/.cargo/bin, mise only moved it to the front, so the action didn't export it. Later steps then found the mise shim first. For example, rustup resolved to the shim instead of ~/.cargo/bin/rustup. The action now asks mise for its entries with mise env --paths and exports them in the order mise reports. This fix needs a mise version that supports --paths. With older versions, the action uses the old comparison. (#685 by @jdx)
Documentation
The new "Release workflows" section of the README says that jobs that publish releases shouldn't restore caches. A lower-trust workflow that can write to default-branch caches could otherwise slip files into a release. In those jobs, use cache: false or GitHub's cache-mode: none. (#682 by @jdx)
The README explains how to cache mise's downloads, keyed on mise.lock, instead of installed tools. It includes a Windows example that sets MISE_CACHE_DIR from ${{ runner.temp }}, because actions/cache doesn't expand %TEMP%. (#686, #690 by @zeitlinger)
Breaking Changes
The default cache key has a new format, so the first run after upgrading is a cache miss and saves a fresh cache. After that, the cache is rebuilt every 30 days by default. To keep the old cache key that never expires, set cache_max_age_days: 0. Workflows that set a custom cache_key without {{default}} or {{cache_period}} aren't affected.
The mise_dir input now also sets where mise installs tools, so those tools end up in the cache. With auto_update: true, the action no longer crashes on Windows when the mise binary is still in use.
Fixed
mise_dir now exports MISE_DATA_DIR. Before this release, mise_dir moved the mise binary and the cache path, but mise kept installing tools to ~/.local/share/mise. The saved cache didn't include the tools. On runners where ~/.local isn't writable, the step failed with EACCES: permission denied. When mise_dir is set, the action now exports MISE_DATA_DIR=<mise_dir>, so tools are installed into the directory that gets cached. If your workflow sets a different MISE_DATA_DIR, the mise_dir input overrides it. If mise_dir isn't set, nothing changes. mise's state directory (~/.local/state/mise) stays where it is. If that path also can't be written, set MISE_STATE_DIR yourself. (#672 by @jdx, fixes #668)
auto_update no longer crashes when it can't replace mise.exe. On Windows, the step used to fail with a bare EPERM: operation not permitted, unlink '…\mise.exe' if another process was still using the binary. Now, if version isn't pinned and the existing binary passes verification against its recorded version, the action prints a warning and continues with that version. In any other case, the step fails with a message that says the file is in use and how to fix it. A pinned version never quietly keeps an older binary. (#665 by @jdx, fixes #664)
Documentation
The README explains how to use mise's MISE_ENABLE_TOOLS setting as a job-level allowlist. Unlike install_args, the allowlist applies to the action's install and to later mise commands. If jobs use different allowlists, add the value to a custom cache_key. (#667 by @zeitlinger)
The Rust cache section is updated for mise 2026.9.2 and later, where mise install repairs a restored toolchain instead of leaving rustfmt missing. Swatinem/rust-cache now works alongside mise-managed Rust. (#670 by @jdx)
mise-action no longer exports its GitHub token as MISE_GITHUB_TOKEN to every later step in the job. A new persist_github_token input lets you turn that back on, or pass a different token to later steps. This changes the default behavior. If later steps need the token, see Breaking Changes below.
Fixed
The GitHub token now stays inside the action by default. Before this release, the github_token input (which defaults to ${{ github.token }}) was written to GITHUB_ENV as MISE_GITHUB_TOKEN. That let any later step read the token and call the GitHub API with the job's permissions, even if the step never asked for a credential. Now the token is set only for the mise-action step and the processes it starts. The action masks the token in logs. (#658 by @jdx, reported in #657)
Added
persist_github_token input (default false). It takes one of three values:
false: the token stays inside the action.
true: the token the action used is exported to later steps. If env.MISE_GITHUB_TOKEN is already set, it takes precedence over github_token.
A token value: that token is exported to later steps instead, for example a read-only token. The action still installs tools with github_token, or with MISE_GITHUB_TOKEN if it's already set.
Setting false doesn't clear a MISE_GITHUB_TOKEN that was already set at the job level or exported by an earlier step. (#658 by @jdx)
Breaking Changes
Check your workflow if a later step needs MISE_GITHUB_TOKEN, such as mise shims, mise exec, mise run or lazy tool installs that call the GitHub API. Those steps no longer get the token automatically and may hit GitHub API rate limits. To get the old behavior back, opt in:
mise-action now reports the tool versions it installed as step outputs, can install mise plugins before tools, and can save the cache at the end of the job. Several caching fixes stop the action from downloading mise again on every run.
Added
Tool versions as step outputs. After install, the action runs mise ls --json --current and sets a versions output. This is a JSON object of the active, installed tools. Each tool maps to a list of {version, requested_version, install_path, source} entries. Each tool also gets its own output with its resolved version, such as steps.mise.outputs.node. A tool only gets its own output if its name is a valid output name and isn't cache-hit or versions. Names like npm:@scope/pkg appear only in versions. If the action can't read the versions, it prints a warning and the step still succeeds. (#655 by @jdx)
plugins input. List plugins one per line as name or name url. Blank lines and # comments are ignored. The action runs mise plugins install -y for each one before mise install. Plugins that are already installed, for example restored from the cache, are left as they are. An unknown plugin fails the step. When plugins is set, its hash is added to the default cache key. Custom cache_key templates can use it as {{plugins_hash}}. If plugins is unset, existing cache keys don't change. (#656 by @jdx)
- uses:jdx/mise-action@v5env:# needed for idiomatic files such as .yvmrcMISE_IDIOMATIC_VERSION_FILE_ENABLE_TOOLS:yarnwith:plugins:| yarn
php https://github.com/verzly/mise-php#latest
cache_save_post input (opt-in, default false). When enabled, the mise cache is saved in the action's post step instead of right after install. This way, tools installed by later steps are included in the cache, for example from monorepo sub-project configs or task-level tools. The setting only applies on a cache miss, because an existing cache entry can't be overwritten. The post step runs even if a later step fails. If the post-step save fails, the action prints a warning and the job doesn't fail. (#649 by @jdx)
auto_update input (default false). See Changed below. (#642 by @jdx)
The action now warns when you use the mise_toml input and a .mise.toml already exists in the working directory. mise loads .mise.toml before the mise.toml the action writes, so the input may have no effect. (#654 by @jdx)
Changed
A cached mise is kept when version is unset. Before, each new mise release made the action reject the cached binary in integrity verification and download mise again on every run until the cache key changed. Now the cached binary is kept until the cache key changes. The action verifies it against the signed checksums of the version recorded at install, without running it first. Caches saved before this release have no version record, so they are still verified against the latest release, and a tampered binary is still replaced. The integrity warning now includes the underlying error. To keep updating to newer releases as before, set auto_update: true. Each updated binary is cached under its own mise version, so each release is downloaded only once. An explicit version input works the same as before. (#642 by @jdx)
Fixed
The cache is saved after a partial-match restore. When the cache was restored from a key that only matched the prefix, the action never saved under the primary key, so it rebuilt the same tools on every run. Exact cache hits still skip the save. (#646 by @jdx)
Caches saved before this release no longer cause a download on every run. These caches have no version record, so a cached binary is verified against the latest release. Once a newer mise shipped, the action downloaded mise again on every run. It now also saves the reinstalled binary in a cache keyed by mise version, so later runs restore that binary instead of downloading it. (#648 by @jdx)
Windows: mise installs without unzip. The mise zip is now extracted with PowerShell's Expand-Archive. Self-hosted Windows runners that don't have unzip, such as fresh Windows 11 arm64 machines, can now install mise. (#650 by @jdx)
Documentation
New README guides cover matrix builds, using another cache action, and Rust caching:
Matrix builds: use MISE_<TOOL>_VERSION overrides and give each matrix entry its own cache_key.
Other cache actions: set cache: false and cache mise's data directory yourself.
Rust: explains why a restored cache can be missing Rust components such as rustfmt, with two workarounds. (#654, #651 by @jdx)
mise-action now checks the integrity of an already-installed mise binary before running it. This fixes a security issue that was reported privately.
Fixed
An existing mise binary is verified before it is run. When a mise binary is already on the runner (for example, restored from cache or in mise_dir), the action now checks it before calling it. If you set a sha256 input, the binary must match that checksum and report the requested version. Otherwise, it must match the signed release checksums for the version being installed. If the check fails, the action prints a warning, deletes the binary and installs the requested release again. Before this fix, the action could run a cached binary before checking it. (#637 by @jdx)
Changed
Changes to how the action handles an existing binary, also from #637:
Switching versions uses a full install. If the cached binary doesn't match the requested version, the action downloads and installs that version. It no longer runs mise self-update.
Unpinned runs always pick a release. Without a version input, the action now selects a release every time, using minimum_release_age, even when mise is already installed. It then checks the existing binary against that release, and reinstalls if the binary doesn't match.
Older releases need a sha256 input to reuse a cached binary. Some older mise releases have no signed checksums. With the sha256 input set, a cached binary of one of these releases can still be reused without a download. Without it, the action can't verify the binary and installs it again.
If you don't pin a version, mise-action now installs the newest stable mise release that is at least 24 hours old. Upgrading mise on a runner that already has it is also less likely to hit GitHub API rate limits.
Breaking Changes
minimum_release_age now defaults to 24h (#632 by @jdx)
Before this release, minimum_release_age was an opt-in setting. It now defaults to 24h. If you don't set version, the action picks the highest-numbered stable mise release published at least 24 hours ago. A mise release that just shipped won't be installed until it's a day old.
To get the latest stable release right away, as in v4, set the delay to 0s. You can also choose a longer delay:
- uses:jdx/mise-action@v5with:minimum_release_age:0s # or e.g. 7d
An explicit version input still takes precedence and skips the delay.
The setting applies only to the mise binary, not to tools installed by mise.
The action now gets the release list from a public CDN index (releases.tsv on mise.jdx.dev) instead of paging through the GitHub Releases API. Picking a release doesn't use GitHub API quota, even when an installed binary is reused. If the index is missing or malformed, the action fails instead of skipping the release-age check.
Replacing an older installed binary still runs mise self-update, which may call the GitHub API to fetch that exact release.
Fixed
mise self-update now runs with MISE_GITHUB_TOKEN. When a runner already had a different mise version installed, the action runs mise self-update to switch versions. That GitHub API call used to go out without authentication, so busy shared or self-hosted runners could hit the rate limit and fail with HTTP 403 RateLimitedError. If you already set a token in your environment, the action leaves it unchanged. (#619 by @hegde5)
This PR contains the following updates:
| Package | Type | Update | Change | Pending |
|---|---|---|---|---|
| [https://github.com/jdx/mise-action](https://github.com/jdx/mise-action) | action | major | `v4.3.0` → `v5.2.7` | `v5.2.8` |
---
### Release Notes
<details>
<summary>jdx/mise-action (https://github.com/jdx/mise-action)</summary>
### [`v5.2.7`](https://github.com/jdx/mise-action/releases/tag/v5.2.7): : Retry failed mise downloads with backoff and show the HTTP status
[Compare Source](https://github.com/jdx/mise-action/compare/v5.2.6...v5.2.7)
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:
```text
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](https://github.com/jdx/mise-action/pull/722) by [@​jdx](https://github.com/jdx), fixes [#​721](https://github.com/jdx/mise-action/issues/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](https://github.com/jdx/mise-action/pull/726))
**Full Changelog**: <https://github.com/jdx/mise-action/compare/v5.2.6...v5.2.7>
### [`v5.2.6`](https://github.com/jdx/mise-action/releases/tag/v5.2.6): : Fix step hanging after a failed cache restore
[Compare Source](https://github.com/jdx/mise-action/compare/v5.2.5...v5.2.6)
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/cache` fired after 10 minutes. That timer is left running when a download fails ([actions/toolkit#2470](https://github.com/actions/toolkit/issues/2470)), and it kept the Node process alive. The action now exits explicitly after both the main step and the post step finish. It waits up to 5 seconds for log output to flush, then exits. The exit code set by any earlier failure is kept. Errors that aren't `Error` objects now mark the step as failed with their message. Before, they caused an unhandled rejection. ([#​718](https://github.com/jdx/mise-action/pull/718) by [@​jdx](https://github.com/jdx) and [@​kjanat](https://github.com/kjanat), fixes [#​717](https://github.com/jdx/mise-action/issues/717))
**Full Changelog**: <https://github.com/jdx/mise-action/compare/v5.2.5...v5.2.6>
### [`v5.2.5`](https://github.com/jdx/mise-action/releases/tag/v5.2.5): : Bundled packslip verifier updated to 1.11.0; README examples use v5
[Compare Source](https://github.com/jdx/mise-action/compare/v5.2.4...v5.2.5)
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.
#### Changed
- **packslip updated from 1.8.0 to 1.11.0.** The action uses packslip to check a downloaded mise binary against the signed `packslip.sigstore.json` that ships with mise releases from 2026.9.3 onward. The new version runs extra checks on the signed statement: the identity it declares must match the certificate that signed it, and the certificate must belong to the `github.com/jdx/mise` repository. GitHub and GitLab repository names now match regardless of letter case. The action still asks for the same identity, issuer and tag as before, and there are no new inputs. ([#​715](https://github.com/jdx/mise-action/pull/715))
- The README examples now use `jdx/mise-action@v5` and `actions/checkout@v7`. ([#​710](https://github.com/jdx/mise-action/pull/710) by [@​deining](https://github.com/deining))
**Full Changelog**: <https://github.com/jdx/mise-action/compare/v5.2.4...v5.2.5>
### [`v5.2.4`](https://github.com/jdx/mise-action/releases/tag/v5.2.4): : Reuse cached signed checksums when restoring mise
[Compare Source](https://github.com/jdx/mise-action/compare/v5.2.3...v5.2.4)
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](https://github.com/jdx/mise-action/pull/708) by [@​jdx](https://github.com/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**: <https://github.com/jdx/mise-action/compare/v5.2.3...v5.2.4>
### [`v5.2.3`](https://github.com/jdx/mise-action/releases/tag/v5.2.3): : Faster cache key computation in large workspaces
[Compare Source](https://github.com/jdx/mise-action/compare/v5.2.2...v5.2.3)
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](https://github.com/jdx/mise-action/pull/703) by [@​jdx](https://github.com/jdx) and [@​corsicanec82](https://github.com/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](https://github.com/corsicanec82) made their first contribution in [91e7f82](https://github.com/jdx/mise-action/commit/91e7f82) ([#​703](https://github.com/jdx/mise-action/issues/703))
**Full Changelog**: <https://github.com/jdx/mise-action/compare/v5.2.2...v5.2.3>
### [`v5.2.2`](https://github.com/jdx/mise-action/releases/tag/v5.2.2): : Include conf.d config fragments in the cache key
[Compare Source](https://github.com/jdx/mise-action/compare/v5.2.1...v5.2.2)
The cache key now includes mise `conf.d/*.toml` config fragments, so changing one of them invalidates the cache.
#### Fixed
- **Editing a `conf.d` fragment now invalidates the cache.** mise can load config from single-file fragments in `conf.d/` directories, but the action didn't hash those files when it built the cache key. As a result, adding or changing tools in a fragment could restore an outdated cache. The cache key now also hashes `conf.d/*.toml` files under `.config/mise/`, `.mise/` and `mise/`. If your repo already uses these fragments, the cache will miss once after you upgrade. ([#​698](https://github.com/jdx/mise-action/pull/698) by [@​rileymichael](https://github.com/rileymichael))
#### New Contributors
- [@​rileymichael](https://github.com/rileymichael) made their first contribution in [#​698](https://github.com/jdx/mise-action/pull/698)
**Full Changelog**: <https://github.com/jdx/mise-action/compare/v5.2.1...v5.2.2>
### [`v5.2.1`](https://github.com/jdx/mise-action/releases/tag/v5.2.1): : Require the signed packslip for mise 2026.9.3 and later
[Compare Source](https://github.com/jdx/mise-action/compare/v5.2.0...v5.2.1)
The action now refuses to install mise 2026.9.3 or later if the release's signed packslip is missing. This closes a gap where verification could be downgraded to the weaker checksum check.
#### Fixed
- **A missing packslip no longer weakens the check on recent mise releases.** v5.2.0 started checking the mise binary against the release's signed `packslip.sigstore.json`. If that file wasn't found, though, the action quietly fell back to the minisign-signed `SHASUMS256` checksums. Anyone who could hide the file could force the weaker check. Every mise release from 2026.9.3 on includes a packslip, so for those versions a missing bundle now stops the install with an error like this:
```
mise v2026.10.11 must ship a signed packslip, but https://github.com/jdx/mise/releases/download/v2026.10.11/packslip.sigstore.json was not found
```
Releases before 2026.9.3 don't include a packslip, so they're still checked against the signed checksums. A version string that isn't three dot-separated numbers also requires a packslip. If you set the `sha256` input, it still takes precedence over both checks. A packslip that fails verification still never falls back to the checksums. ([#​695](https://github.com/jdx/mise-action/pull/695) by [@​jdx](https://github.com/jdx))
**Full Changelog**: <https://github.com/jdx/mise-action/compare/v5.2.0...v5.2.1>
### [`v5.2.0`](https://github.com/jdx/mise-action/releases/tag/v5.2.0): : Periodic cache rebuilds, signed packslip verification, and monorepo installs
[Compare Source](https://github.com/jdx/mise-action/compare/v5.1.2...v5.2.0)
The default cache key now rolls over every 30 days, so long-lived caches pick up newer mise releases. The action also checks the downloaded mise binary against the release's signed packslip, and it runs `mise install --monorepo` automatically in monorepos. **Existing caches miss once after you upgrade**, because the default cache key format has changed.
#### Added
- **The cache is rebuilt every 30 days by default.** GitHub never evicts a cache that keeps getting hits. Before this release, an active repo could keep the same mise binary and tools for months, until a config file changed. The default cache key now includes a period suffix (`-p<N>`), so the cache is rebuilt from scratch at least once per period. All repos roll over on the same calendar boundary. Use the new `cache_max_age_days` input to change the period, or set it to `0` to keep the old key that never expires. Custom `cache_key` templates can use the new `{{cache_period}}` variable, which `{{default}}` already includes. A custom key that doesn't use it behaves as before. On self-hosted runners that keep mise data between runs, you may also need `auto_update: true` to pick up a newer mise. ([#​689](https://github.com/jdx/mise-action/pull/689) by [@​jdx](https://github.com/jdx), fixes [#​688](https://github.com/jdx/mise-action/issues/688))
```yaml
- uses: jdx/mise-action@v5
with:
cache_max_age_days: 14 # default 30; 0 disables periodic rebuilds
```
- **Throttled cache restores and saves can be retried.** Before this release, when GitHub's cache service returned HTTP 429, the action gave up right away: a restore counted as a miss and a save was skipped. The new `cache_restore_retry_budget` and `cache_save_retry_budget` inputs set how long the action may wait. Each retry waits for the `Retry-After` value plus some random jitter. Once the budget runs out, the action falls back to the old behavior. Retries apply to the main cache, the post-step save and the binary cache. Real cache misses and reservation conflicts are never retried. Both budgets default to `0s` (no retries). `@actions/cache` doesn't report 429 errors directly, so the action detects throttling from its warning messages. If those messages change in a future `@actions/cache` release, throttling won't be detected and nothing will be retried. ([#​692](https://github.com/jdx/mise-action/pull/692) by [@​jdx](https://github.com/jdx), fixes [#​691](https://github.com/jdx/mise-action/issues/691))
```yaml
- uses: jdx/mise-action@v5
with:
cache_restore_retry_budget: 60s
cache_save_retry_budget: 120s
```
- **The latest mise binary can fall back to a second download source.** When the action downloads the latest mise version, it can fall back between GitHub and mise.jdx.dev if the first source fails. The `fetch_from_github` setting decides which source it tries first. Pinned versions and `minimum_release_age` installs are only downloaded from GitHub. The binary is still checked against the signed checksums for the resolved version, whichever source it came from. ([#​692](https://github.com/jdx/mise-action/pull/692) by [@​jdx](https://github.com/jdx))
- **The mise binary is checked against its signed packslip.** If a mise release includes `packslip.sigstore.json`, the action checks the downloaded binary against it. The bundle must be signed by mise's release workflow for that exact tag. After a successful check, the log shows `Verified <asset> against the signed packslip`. If the check fails, the install stops instead of falling back to a weaker check. Releases without a packslip use the existing minisign and `SHASUMS256` check. An explicit `sha256` input still takes precedence. ([#​693](https://github.com/jdx/mise-action/pull/693) by [@​jdx](https://github.com/jdx))
- **Monorepo-aware installs.** If your mise config sets `[monorepo].config_roots`, the action now adds `--monorepo` to `mise install`, so tools configured anywhere in the monorepo get installed. Repos without that setting aren't affected. To opt out, set `monorepo: false`. ([#​679](https://github.com/jdx/mise-action/pull/679) by [@​zeitlinger](https://github.com/zeitlinger))
#### Fixed
- **Tool directories that mise moves to the front of `PATH` are now exported.** The action used to find mise's `PATH` changes by comparing mise's `PATH` with the runner's. If a tool's bin directory was already on the runner's `PATH`, such as `~/.cargo/bin`, mise only moved it to the front, so the action didn't export it. Later steps then found the mise shim first. For example, `rustup` resolved to the shim instead of `~/.cargo/bin/rustup`. The action now asks mise for its entries with `mise env --paths` and exports them in the order mise reports. This fix needs a mise version that supports `--paths`. With older versions, the action uses the old comparison. ([#​685](https://github.com/jdx/mise-action/pull/685) by [@​jdx](https://github.com/jdx))
#### Documentation
- The new "Release workflows" section of the README says that jobs that publish releases shouldn't restore caches. A lower-trust workflow that can write to default-branch caches could otherwise slip files into a release. In those jobs, use `cache: false` or GitHub's `cache-mode: none`. ([#​682](https://github.com/jdx/mise-action/pull/682) by [@​jdx](https://github.com/jdx))
- The README explains how to cache mise's downloads, keyed on `mise.lock`, instead of installed tools. It includes a Windows example that sets `MISE_CACHE_DIR` from `${{ runner.temp }}`, because `actions/cache` doesn't expand `%TEMP%`. ([#​686](https://github.com/jdx/mise-action/pull/686), [#​690](https://github.com/jdx/mise-action/pull/690) by [@​zeitlinger](https://github.com/zeitlinger))
#### Breaking Changes
- The default cache key has a new format, so the first run after upgrading is a cache miss and saves a fresh cache. After that, the cache is rebuilt every 30 days by default. To keep the old cache key that never expires, set `cache_max_age_days: 0`. Workflows that set a custom `cache_key` without `{{default}}` or `{{cache_period}}` aren't affected.
**Full Changelog**: <https://github.com/jdx/mise-action/compare/v5.1.2...v5.2.0>
### [`v5.1.2`](https://github.com/jdx/mise-action/releases/tag/v5.1.2): : mise_dir now sets MISE_DATA_DIR; auto_update handles a locked mise binary
[Compare Source](https://github.com/jdx/mise-action/compare/v5.1.1...v5.1.2)
The `mise_dir` input now also sets where mise installs tools, so those tools end up in the cache. With `auto_update: true`, the action no longer crashes on Windows when the mise binary is still in use.
#### Fixed
- **`mise_dir` now exports `MISE_DATA_DIR`.** Before this release, `mise_dir` moved the mise binary and the cache path, but mise kept installing tools to `~/.local/share/mise`. The saved cache didn't include the tools. On runners where `~/.local` isn't writable, the step failed with `EACCES: permission denied`. When `mise_dir` is set, the action now exports `MISE_DATA_DIR=<mise_dir>`, so tools are installed into the directory that gets cached. If your workflow sets a different `MISE_DATA_DIR`, the `mise_dir` input overrides it. If `mise_dir` isn't set, nothing changes. mise's state directory (`~/.local/state/mise`) stays where it is. If that path also can't be written, set `MISE_STATE_DIR` yourself. ([#​672](https://github.com/jdx/mise-action/pull/672) by [@​jdx](https://github.com/jdx), fixes [#​668](https://github.com/jdx/mise-action/issues/668))
```yaml
- uses: jdx/mise-action@v5
with:
mise_dir: ${{ runner.tool_cache }}/mise/data
```
- **`auto_update` no longer crashes when it can't replace `mise.exe`.** On Windows, the step used to fail with a bare `EPERM: operation not permitted, unlink '…\mise.exe'` if another process was still using the binary. Now, if `version` isn't pinned and the existing binary passes verification against its recorded version, the action prints a warning and continues with that version. In any other case, the step fails with a message that says the file is in use and how to fix it. A pinned `version` never quietly keeps an older binary. ([#​665](https://github.com/jdx/mise-action/pull/665) by [@​jdx](https://github.com/jdx), fixes [#​664](https://github.com/jdx/mise-action/issues/664))
#### Documentation
- The README explains how to use mise's `MISE_ENABLE_TOOLS` setting as a job-level allowlist. Unlike `install_args`, the allowlist applies to the action's install and to later `mise` commands. If jobs use different allowlists, add the value to a custom `cache_key`. ([#​667](https://github.com/jdx/mise-action/pull/667) by [@​zeitlinger](https://github.com/zeitlinger))
- The Rust cache section is updated for mise 2026.9.2 and later, where `mise install` repairs a restored toolchain instead of leaving `rustfmt` missing. Swatinem/rust-cache now works alongside mise-managed Rust. ([#​670](https://github.com/jdx/mise-action/pull/670) by [@​jdx](https://github.com/jdx))
**Full Changelog**: <https://github.com/jdx/mise-action/compare/v5.1.1...v5.1.2>
### [`v5.1.1`](https://github.com/jdx/mise-action/releases/tag/v5.1.1): : GitHub token is no longer exported to later steps by default
[Compare Source](https://github.com/jdx/mise-action/compare/v5.1.0...v5.1.1)
mise-action no longer exports its GitHub token as `MISE_GITHUB_TOKEN` to every later step in the job. A new `persist_github_token` input lets you turn that back on, or pass a different token to later steps. **This changes the default behavior.** If later steps need the token, see Breaking Changes below.
#### Fixed
- **The GitHub token now stays inside the action by default.** Before this release, the `github_token` input (which defaults to `${{ github.token }}`) was written to `GITHUB_ENV` as `MISE_GITHUB_TOKEN`. That let any later step read the token and call the GitHub API with the job's permissions, even if the step never asked for a credential. Now the token is set only for the mise-action step and the processes it starts. The action masks the token in logs. ([#​658](https://github.com/jdx/mise-action/pull/658) by [@​jdx](https://github.com/jdx), reported in [#​657](https://github.com/jdx/mise-action/issues/657))
#### Added
- **`persist_github_token` input (default `false`).** It takes one of three values:
- `false`: the token stays inside the action.
- `true`: the token the action used is exported to later steps. If `env.MISE_GITHUB_TOKEN` is already set, it takes precedence over `github_token`.
- A token value: that token is exported to later steps instead, for example a read-only token. The action still installs tools with `github_token`, or with `MISE_GITHUB_TOKEN` if it's already set.
Setting `false` doesn't clear a `MISE_GITHUB_TOKEN` that was already set at the job level or exported by an earlier step. ([#​658](https://github.com/jdx/mise-action/pull/658) by [@​jdx](https://github.com/jdx))
#### Breaking Changes
Check your workflow if a later step needs `MISE_GITHUB_TOKEN`, such as mise shims, `mise exec`, `mise run` or lazy tool installs that call the GitHub API. Those steps no longer get the token automatically and may hit GitHub API rate limits. To get the old behavior back, opt in:
```yaml
- uses: jdx/mise-action@v5
with:
persist_github_token: true
```
Or give later steps a separate token:
```yaml
- uses: jdx/mise-action@v5
with:
persist_github_token: ${{ secrets.READ_ONLY_TOKEN }}
```
**Full Changelog**: <https://github.com/jdx/mise-action/compare/v5.1.0...v5.1.1>
### [`v5.1.0`](https://github.com/jdx/mise-action/releases/tag/v5.1.0): : Tool version outputs, plugins input, and cached mise reuse
[Compare Source](https://github.com/jdx/mise-action/compare/v5.0.1...v5.1.0)
mise-action now reports the tool versions it installed as step outputs, can install mise plugins before tools, and can save the cache at the end of the job. Several caching fixes stop the action from downloading mise again on every run.
#### Added
- **Tool versions as step outputs.** After install, the action runs `mise ls --json --current` and sets a `versions` output. This is a JSON object of the active, installed tools. Each tool maps to a list of `{version, requested_version, install_path, source}` entries. Each tool also gets its own output with its resolved version, such as `steps.mise.outputs.node`. A tool only gets its own output if its name is a valid output name and isn't `cache-hit` or `versions`. Names like `npm:@scope/pkg` appear only in `versions`. If the action can't read the versions, it prints a warning and the step still succeeds. ([#​655](https://github.com/jdx/mise-action/pull/655) by [@​jdx](https://github.com/jdx))
```yaml
- uses: jdx/mise-action@v5
id: mise
- run: echo "node ${{ steps.mise.outputs.node }}"
```
- **`plugins` input.** List plugins one per line as `name` or `name url`. Blank lines and `#` comments are ignored. The action runs `mise plugins install -y` for each one before `mise install`. Plugins that are already installed, for example restored from the cache, are left as they are. An unknown plugin fails the step. When `plugins` is set, its hash is added to the default cache key. Custom `cache_key` templates can use it as `{{plugins_hash}}`. If `plugins` is unset, existing cache keys don't change. ([#​656](https://github.com/jdx/mise-action/pull/656) by [@​jdx](https://github.com/jdx))
```yaml
- uses: jdx/mise-action@v5
env:
# needed for idiomatic files such as .yvmrc
MISE_IDIOMATIC_VERSION_FILE_ENABLE_TOOLS: yarn
with:
plugins: |
yarn
php https://github.com/verzly/mise-php#latest
```
- **`cache_save_post` input (opt-in, default `false`).** When enabled, the mise cache is saved in the action's post step instead of right after install. This way, tools installed by later steps are included in the cache, for example from monorepo sub-project configs or task-level tools. The setting only applies on a cache miss, because an existing cache entry can't be overwritten. The post step runs even if a later step fails. If the post-step save fails, the action prints a warning and the job doesn't fail. ([#​649](https://github.com/jdx/mise-action/pull/649) by [@​jdx](https://github.com/jdx))
- **`auto_update` input (default `false`).** See Changed below. ([#​642](https://github.com/jdx/mise-action/pull/642) by [@​jdx](https://github.com/jdx))
- The action now warns when you use the `mise_toml` input and a `.mise.toml` already exists in the working directory. mise loads `.mise.toml` before the `mise.toml` the action writes, so the input may have no effect. ([#​654](https://github.com/jdx/mise-action/pull/654) by [@​jdx](https://github.com/jdx))
#### Changed
- **A cached mise is kept when `version` is unset.** Before, each new mise release made the action reject the cached binary in integrity verification and download mise again on every run until the cache key changed. Now the cached binary is kept until the cache key changes. The action verifies it against the signed checksums of the version recorded at install, without running it first. Caches saved before this release have no version record, so they are still verified against the latest release, and a tampered binary is still replaced. The integrity warning now includes the underlying error. To keep updating to newer releases as before, set `auto_update: true`. Each updated binary is cached under its own mise version, so each release is downloaded only once. An explicit `version` input works the same as before. ([#​642](https://github.com/jdx/mise-action/pull/642) by [@​jdx](https://github.com/jdx))
#### Fixed
- **The cache is saved after a partial-match restore.** When the cache was restored from a key that only matched the prefix, the action never saved under the primary key, so it rebuilt the same tools on every run. Exact cache hits still skip the save. ([#​646](https://github.com/jdx/mise-action/pull/646) by [@​jdx](https://github.com/jdx))
- **Caches saved before this release no longer cause a download on every run.** These caches have no version record, so a cached binary is verified against the latest release. Once a newer mise shipped, the action downloaded mise again on every run. It now also saves the reinstalled binary in a cache keyed by mise version, so later runs restore that binary instead of downloading it. ([#​648](https://github.com/jdx/mise-action/pull/648) by [@​jdx](https://github.com/jdx))
- **Windows: mise installs without `unzip`.** The mise zip is now extracted with PowerShell's `Expand-Archive`. Self-hosted Windows runners that don't have `unzip`, such as fresh Windows 11 arm64 machines, can now install mise. ([#​650](https://github.com/jdx/mise-action/pull/650) by [@​jdx](https://github.com/jdx))
#### Documentation
- New README guides cover matrix builds, using another cache action, and Rust caching:
- Matrix builds: use `MISE_<TOOL>_VERSION` overrides and give each matrix entry its own `cache_key`.
- Other cache actions: set `cache: false` and cache mise's data directory yourself.
- Rust: explains why a restored cache can be missing Rust components such as `rustfmt`, with two workarounds. ([#​654](https://github.com/jdx/mise-action/pull/654), [#​651](https://github.com/jdx/mise-action/pull/651) by [@​jdx](https://github.com/jdx))
**Full Changelog**: <https://github.com/jdx/mise-action/compare/v5.0.1...v5.1.0>
### [`v5.0.1`](https://github.com/jdx/mise-action/releases/tag/v5.0.1): : Verify cached mise binaries before running them
[Compare Source](https://github.com/jdx/mise-action/compare/v5.0.0...v5.0.1)
mise-action now checks the integrity of an already-installed `mise` binary before running it. This fixes a security issue that was reported privately.
#### Fixed
- **An existing `mise` binary is verified before it is run.** When a `mise` binary is already on the runner (for example, restored from cache or in `mise_dir`), the action now checks it before calling it. If you set a `sha256` input, the binary must match that checksum and report the requested version. Otherwise, it must match the signed release checksums for the version being installed. If the check fails, the action prints a warning, deletes the binary and installs the requested release again. Before this fix, the action could run a cached binary before checking it. ([#​637](https://github.com/jdx/mise-action/pull/637) by [@​jdx](https://github.com/jdx))
#### Changed
Changes to how the action handles an existing binary, also from [#​637](https://github.com/jdx/mise-action/pull/637):
- **Switching versions uses a full install.** If the cached binary doesn't match the requested version, the action downloads and installs that version. It no longer runs `mise self-update`.
- **Unpinned runs always pick a release.** Without a `version` input, the action now selects a release every time, using `minimum_release_age`, even when `mise` is already installed. It then checks the existing binary against that release, and reinstalls if the binary doesn't match.
- **Older releases need a `sha256` input to reuse a cached binary.** Some older mise releases have no signed checksums. With the `sha256` input set, a cached binary of one of these releases can still be reused without a download. Without it, the action can't verify the binary and installs it again.
**Full Changelog**: <https://github.com/jdx/mise-action/compare/v5.0.0...v5.0.1>
### [`v5.0.0`](https://github.com/jdx/mise-action/releases/tag/v5.0.0): : Default minimum release age of 24 hours for mise
[Compare Source](https://github.com/jdx/mise-action/compare/v4.3.0...v5.0.0)
If you don't pin a `version`, mise-action now installs the newest stable mise release that is at least 24 hours old. Upgrading mise on a runner that already has it is also less likely to hit GitHub API rate limits.
#### Breaking Changes
##### `minimum_release_age` now defaults to `24h` ([#​632](https://github.com/jdx/mise-action/pull/632) by [@​jdx](https://github.com/jdx))
Before this release, `minimum_release_age` was an opt-in setting. It now defaults to `24h`. If you don't set `version`, the action picks the highest-numbered stable mise release published at least 24 hours ago. A mise release that just shipped won't be installed until it's a day old.
To get the latest stable release right away, as in v4, set the delay to `0s`. You can also choose a longer delay:
```yaml
- uses: jdx/mise-action@v5
with:
minimum_release_age: 0s # or e.g. 7d
```
- An explicit `version` input still takes precedence and skips the delay.
- The setting applies only to the mise binary, not to tools installed by mise.
- The action now gets the release list from a public CDN index (`releases.tsv` on mise.jdx.dev) instead of paging through the GitHub Releases API. Picking a release doesn't use GitHub API quota, even when an installed binary is reused. If the index is missing or malformed, the action fails instead of skipping the release-age check.
- Replacing an older installed binary still runs `mise self-update`, which may call the GitHub API to fetch that exact release.
#### Fixed
- `mise self-update` now runs with `MISE_GITHUB_TOKEN`. When a runner already had a different mise version installed, the action runs `mise self-update` to switch versions. That GitHub API call used to go out without authentication, so busy shared or self-hosted runners could hit the rate limit and fail with `HTTP 403 RateLimitedError`. If you already set a token in your environment, the action leaves it unchanged. ([#​619](https://github.com/jdx/mise-action/pull/619) by [@​hegde5](https://github.com/hegde5))
#### New Contributors
- [@​hegde5](https://github.com/hegde5) made their first contribution in [#​619](https://github.com/jdx/mise-action/pull/619)
**Full Changelog**: <https://github.com/jdx/mise-action/compare/v4.3.0...v5.0.0>
</details>
---
### Configuration
📅 **Schedule**: (UTC)
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
♻ **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.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMjYuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjIzNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR contains the following updates:
v4.3.0→v5.2.7v5.2.8Release Notes
jdx/mise-action (https://github.com/jdx/mise-action)
v5.2.7: : Retry failed mise downloads with backoff and show the HTTP statusCompare 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 22and 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: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
Full Changelog: https://github.com/jdx/mise-action/compare/v5.2.6...v5.2.7
v5.2.6: : Fix step hanging after a failed cache restoreCompare Source
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
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/cachefired after 10 minutes. That timer is left running when a download fails (actions/toolkit#2470), and it kept the Node process alive. The action now exits explicitly after both the main step and the post step finish. It waits up to 5 seconds for log output to flush, then exits. The exit code set by any earlier failure is kept. Errors that aren'tErrorobjects now mark the step as failed with their message. Before, they caused an unhandled rejection. (#718 by @jdx and @kjanat, fixes #717)Full Changelog: https://github.com/jdx/mise-action/compare/v5.2.5...v5.2.6
v5.2.5: : Bundled packslip verifier updated to 1.11.0; README examples use v5Compare Source
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.
Changed
packslip.sigstore.jsonthat ships with mise releases from 2026.9.3 onward. The new version runs extra checks on the signed statement: the identity it declares must match the certificate that signed it, and the certificate must belong to thegithub.com/jdx/miserepository. GitHub and GitLab repository names now match regardless of letter case. The action still asks for the same identity, issuer and tag as before, and there are no new inputs. (#715)jdx/mise-action@v5andactions/checkout@v7. (#710 by @deining)Full Changelog: https://github.com/jdx/mise-action/compare/v5.2.4...v5.2.5
v5.2.4: : Reuse cached signed checksums when restoring miseCompare Source
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
SHASUMS256.txtand 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 asSHASUMS256-<version>.txtand.minisigin<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)Full Changelog: https://github.com/jdx/mise-action/compare/v5.2.3...v5.2.4
v5.2.3: : Faster cache key computation in large workspacesCompare Source
The cache key no longer comes from searching the whole workspace for mise config files. In repos that already contain
node_modulesorvendor/bundle, this removes a delay of several minutes in "Restoring mise cache".Fixed
**/…glob patterns. That meant it walked every subdirectory of the workspace, includingnode_modulesandvendor/bundle, before checking the cache at all. When the action ran after a step likepnpm installorruby/setup-rubywithbundler-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 formise.toml,.mise.toml,.config/mise/…,conf.dfragments,.tool-versions, and their local, env-specific and.lockvariants. The step also logsHashed mise config files in N.Ns. (#703 by @jdx and @corsicanec82)cache_keythat doesn't use{{file_hash}}or{{default}}, the action no longer hashes config files at all.--monorepo.New Contributors
Full Changelog: https://github.com/jdx/mise-action/compare/v5.2.2...v5.2.3
v5.2.2: : Include conf.d config fragments in the cache keyCompare Source
The cache key now includes mise
conf.d/*.tomlconfig fragments, so changing one of them invalidates the cache.Fixed
conf.dfragment now invalidates the cache. mise can load config from single-file fragments inconf.d/directories, but the action didn't hash those files when it built the cache key. As a result, adding or changing tools in a fragment could restore an outdated cache. The cache key now also hashesconf.d/*.tomlfiles under.config/mise/,.mise/andmise/. If your repo already uses these fragments, the cache will miss once after you upgrade. (#698 by @rileymichael)New Contributors
Full Changelog: https://github.com/jdx/mise-action/compare/v5.2.1...v5.2.2
v5.2.1: : Require the signed packslip for mise 2026.9.3 and laterCompare Source
The action now refuses to install mise 2026.9.3 or later if the release's signed packslip is missing. This closes a gap where verification could be downgraded to the weaker checksum check.
Fixed
packslip.sigstore.json. If that file wasn't found, though, the action quietly fell back to the minisign-signedSHASUMS256checksums. Anyone who could hide the file could force the weaker check. Every mise release from 2026.9.3 on includes a packslip, so for those versions a missing bundle now stops the install with an error like this:sha256input, it still takes precedence over both checks. A packslip that fails verification still never falls back to the checksums. (#695 by @jdx)Full Changelog: https://github.com/jdx/mise-action/compare/v5.2.0...v5.2.1
v5.2.0: : Periodic cache rebuilds, signed packslip verification, and monorepo installsCompare Source
The default cache key now rolls over every 30 days, so long-lived caches pick up newer mise releases. The action also checks the downloaded mise binary against the release's signed packslip, and it runs
mise install --monorepoautomatically in monorepos. Existing caches miss once after you upgrade, because the default cache key format has changed.Added
-p<N>), so the cache is rebuilt from scratch at least once per period. All repos roll over on the same calendar boundary. Use the newcache_max_age_daysinput to change the period, or set it to0to keep the old key that never expires. Customcache_keytemplates can use the new{{cache_period}}variable, which{{default}}already includes. A custom key that doesn't use it behaves as before. On self-hosted runners that keep mise data between runs, you may also needauto_update: trueto pick up a newer mise. (#689 by @jdx, fixes #688)cache_restore_retry_budgetandcache_save_retry_budgetinputs set how long the action may wait. Each retry waits for theRetry-Aftervalue plus some random jitter. Once the budget runs out, the action falls back to the old behavior. Retries apply to the main cache, the post-step save and the binary cache. Real cache misses and reservation conflicts are never retried. Both budgets default to0s(no retries).@actions/cachedoesn't report 429 errors directly, so the action detects throttling from its warning messages. If those messages change in a future@actions/cacherelease, throttling won't be detected and nothing will be retried. (#692 by @jdx, fixes #691)fetch_from_githubsetting decides which source it tries first. Pinned versions andminimum_release_ageinstalls are only downloaded from GitHub. The binary is still checked against the signed checksums for the resolved version, whichever source it came from. (#692 by @jdx)packslip.sigstore.json, the action checks the downloaded binary against it. The bundle must be signed by mise's release workflow for that exact tag. After a successful check, the log showsVerified <asset> against the signed packslip. If the check fails, the install stops instead of falling back to a weaker check. Releases without a packslip use the existing minisign andSHASUMS256check. An explicitsha256input still takes precedence. (#693 by @jdx)[monorepo].config_roots, the action now adds--monorepotomise install, so tools configured anywhere in the monorepo get installed. Repos without that setting aren't affected. To opt out, setmonorepo: false. (#679 by @zeitlinger)Fixed
PATHare now exported. The action used to find mise'sPATHchanges by comparing mise'sPATHwith the runner's. If a tool's bin directory was already on the runner'sPATH, such as~/.cargo/bin, mise only moved it to the front, so the action didn't export it. Later steps then found the mise shim first. For example,rustupresolved to the shim instead of~/.cargo/bin/rustup. The action now asks mise for its entries withmise env --pathsand exports them in the order mise reports. This fix needs a mise version that supports--paths. With older versions, the action uses the old comparison. (#685 by @jdx)Documentation
cache: falseor GitHub'scache-mode: none. (#682 by @jdx)mise.lock, instead of installed tools. It includes a Windows example that setsMISE_CACHE_DIRfrom${{ runner.temp }}, becauseactions/cachedoesn't expand%TEMP%. (#686, #690 by @zeitlinger)Breaking Changes
cache_max_age_days: 0. Workflows that set a customcache_keywithout{{default}}or{{cache_period}}aren't affected.Full Changelog: https://github.com/jdx/mise-action/compare/v5.1.2...v5.2.0
v5.1.2: : mise_dir now sets MISE_DATA_DIR; auto_update handles a locked mise binaryCompare Source
The
mise_dirinput now also sets where mise installs tools, so those tools end up in the cache. Withauto_update: true, the action no longer crashes on Windows when the mise binary is still in use.Fixed
mise_dirnow exportsMISE_DATA_DIR. Before this release,mise_dirmoved the mise binary and the cache path, but mise kept installing tools to~/.local/share/mise. The saved cache didn't include the tools. On runners where~/.localisn't writable, the step failed withEACCES: permission denied. Whenmise_diris set, the action now exportsMISE_DATA_DIR=<mise_dir>, so tools are installed into the directory that gets cached. If your workflow sets a differentMISE_DATA_DIR, themise_dirinput overrides it. Ifmise_dirisn't set, nothing changes. mise's state directory (~/.local/state/mise) stays where it is. If that path also can't be written, setMISE_STATE_DIRyourself. (#672 by @jdx, fixes #668)auto_updateno longer crashes when it can't replacemise.exe. On Windows, the step used to fail with a bareEPERM: operation not permitted, unlink '…\mise.exe'if another process was still using the binary. Now, ifversionisn't pinned and the existing binary passes verification against its recorded version, the action prints a warning and continues with that version. In any other case, the step fails with a message that says the file is in use and how to fix it. A pinnedversionnever quietly keeps an older binary. (#665 by @jdx, fixes #664)Documentation
MISE_ENABLE_TOOLSsetting as a job-level allowlist. Unlikeinstall_args, the allowlist applies to the action's install and to latermisecommands. If jobs use different allowlists, add the value to a customcache_key. (#667 by @zeitlinger)mise installrepairs a restored toolchain instead of leavingrustfmtmissing. Swatinem/rust-cache now works alongside mise-managed Rust. (#670 by @jdx)Full Changelog: https://github.com/jdx/mise-action/compare/v5.1.1...v5.1.2
v5.1.1: : GitHub token is no longer exported to later steps by defaultCompare Source
mise-action no longer exports its GitHub token as
MISE_GITHUB_TOKENto every later step in the job. A newpersist_github_tokeninput lets you turn that back on, or pass a different token to later steps. This changes the default behavior. If later steps need the token, see Breaking Changes below.Fixed
github_tokeninput (which defaults to${{ github.token }}) was written toGITHUB_ENVasMISE_GITHUB_TOKEN. That let any later step read the token and call the GitHub API with the job's permissions, even if the step never asked for a credential. Now the token is set only for the mise-action step and the processes it starts. The action masks the token in logs. (#658 by @jdx, reported in #657)Added
persist_github_tokeninput (defaultfalse). It takes one of three values:false: the token stays inside the action.true: the token the action used is exported to later steps. Ifenv.MISE_GITHUB_TOKENis already set, it takes precedence overgithub_token.github_token, or withMISE_GITHUB_TOKENif it's already set.Setting
falsedoesn't clear aMISE_GITHUB_TOKENthat was already set at the job level or exported by an earlier step. (#658 by @jdx)Breaking Changes
Check your workflow if a later step needs
MISE_GITHUB_TOKEN, such as mise shims,mise exec,mise runor lazy tool installs that call the GitHub API. Those steps no longer get the token automatically and may hit GitHub API rate limits. To get the old behavior back, opt in:Or give later steps a separate token:
Full Changelog: https://github.com/jdx/mise-action/compare/v5.1.0...v5.1.1
v5.1.0: : Tool version outputs, plugins input, and cached mise reuseCompare Source
mise-action now reports the tool versions it installed as step outputs, can install mise plugins before tools, and can save the cache at the end of the job. Several caching fixes stop the action from downloading mise again on every run.
Added
mise ls --json --currentand sets aversionsoutput. This is a JSON object of the active, installed tools. Each tool maps to a list of{version, requested_version, install_path, source}entries. Each tool also gets its own output with its resolved version, such assteps.mise.outputs.node. A tool only gets its own output if its name is a valid output name and isn'tcache-hitorversions. Names likenpm:@scope/pkgappear only inversions. If the action can't read the versions, it prints a warning and the step still succeeds. (#655 by @jdx)pluginsinput. List plugins one per line asnameorname url. Blank lines and#comments are ignored. The action runsmise plugins install -yfor each one beforemise install. Plugins that are already installed, for example restored from the cache, are left as they are. An unknown plugin fails the step. Whenpluginsis set, its hash is added to the default cache key. Customcache_keytemplates can use it as{{plugins_hash}}. Ifpluginsis unset, existing cache keys don't change. (#656 by @jdx)cache_save_postinput (opt-in, defaultfalse). When enabled, the mise cache is saved in the action's post step instead of right after install. This way, tools installed by later steps are included in the cache, for example from monorepo sub-project configs or task-level tools. The setting only applies on a cache miss, because an existing cache entry can't be overwritten. The post step runs even if a later step fails. If the post-step save fails, the action prints a warning and the job doesn't fail. (#649 by @jdx)auto_updateinput (defaultfalse). See Changed below. (#642 by @jdx)mise_tomlinput and a.mise.tomlalready exists in the working directory. mise loads.mise.tomlbefore themise.tomlthe action writes, so the input may have no effect. (#654 by @jdx)Changed
versionis unset. Before, each new mise release made the action reject the cached binary in integrity verification and download mise again on every run until the cache key changed. Now the cached binary is kept until the cache key changes. The action verifies it against the signed checksums of the version recorded at install, without running it first. Caches saved before this release have no version record, so they are still verified against the latest release, and a tampered binary is still replaced. The integrity warning now includes the underlying error. To keep updating to newer releases as before, setauto_update: true. Each updated binary is cached under its own mise version, so each release is downloaded only once. An explicitversioninput works the same as before. (#642 by @jdx)Fixed
unzip. The mise zip is now extracted with PowerShell'sExpand-Archive. Self-hosted Windows runners that don't haveunzip, such as fresh Windows 11 arm64 machines, can now install mise. (#650 by @jdx)Documentation
MISE_<TOOL>_VERSIONoverrides and give each matrix entry its owncache_key.cache: falseand cache mise's data directory yourself.rustfmt, with two workarounds. (#654, #651 by @jdx)Full Changelog: https://github.com/jdx/mise-action/compare/v5.0.1...v5.1.0
v5.0.1: : Verify cached mise binaries before running themCompare Source
mise-action now checks the integrity of an already-installed
misebinary before running it. This fixes a security issue that was reported privately.Fixed
misebinary is verified before it is run. When amisebinary is already on the runner (for example, restored from cache or inmise_dir), the action now checks it before calling it. If you set asha256input, the binary must match that checksum and report the requested version. Otherwise, it must match the signed release checksums for the version being installed. If the check fails, the action prints a warning, deletes the binary and installs the requested release again. Before this fix, the action could run a cached binary before checking it. (#637 by @jdx)Changed
Changes to how the action handles an existing binary, also from #637:
mise self-update.versioninput, the action now selects a release every time, usingminimum_release_age, even whenmiseis already installed. It then checks the existing binary against that release, and reinstalls if the binary doesn't match.sha256input to reuse a cached binary. Some older mise releases have no signed checksums. With thesha256input set, a cached binary of one of these releases can still be reused without a download. Without it, the action can't verify the binary and installs it again.Full Changelog: https://github.com/jdx/mise-action/compare/v5.0.0...v5.0.1
v5.0.0: : Default minimum release age of 24 hours for miseCompare Source
If you don't pin a
version, mise-action now installs the newest stable mise release that is at least 24 hours old. Upgrading mise on a runner that already has it is also less likely to hit GitHub API rate limits.Breaking Changes
minimum_release_agenow defaults to24h(#632 by @jdx)Before this release,
minimum_release_agewas an opt-in setting. It now defaults to24h. If you don't setversion, the action picks the highest-numbered stable mise release published at least 24 hours ago. A mise release that just shipped won't be installed until it's a day old.To get the latest stable release right away, as in v4, set the delay to
0s. You can also choose a longer delay:versioninput still takes precedence and skips the delay.releases.tsvon mise.jdx.dev) instead of paging through the GitHub Releases API. Picking a release doesn't use GitHub API quota, even when an installed binary is reused. If the index is missing or malformed, the action fails instead of skipping the release-age check.mise self-update, which may call the GitHub API to fetch that exact release.Fixed
mise self-updatenow runs withMISE_GITHUB_TOKEN. When a runner already had a different mise version installed, the action runsmise self-updateto switch versions. That GitHub API call used to go out without authentication, so busy shared or self-hosted runners could hit the rate limit and fail withHTTP 403 RateLimitedError. If you already set a token in your environment, the action leaves it unchanged. (#619 by @hegde5)New Contributors
Full Changelog: https://github.com/jdx/mise-action/compare/v4.3.0...v5.0.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR has been generated by Mend Renovate CLI.
4a0c2d87deto3a0ecdced53a0ecdced5to00091a4e7200091a4e72to7bbd6e55b37bbd6e55b3to3f6726272a3f6726272ato3812412e1e3812412e1eto72d7f4f4e672d7f4f4e6toadc1e9276badc1e9276btocd3fab2409cd3fab2409to0d5b4f44750d5b4f4475tod1548ca020d1548ca020to164c00cc1b164c00cc1btob871a45c3fView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.