-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mise prune
wanna remove a tool just installed by mise use
: probably version tag slash/dash issue
#2870
Labels
bug
Something isn't working
Comments
jdx
added a commit
that referenced
this issue
Nov 26, 2024
jdx
added a commit
that referenced
this issue
Nov 26, 2024
jdx
added a commit
that referenced
this issue
Nov 26, 2024
I can confirm that #3195 seems to have fixed the immediate problem: ❯ mise use ubi:plandex-ai/plandex@cli/v1.1.1
mise Installed binary into /Users/simon/.local/share/mise/installs/ubi-plandex-ai-plandex/cli-v1.1.1/bin/plandex
mise ubi:plandex-ai/plandex@cli/v1.1.1 ✓ installed mise ~/Code/sandbox/vars/mise.toml tools: ubi:plandex-ai/plandex@cli/v1.1.1
❯ rm mise.toml
❯ mise prune
mise pruned configuration links
remove ubi:plandex-ai/[email protected] ? Yes
mise ubi:plandex-ai/[email protected] ✓ remove ~/Library/Caches/mise/ubi-plandex-ai-plandex/cli-v1.1.1 However the tool is now listed twice in ❯ mise ls
Tool Version Config Source Requested
ubi:plandex-ai/plandex cli/v1.1.1 ~/Code/sandbox/vars/mise.toml cli/v1.1.1
ubi:plandex-ai/plandex cli-v1.1.1 Both are removed after the prune. |
jdx
added a commit
that referenced
this issue
Nov 26, 2024
jdx
added a commit
that referenced
this issue
Nov 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After installing a tool with
mise use
followingmise prune
asks to delete it.To Reproduce
Expected behavior
mise prune
shouldn't remove tool listed in.mise.toml
.mise doctor
outputAdditional context
It's weird
mise prune
reports version ascli-v1.1.1
instead ofcli/v1.1.1
- maybe it's related to the issue.The text was updated successfully, but these errors were encountered: