Repository navigation
mise upgrade does not respect minimum release age
#10303
Replies: 6 comments
|
This analysis was performed with the help of Claude (Anthropic Claude Opus 4.8, 1M-context, model ID Summary
Reproduced on the released Root causeThe value is parsed and threaded through correctly — In
This is visible with the existing debug logging — no patching needed: The decisive test: a far-future cutoff ( Two distinct defectsA. B. The candidate gate conflates "missing from the (stale) cached metadata" with "genuinely too new." When the canonical latest-stable is newer than the cached version-info list, mise silently downgrades and mislabels it as a Fixing only A is insufficient: This comment was generated by an AI coding assistant. |
|
Follow-up to the analysis above, also prepared with the help of Claude (Anthropic Claude Opus 4.8, 1M-context, I wrote a unit test that demonstrates the defect, on a fork: Commit: cj81499@7536ce0 What it doesIt adds
ResultThe test fails on current This isolates the root cause cleanly: because the candidate gate ( The test is marked This comment was generated by an AI coding assistant. |
|
Thanks for taking a look at this! I upgraded to I reproduced on both macOS and Linux. macOS: Linux: EDIT: with |
|
Thanks for the The issue is that the shared resolver handled I verified the This comment was generated by an AI coding assistant. |
|
Sounds good, thanks! I'll give this a try once it's released. |
Uh oh!
There was an error while loading. Please reload this page.
Despite setting
minimum_release_ageto "0s",miseignores recent releases.$ mise --version _ __ ____ ___ (_)_______ ___ ____ ____ / /___ _________ / __ `__ \/ / ___/ _ \______/ _ \/ __ \______/ __ \/ / __ `/ ___/ _ \ / / / / / / (__ ) __/_____/ __/ / / /_____/ /_/ / / /_/ / /__/ __/ /_/ /_/ /_/_/____/\___/ \___/_/ /_/ / .___/_/\__,_/\___/\___/ /_/ by @jdx 2026.6.2 linux-x64 (2026-06-09) $ grep -B 5 minimum ~/.config/mise/config.toml [settings] idiomatic_version_file_enable_tools = [ "python", "node", ] minimum_release_age = "0s" $ mise upgrade mise WARN newer codex release 0.139.0 ignored by minimum_release_age; latest eligible release is 0.138.0 mise WARN newer gh release 2.94.0 ignored by minimum_release_age; latest eligible release is 2.93.0 mise WARN newer opencode release 1.17.3 ignored by minimum_release_age; latest eligible release is 1.17.0 mise WARN newer usage release 3.5.0 ignored by minimum_release_age; latest eligible release is 3.4.0 mise WARN newer uv release 0.11.20 ignored by minimum_release_age; latest eligible release is 0.11.19 mise All tools are up to dateThe same behavior occurs even when using the CLI flag:
and even when using a non-zero value:
All reactions