about summary refs log tree commit diff
path: root/test/python/test_version.py
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-11-07 17:17:19 +0000
committerPjotr <wrk@bosa.lan>2026-11-07 17:17:19 +0000
commit2307d5e2db5ce8efae19a647bd48b4311be34607 (patch)
treeaefc0a48a38cd69fd0f38f8c163ad77ad8d8317a /test/python/test_version.py
parent9fa03035b9f21352c1c8b93681cc1bc1ce4cf6ff (diff)
downloadgenenetwork4-2307d5e2db5ce8efae19a647bd48b4311be34607.tar.gz
version: document the provenance fields, and assert they agree
* README.md (/version): the example carries dirty/source_digest/branch,
and the prose says why a stamp can lag a commit -- a binary built from a
dirty tree must not claim that commit -- and that build.rs re-stamps on
a commit because it watches the ref, not just .git/HEAD.
* docs/www/ai-instruction.md: comparing against a clone means comparing
the part before "-dirty", with source_digest for the exact build.
* tests/version.rs: `dirty` mirrors the suffix, branch is non-empty, and
source_digest is 16 hex digits or unknown.
Diffstat (limited to 'test/python/test_version.py')
0 files changed, 0 insertions, 0 deletions