v5.1.2
v5.1.2: mise_dir now sets MISE_DATA_DIR; auto_update handles a locked mise binary
Changed 2
- The README documents using MISE_ENABLE_TOOLS as a job-level allowlist that applies to the action's install and later mise commands, and recommends adding it to a custom cache_key when jobs use different allowlists
- The Rust cache section of the README is updated for mise 2026.9.2 and later, where mise install repairs a restored toolchain so Swatinem/rust-cache works alongside mise-managed Rust
Fixed 2
- When mise_dir is set, the action exports MISE_DATA_DIR so tools are installed into the directory that gets cached, overriding any different MISE_DATA_DIR set in the workflow behavior changed · inferred, marked in the notes below
- auto_update no longer fails with a bare EPERM error on Windows when mise.exe is in use; if version is not pinned and the existing binary verifies against its recorded version, a warning is printed and the step continues with that version, otherwise the step fails with a message explaining the file is in use
1 change to check, marked in the notes below
From jdx/mise-action
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_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) behavior changed · inferred- uses: jdx/mise-action@v5 with: mise_dir: ${{ runner.tool_cache }}/mise/dataauto_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
- The README explains how to use mise's
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) - The Rust cache section is updated for mise 2026.9.2 and later, where
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