node@sub-0.1:20.17.0 resolves to node@20.16.0, so the output should be the same 20.16.0
$ mise ls-remote node@sub-0.1:20.17.0
20.16.0
Similarly, if no such version exists (e.g., node@sub-0.0.1:20.17.0), mise should exit with status code 0, but no output (same as querying a non-existent version, e.g., mise ls-remote node@20.4983.324234)
The reason this is a problem is because I want to pre-install a selection of recent versions on our CI runners (without needing to manually specify the versions), to improve my users' build speeds.
I was intending to run mise install node@latest node@sub-0.0.1:latest node@sub-0.1:latest, but this fails if there's no such version (e.g., if latest is 20.0.0, then sub-0.1:latest doesn't exist).
Therefore, I was hoping to use mise ls-remote to filter out the non-existent versions first.
Hey, thanks for the work you've done on this project!
Describe the bug
When using
mise ls-remote
with antool@sub-X:base
argument, it returns every version for that tool, instead of the version that matches.To Reproduce
Expected behavior
node@sub-0.1:20.17.0
resolves tonode@20.16.0
, so the output should be the same20.16.0
Similarly, if no such version exists (e.g.,
node@sub-0.0.1:20.17.0
),mise
should exit with status code 0, but no output (same as querying a non-existent version, e.g.,mise ls-remote node@20.4983.324234
)mise doctor
outputAdditional context
The reason this is a problem is because I want to pre-install a selection of recent versions on our CI runners (without needing to manually specify the versions), to improve my users' build speeds.
I was intending to run
mise install node@latest node@sub-0.0.1:latest node@sub-0.1:latest
, but this fails if there's no such version (e.g., iflatest
is20.0.0
, thensub-0.1:latest
doesn't exist).Therefore, I was hoping to use
mise ls-remote
to filter out the non-existent versions first.