Repository navigation
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_DIRis on another drive. On hostedwindows-2025runners, the workspace andRUNNER_TEMPare onD:, but the action downloaded mise toos.tmpdir()onC:. IfMISE_DATA_DIRpointed into the workspace, movingmise.exeinto 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_TEMPwhen that variable is set and the directory exists. Otherwise it falls back to the system temp directory. If movingmise.exe,mise-shim.exeor a raw mise binary still crosses drives, the action copies the file and then deletes the original. This also covers self-hosted runners whereRUNNER_TEMPis on a different drive from the data directory. Setups that use the default data directory were not affected. If you setTEMPandTMPto${{ runner.temp }}to work around this, you can remove those settings. (#732 by @jdx and @HengYangDS, fixes #730)
New Contributors
- @HengYangDS made their first contribution in cff84f4
Full Changelog: v5.2.7...v5.2.8