1.0.0b2

The release whose project page is right. Nothing in the engine changed.

1.0.0b1 proved the publishing path end to end, and in doing so showed what the path had not checked: the README is what PyPI renders as the project description, and it was written for GitHub.

• The banner used a relative path. GitHub resolves it against the repository; PyPI has none, so the page opened with a broken image where the product's name belongs.
• Eighteen more links pointed at CONTRIBUTING, LICENSE, CHANGELOG and ten documents under docs/ by relative path. Every one of them was dead on the project page.
• pip install m365-governance-as-code resolves to nothing while the only version is a pre-release, and that was the first command anybody was given.
• The README claimed doctor prints where the packaged fixtures live. It does not, so the quick start reached evaluate --evidence <a file> with no file.

A release description on PyPI is frozen at upload, so correcting the files could not correct the published page. This version is what publishes the corrected one.

Also added: badges for the published version, the Python versions CI runs the suite against, the licence, the state of main, the documentation, the current release and the DCO requirement, each with a line saying what it reports and what it does not. And docs/RELEASING.md, which writes down the publishing procedure and the two things that cannot be fixed after an upload.

Install

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

The == is not optional: 1.0.0b2 is a pre-release, and pip skips those unless a version is pinned or --pre is given.