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

[LukasWodka]

Summary

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

v0.10.12 is already tagged — bothv0.10.12 and v0.10.12-rc.1 exist — and the delta waiting on develop touches internal/doctor/doctor.go, under the internal/* publish_path in release-train's repos.yml:

• fix(release): retry the cosign call, bounded and transient-only (backend#2379) #563fix(release): retry the cosign call, bounded and transient-only
• feat(doctor): measure disk, the dimension it never looked at (backend#2223) #564feat(doctor): measure disk, the dimension it never looked at

With VERSION still reading 0.10.12, the staging hop's version preflight refuses:

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

Measured, not inferred: the cli leg hit this on the 2026-08-25 staging hop and cli sat the hop out while the rest of the fleet rode. It cannot ride any hop until this lands.

Same shape as #562 (the 0.10.12 bump) one day earlier. Worth stating the pattern out loud: each hop that ships published files needs its own bump, because the previous bump is consumed by the hop that shipped it. This is the second consecutive day the cli leg has been the only repo held for this reason.

Patch-level, matching the whole 0.10.x series.

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\.12" --include="*.go" --include="*.sh" --include="*.md" --include="*.yml" .
→ VERSION:1 only

File shape is byte-exact — single line, trailing newline preserved (0.10.13\n), confirmed with xxd — which is what 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 stamp only; no application logic, security, or data-path changes.

Overview
Bumps the repo VERSION file from 0.10.12 to 0.10.13 so the release train can tag the next rc after v0.10.12 is already cut.

This is a release-metadata-only change: it unblocks staging/version preflight when develop has deltas under published paths (e.g. doctor and release fixes queued after 0.10.12), without altering runtime CLI behavior.

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

[saqlainsyed007]

Approving. I checked the standards concern (org rule: "never hand-bump a version file") against release-train's own code, and this is the sanctioned mechanism rather than a bypass: scripts/promote-repo.shreadsVERSION and refuses to cut an rc when v$ver is already tagged ("NOT tagged - v$ver already exists" — the exact message, pinned in promote-verify.sh). It does not bump VERSION itself, so declaring the next cycle's version on develop is the input the train needs. develop isn't a publish branch, no tag is cut here, and the train still owns the actual rc/promotion — so this doesn't cross the hand-cut-tag / hand-publish line the rule is about.

Correct and unblocks #563/#564's internal/doctor delta for the next rc. CI green.