Closed RafalSkolasinski closed 1 month ago
Might be related to #2265 (takes up to 6h for new versions to be picked up) or the local cache. Have you tried mise cache clear
already?
Have you tried mise cache clear already? Tried it now, still the same.
Problem seems to be in the asdf-kubectl plugin. The command mise latest kubectl
shows 1.31.0
whereas the latest version is 1.31.1
.
The latest-stable shell script (respectively its curl command) also shows this version.
curl -L -s https://dl.k8s.io/release/stable.txt | cut -c 2- -
Nevertheless mise
should probably handle this case and not mark the version as outdated if it is newer than the latest available version reported.
Nevertheless mise should probably handle this case and not mark the version as outdated if it is newer than the latest available version reported.
Maybe what we could do is have a method on the backends like is_latest(v: &str)
which would dispatch to each plugin rather than just doing v == latest
. Then inside that logic we could default to some semver code or have special overrides similar to what we've done for version prefixing with ruby/java.
or perhaps this code should just use that same fuzzy logic we use with ruby/java and compare where the current version is within the list. If our version is newer than latest we could not display the latest field.
Currently not able to reproduce this behaviour and at some point i already addressed this at least partially.
https://github.com/jdx/mise/blob/b9f5ac22905c47d776c91ee3f950328656909085/src/toolset/mod.rs#L335
It also stopped happening for me ;/ Unless you want to keep it open for investigation I am good with closing it.
Describe the bug
Mise reports newest kubectl as outdated
To Reproduce
mise list kubectl
Expected behavior
1.31.1 is not marked as outdated
mise doctor
outputAdditional context Add any other context about the problem here. Consider running mise with
--debug
or--trace
for extra debug info.