Closed KaBankz closed 3 weeks ago
It might well be that caching plays its part here. From my quick try to reproduce i could resolve this by running a mise cache clear
before a mise ls
which then showed the outdated indicator properly. Maybe the cache freshness threshold for remote/latest versions should be ~lowered~ implemented.
Describe the bug Packages installed using the npm backend do not update even though they are set to version "latest"
I've only discovered this because I use
eas-cli
which notifies me whenever it's out of date.To Reproduce
mise outdated
ormise upgrade
Expected behavior npm packages to be updated when there are updated available
mise doctor
outputAdditional context mise config
mise ls
When I manually install the latest version using
mise install npm:eas-cli@11.0.0
the output ofmise ls
says it's outdated