1.0.0b3

The engine reports the version that built it, and signs its assessments with it.

1.0.0b2 answered 1.0.0b1, because __version__ was a literal in __init__.py beside the one in pyproject.toml and only one of them was bumped.

That value is part of the canonical content an assessment is digested over. A document produced by 1.0.0b2 therefore carried a correct digest over content naming the wrong engine: the digest was honest about what it covered, and what it covered was not honest about what made it. In an engine whose whole claim is that a conclusion traces back to what produced it, that is not a typo.

The version is now read from the installed distribution metadata, so pyproject.toml is the only place it exists. tests/test_version.py compares the two by import and through --version as a user runs it, and refuses to let the not-installed fallback pass as a real version. It failed the moment it was written, against a virtual environment still holding the previous install.

Also in this release:

• The generated contract manifest and the stored example assessment and comparison carry 1.0.0b3. Both were stale for the same reason.
• CONTRIBUTING.md names the whole gate. CI runs tools/release-check.sh, nine steps; the document listed four, so a contributor could run everything it asked for and still be refused for formatting.
• The repository speaks English. A test file, a comment in tools/coverage.py and the same note repeated across seven PowerShell modules were in Portuguese.

1.0.0b1 and 1.0.0b2 stay in the history. Neither is withdrawn and neither number is reused.

Install

pip install m365-governance-as-code==1.0.0b3