You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ mise trust .mise.tomlmise trusted /Users/yous/foo/.mise.tomlmise Config file is not trusted.Trust it with `mise trust`.mise Run with --verbose or MISE_VERBOSE=1 for more information
$ mise trust ./.mise.tomlmise trusted /Users/yous/foo/.mise.tomlmise Config file is not trusted.Trust it with `mise trust`.mise Run with --verbose or MISE_VERBOSE=1 for more information
The input goes to trusted-configs directly, so relative paths are not working:
$ ls -alF ~/.local/state/mise/trusted-configstotal 8drwxr-xr-x@ 5 yous staff 160 Mar 21 16:47 ./drwxr-xr-x@ 4 yous staff 128 Mar 21 16:22 ../-rw-r--r--@ 1 yous staff 64 Mar 21 16:45 .mise.hashlrwxr-xr-x@ 1 yous staff 10 Mar 21 16:47 .mise.toml-24d2afe543c3f0fa@ -> .mise.tomllrwxr-xr-x@ 1 yous staff 12 Mar 21 16:45 .mise.toml-ff3e8c3a48cfb2b6@ -> ./.mise.toml
A clear and concise description of what the bug is.
Expected behavior
Links in trusted-configs should point to the absolute paths like /Users/yous/foo/.mise.toml.
Describe the bug
When
mise trust
is executed with a relative path of config file,trusted-configs
points to a wrong path.To Reproduce
But the output of
mise trust
is confusing:The input goes to
trusted-configs
directly, so relative paths are not working:A clear and concise description of what the bug is.
Expected behavior
Links in
trusted-configs
should point to the absolute paths like/Users/yous/foo/.mise.toml
.mise doctor
outputThe text was updated successfully, but these errors were encountered: