Skip to content

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

Choose a tag to compare

@github-actions github-actions released this 12 Nov 17:49
· 8 commits to main since this release
Immutable release. Only release title and notes can be modified.
d5574b5

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: v5.2.7...v5.2.8