mise manager: treat symbolic selectors (latest/lts/partial) as ranges and support lockfile-only updates

[zeitlinger]

What

Extend the mise manager so that symbolic version selectors in mise.toml — latest, lts, and partial forms like temurin-25 — are treated as range constraints and receive Renovate updates against the lockfile, instead of being dropped with skipReason: invalid-value.

Current behavior

With mise.toml:

[tools]
node = "lts"
java = "temurin-25"
protoc = "latest"

and a committed mise.lock, Renovate:

• extract.js:33 reads mise.lock and forwards lockedVersion (e.g. 24.18.0, temurin-25.0.3+9.0.LTS).
• currentValue stays "lts" / "latest" / "temurin-25".
• Lookup at workers/repository/process/lookup/index.js:276 can't parse it as a version → skipReason: "invalid-value" → no update PR.
• update-locked.js is a stub: returns unsupported in every branch except already-updated.

Net effect: users who use mise's own selector syntax get zero Renovate coverage, even though mise.lock pins a concrete version that could be bumped safely.

Proposal

Treat these selectors as ranges, not opaque strings:

Selector	Semantics
latest	unbounded — any newer release
lts	LTS releases only (per datasource)
temurin-25	major = 25 (vendor-prefixed partial)
24, 24.1	major / major.minor partial (already common)

For deps matching one of these, use lockedVersion as compareValue for lookup, apply the selector as an allowedVersions filter (the workarounds:javaLTSVersions preset already does the LTS filter for java-version), and emit an update-lockfile update that only rewrites mise.lock, leaving mise.toml untouched.

Work items

1. extract.js — recognize selectors per backend; when present with a lockedVersion, emit currentValue: lockedVersion + a rangeStrategy: "update-lockfile" hint. Preserve the original selector so update-lockfile knows not to touch the toml.
2. update-locked.js — implement real lockfile mutation (currently stub at line 5).
3. Selector taxonomy — decide which selectors count per backend. core/java-version and aqua are the common cases; cargo, pipx, npm, go, ubi, gem, dotnet, spm each have their own conventions.
4. Tests + docs.

Motivation

Discovered while debugging why mise.lock's vendor-prefixed lockedVersion (temurin-25.0.3+9.0.LTS) breaks a downstream tool's tracked-deps snapshot in prometheus/client_java. The immediate workaround was to keep pinned concrete versions in mise.toml, but that defeats the point of mise.lock and mise's own selector semantics. Would be great to have first-class Renovate support.

Happy to help scope / prototype once maintainers weigh in on the approach.

---

Drafted with Claude (Claude Code).