From ede28a076c7d86971b434b732c1635a5f3ea73fa Mon Sep 17 00:00:00 2001 From: CoderDeltaLAN Date: Tue, 16 Jun 2026 00:11:27 +0100 Subject: [PATCH] docs: mark v0.2 readiness report as historical --- docs/V0.2-RELEASE-READINESS.md | 22 +++++++++++++++++----- 1 file changed, 17 insertions(+), 5 deletions(-) diff --git a/docs/V0.2-RELEASE-READINESS.md b/docs/V0.2-RELEASE-READINESS.md index 594e845..9ce0e1c 100644 --- a/docs/V0.2-RELEASE-READINESS.md +++ b/docs/V0.2-RELEASE-READINESS.md @@ -1,6 +1,6 @@ # v0.2 Release Readiness Report -Status: blocked for v0.2 release, approved for release preparation. +Status: historical release-readiness preparation report; superseded by the published v0.2.0 release. Date: 2026-06-15. @@ -12,6 +12,18 @@ This report records the release-readiness state after the unreleased v0.2 govern It is not a release note, tag decision, version bump, or stability claim. +## Post-release status note + +This document is retained as historical release-preparation evidence. It no longer represents the current release state. + +The `v0.2.0` release has since been published from commit `c0f542e922bf776083c263751ae9f1f27a9c8c4f`. + +The exact `v0.2.0` tag and GitHub Release exist. Release assets were uploaded, downloaded, checksum-verified, installed from wheel and sdist, and smoke-tested from clean environments. + +PyPI publication has not been performed or claimed. + +For current release state, use the `v0.2.0` GitHub Release, `CHANGELOG.md`, `SECURITY.md`, and post-release audit evidence rather than the historical blockers below. + ## Scope This report covers readiness for a future `v0.2.0` GitHub release of the governance baseline currently present on `main`. @@ -108,7 +120,7 @@ docs/V0.2-GOVERNANCE-RULES-SPEC.md requires a release-readiness audit before any ## Release blockers -The project is not ready for a `v0.2.0` release until these blockers are closed in separate phases. +Historical note: at the reviewed commit, the project was not ready for a `v0.2.0` release until the blockers below were closed in separate phases. These blockers were later closed by the release train. ### Blocker 1: version metadata not cut @@ -140,7 +152,7 @@ A dedicated packaging dry-run phase must verify: ### Blocker 4: v0.2 tag and GitHub Release do not exist -No `v0.2.0` tag or GitHub Release should exist yet. +Historical state at the reviewed commit: no `v0.2.0` tag or GitHub Release existed yet. A dedicated release phase must create them only after version metadata, changelog, artifacts, and release notes are verified. @@ -218,7 +230,7 @@ The recommended release train is: ## Decision -Do not publish `v0.2.0` from the current state. +Historical decision at the reviewed commit: do not publish `v0.2.0` from that state. The correct next action is a packaging and install dry-run after this report is merged. @@ -239,4 +251,4 @@ v0.2 release status: Final verdict: -`v0.2.0` is not releasable yet, but the repository is in a good state to continue a disciplined v0.2 release train. +`v0.2.0` was not releasable from the reviewed commit, but the repository was in a good state to continue a disciplined v0.2 release train.