Skip to content

chore(release): OATHDO v0.2.0 - #91

Open
eimyroot wants to merge 2 commits into
mainfrom
release/oathdo-v0.2.0
Open

eimyroot wants to merge 2 commits into
mainfrom
release/oathdo-v0.2.0

Conversation

@eimyroot

@eimyroot eimyroot commented Sep 2, 2026

Copy link
Copy Markdown
Owner

Release intent

Prepare the first OATHDO-branded release from the closed public baseline.

Scope

  • bump package version from 0.1.0 to 0.2.0;
  • promote accumulated closure work from Unreleased into 0.2.0 — 2026-09-02;
  • preserve the compatible goverdocs Python package and CLI naming;
  • no governance rule, authority binding, workflow, dependency policy, schema identifier, or runtime trust boundary is weakened.

Release highlights

  • public OATHDO identity;
  • read-only localhost governance cockpit;
  • repository banner and professional public surface;
  • English README / CONTRIBUTING / SECURITY / INSTALLATION / MkDocs portal;
  • portable installation guidance;
  • cockpit safety/inventory coverage;
  • preserved REUSE, OpenSSF Scorecard, reproducible build, and exact-head governance model.

Verification

This PR must pass the repository Quality, CodeQL, and GOVERDOCS Governance Gate checks on its exact HEAD before merge. After merge, tag/release v0.2.0 should target the resulting main release commit. Historical v0.1.0 remains unchanged.

Rollback

Do not tag or publish if any release or governance check fails. Revert the release bump via a governed PR if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant