fix(ci): uv.lock recorded 1.4.0, so every locked lane died before testing

The v1.5.0 lock was generated before the version bump, so its own
[[package]] entry said autocad-mcp-pro 1.4.0 while pyproject said 1.5.0.
No dependency differed -- the transitive graph is byte-identical -- but
`uv sync --locked` will not re-resolve, so lint, test-linux 3.11,
test-linux 3.12 and test-windows all failed at install before running a
single test.

`uv lock` fixes it in one line. The gate that should have caught it did
not exist: test_release_consistency chains pyproject -> version.py ->
CHANGELOG -> README -> server.json, and the lockfile was the one release
artifact carrying a version string nothing checked. Added
test_uv_lock_records_the_pyproject_version, verified RED against the
broken lock and green against the fixed one.

Reproduced the CI lanes locally into a throwaway environment before
pushing this time: `uv sync --locked --only-group dev`, then
`--locked --extra pdf`, then ruff and pytest under `uv run --no-sync`.
1242 passed, 1 xfailed.

README test-count snapshot 1242 -> 1243 for the new gate.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Umut CAN
2026-08-06 10:03:29 +03:00
co-authored by Claude Opus 5
parent b03a7615b1
commit 4e0f8a90fd
3 changed files with 33 additions and 2 deletions
+1 -1
View File
@@ -16,7 +16,7 @@ refine quality issues inside transactions, and deliver hashed artifacts with
validation evidence.
> **v1.5 release snapshot:** 154 tools · 6 resources · 5 prompt templates ·
> 1242 collected tests. Runtime discovery through `system_about` is authoritative.
> 1243 collected tests. Runtime discovery through `system_about` is authoritative.
## Install in 10 seconds