When targeting a project which has not yet hit 1.0, it appears that mise is picking the highest-sorted member using lexicographic sorting rather than alphanumeric sorting, and thus for the package llm (a CLI utility) it chooses 0.9 instead of the most current release (as of this writing), 0.14. Because 0.9 contains a showstopping bug (a missing core dependency), the resulting CLI always crashes.
My current workaround is to specify a release manually (in this case, pipx:llm@0.14).
To Reproduce
➜ mise use -g pipx:llm
creating virtual environment...
creating shared libraries...
upgrading shared libraries...
installing llm from spec 'llm==0.9'...
done! ✨ 🌟 ✨
mise pipx:llm@0.9 ✓ installed mise ~/.config/mise/config.toml tools: pipx:llm@0.9
➜ llm --version
Traceback (most recent call last):
<...snip...>
ModuleNotFoundError: No module named 'requests'
➜ mise uninstall pipx:llm
mise pipx:llm@0.9 ✓ uninstalled
➜ mise use -g pipx:llm@0.14
creating virtual environment...
creating shared libraries...
upgrading shared libraries...
installing llm from spec 'llm==0.14'...
done! ✨ 🌟 ✨
mise pipx:llm@0.14 ✓ installed mise ~/.config/mise/config.toml tools: pipx:llm@0.14
➜ llm --version
llm, version 0.14
Expected behavior
mise use -g pipx:llm && llm --version should print "llm, version 0.14"
Describe the bug
When targeting a project which has not yet hit 1.0, it appears that mise is picking the highest-sorted member using lexicographic sorting rather than alphanumeric sorting, and thus for the package
llm
(a CLI utility) it chooses 0.9 instead of the most current release (as of this writing), 0.14. Because 0.9 contains a showstopping bug (a missing core dependency), the resulting CLI always crashes.My current workaround is to specify a release manually (in this case,
pipx:llm@0.14
).To Reproduce
Expected behavior
mise use -g pipx:llm && llm --version
should print "llm, version 0.14"mise doctor
outputAdditional context This could be intended behavior, but perhaps should surface a warning?