luum-home/luum-cognitive-os/bump-version

Bump Version

Purpose

Determine the next version number and write it to the VERSION file. Accepts an explicit version or a bump type (patch, minor, major).

Input

One of:

• Explicit version: /bump-version 1.2.3
• Bump type: /bump-version patch | /bump-version minor | /bump-version major
• If neither provided: ask the user which bump type to use before proceeding

Output

BUMP VERSION: X.Y.Z
  Previous: A.B.C
  New: X.Y.Z
  Bump type: patch | minor | major | explicit
  Written to: VERSION

Exits 0 on success. Exits 1 if VERSION file is missing or current version is malformed.

When to Use

• After /validate-release passes
• Before /generate-changelog (changelog needs the new version number)
• User says /bump-version [version_or_type]

Process

Step 1: Read Current Version

CURRENT=$(cat VERSION)

Validate it is semver (X.Y.Z). If malformed: FAIL.

Step 2: Calculate New Version

Given the input:

• Explicit version (e.g., 1.2.3): use directly. Validate it is greater than current.
• `patch`: increment patch: 0.2.1 → 0.2.2
• `minor`: increment minor, reset patch: 0.2.1 → 0.3.0
• `major`: increment major, reset minor and patch: 0.2.1 → 1.0.0
• No input: ask the user: "Current version is X.Y.Z. Bump patch, minor, or major?"

Step 3: Write VERSION (lockstep — both files)

The OS uses TWO version files in lockstep (decided 2026-05-06):

• VERSION (root) — canonical Cognitive OS version stream
• cmd/cos/VERSION — Go binary build version, equal to root VERSION

Write to BOTH:

echo "X.Y.Z" > VERSION
echo "X.Y.Z" > cmd/cos/VERSION

Verify both:

test "$(cat VERSION)" = "$(cat cmd/cos/VERSION)" || { echo "VERSION drift"; exit 1; }
cat VERSION

Output equals the new version string and both files match.

Rationale: cos Go binary is Surface 1 of the OS (ADR-172). Streams stay synced unless a future ADR explicitly bifurcates (e.g. cos-vX.Y prefix tags). Until then, keep them in lockstep.

Safety Rules

• Keep version monotonic: new version > current version
• Write only valid semver strings to VERSION
• Write VERSION + cmd/cos/VERSION in lockstep — drift is a release blocker
• If the user provides an explicit version that is <= current, ask for confirmation before proceeding
• Leave committing to /tag-release

Trust Report

TRUST_REPORT: SCORE=95 STATUS=HIGH EVIDENCE=3 UNCERTAINTIES=1
---
Score: 95/100
EVIDENCE: Read current VERSION, calculated new version, verified write
CONFIDENT: Arithmetic is deterministic; file write is verified
UNSURE: User may have intended a different bump direction than what was inferred
VERIFY: cat VERSION should show the expected new version