chore(release): bump VERSION to 0.10.12 for next cycle

[LukasWodka]

Summary

Declares 0.10.12 as the next release version so the release train can cut an rc for it.

v0.10.11 is already tagged — bothv0.10.11 and v0.10.11-rc.1 exist — and the delta
waiting on develop (#541, feat(doctor): surface the machine beneath the nodes) touches
internal/cli/*, a declared publish_path in release-train's repos.yml. With VERSION
still reading 0.10.11, the staging hop's version preflight refuses:

rc NOT tagged - v0.10.11 already exists and the delta DOES touch published files
(bump VERSION on develop before the next release)

Measured, not inferred: on the 2026-08-24 staging hop the cli leg hit this on both
settle dispatches (runs 32713998202
and 32717833447), so cli sat
the hop out while the rest of the fleet rode. It cannot ride any hop until this lands.

Patch-level, matching the whole 0.10.x series (0.10.1 → 0.10.11 were all patch bumps,
features included).

Type

chore(release)

Test plan

No behaviour change. VERSION is read by release.yml at tag time and by the release
train's version preflight; nothing in the binary reads it at runtime. Verified nothing else
in the repo pins the old version:

grep -rn "0\.10\.11" --include="*.go" --include="*.sh" --include="*.md" --include="*.yml" .
→ no matches

The bump is byte-exact in shape (single line, trailing newline preserved), so the file stays
0.10.12\n as release.yml expects.

Checklist

• Targets develop
• One self-contained change (VERSION, 1 line)
• Assignee set, one reviewer requested
• No secrets, tokens or customer data

---

Note

Low Risk
Single-line version file bump with no runtime, auth, or data-handling changes.

Overview
Bumps VERSION from 0.10.11 to 0.10.12 so the release train can cut the next rc. v0.10.11 is already tagged, and pending published-path changes were blocking staging while this file still matched the last tag.

^{Reviewed by Cursor Bugbot for commit e334805. Bugbot is set up for automated code reviews on this repo. Configure here.}