Version and stage labels are stuck at 0.6.3 / Stage 6 #10

Closed
opened 2026-10-13 05:50:27 -04:00 by vinny · 1 comment
Owner

These places still say 0.6.3 / Stage 6:

  • pyproject.toml
  • src/cmonet/__init__.py
  • the RuntimeStatus contract (a literal "0.6.3" in generated-contracts.ts)
  • frontend/package.json
  • the footer in frontend/src/app.ts
  • /healthz ("stage": 6)
  • the FastAPI title in server.py

Meanwhile 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/status instead of hard-coding it.

Found in the 2026-10-13 review (PR #1).

These places still say 0.6.3 / Stage 6: - `pyproject.toml` - `src/cmonet/__init__.py` - the RuntimeStatus contract (a literal `"0.6.3"` in `generated-contracts.ts`) - `frontend/package.json` - the footer in `frontend/src/app.ts` - `/healthz` (`"stage": 6`) - the FastAPI title in `server.py` Meanwhile 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/status` instead of hard-coding it. Found in the 2026-10-13 review (PR #1).
Author
Owner

Done in c6a63e9 and the version commits after it, now on master. src/cmonet/__init__.py holds the version and STAGE (13), and the footer, /healthz and /api/v1/status read them from there. tools/version.py checks and bumps every copy, and tools/check.py fails if any copy disagrees. tools/pr.py raises 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.

Done in c6a63e9 and the version commits after it, now on master. `src/cmonet/__init__.py` holds the version and `STAGE` (13), and the footer, `/healthz` and `/api/v1/status` read them from there. `tools/version.py` checks and bumps every copy, and `tools/check.py` fails if any copy disagrees. `tools/pr.py` raises the version once per PR, stacked PRs included, with a "Version X.Y.Z (<topic>)" commit. 0.6.3 went to 0.7.0, 0.7.1 and then 0.7.2.
vinny closed this issue 2026-10-13 15:44:44 -04:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
vinny/CMOnet#10
No description provided.