Version and stage labels are stuck at 0.6.3 / Stage 6 #10
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
These places still say 0.6.3 / Stage 6:
pyproject.tomlsrc/cmonet/__init__.py"0.6.3"ingenerated-contracts.ts)frontend/package.jsonfrontend/src/app.ts/healthz("stage": 6)server.pyMeanwhile the schema is at 18 and the docs cover Stage 13. Releases are signed (
tools/release.py) and backups carry provenance, so the version should move with them.Decision needed: the numbering, for example 0.13.0 for the Stage 13 state or a date-based scheme.
Tests pin the literals (
tests/stage4/test_delivery.py,tests/stage6/test_runtime.py). The footer could read the version from/api/v1/statusinstead of hard-coding it.Found in the 2026-10-13 review (PR #1).
Done in
c6a63e9and the version commits after it, now on master.src/cmonet/__init__.pyholds the version andSTAGE(13), and the footer,/healthzand/api/v1/statusread them from there.tools/version.pychecks and bumps every copy, andtools/check.pyfails if any copy disagrees.tools/pr.pyraises the version once per PR, stacked PRs included, with a "Version X.Y.Z ()" commit. 0.6.3 went to 0.7.0, 0.7.1 and then 0.7.2.