Release v0.9.0 - #173
Merged
Merged
Conversation
xeonvs
added a commit
that referenced
this pull request
Sep 3, 2026
## Goal Reconcile repository truth after completed stable v0.9.0 publication. The archived v0.9.0 plan still said `external stable delivery pending`, although the immutable Release, tag, Actions receipts, issue closure, milestone closure, branch cleanup, and synchronized `main` already existed. This is a `no-release` documentation/process correction in the same PR. It does not modify toolkit runtime, package or next-release versions, OCR compatibility, dependencies, workflows, tags, Release assets, registry artifacts, attestations, provenance, or the immutable receipt. ## Delivered 1. Records the exact external v0.9.0 closure evidence in the current archived plan and index. 2. Adds `.release-reconciled-version=0.9.0` as the single machine-readable external-closure marker. 3. Defines two valid lifecycle states: a release PR has a newer `.release-version` and a pending current archive section; its post-publication `no-release` closure PR aligns both markers and completes that section. 4. Adds one focused existing-suite contract for marker, current archive status, and index consistency. 5. Returns `PLANS.md` to its inactive template after validation and self-review. ## Validation - `uv run pytest -q tests/test_operations_docs.py` — 30 passed - `uv run pytest -q tests/test_distribution_contents.py tests/test_release_authorization.py` — 26 passed - focused Ruff check and format check - `git diff --check` - `./scripts/gitleaks.sh origin/main HEAD` - complete range self-review; no runtime/package/workflow changes ## External evidence already read back - Release PR #173 merge and annotated `v0.9.0` target: `39ff90a5eb58072f4a5ef5ea6657ba4cadbe1bb0` - Stable workflow: #33734006965, successful - Immutable GitHub Release: `v0.9.0` - Release receipt SHA-256: `1cc0d0641ea76675f403084c21e0f35b97c611e1ea11ea8328d3af7de6236857` - Issues #167, #168, #169, #170, and #172: closed by GitHub Actions receipts - Milestone #11 `v0.9.0`: closed with 0 open / 5 closed - `main == origin/main == v0.9.0^{}` at stable release closure; release branch deleted No closing keywords are used; the release issues are already closed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release scope
Prepare stable toolkit 0.9.0 for the exact authorized issue set:
The stable Release workflow owns issue and milestone closure; this PR deliberately uses no closing keywords.
Reviewed implementation evidence
3441e8a77d71b026db89a896d6374f6cb0a09b993c7e38c08a48c9af1d0b0c5e10ecf0ac8b5eacc30.8.8.dev83706dfce3991a00b9e93aa65f19bb30baa6b323eab57d8c449d170310a63bbfafb22e1fa5eacade47a130e21474442034aee28c93b5f6880a652981efb353de99cecd81ce-bc01-42eb-bedf-a4a2a44a096c: zero reportable findings; not rerun6ad0e1f607b2ddcbb9e7b25e4432d6102ec22d7ef6847c2858c8fb22d38cc0f2Repository release mutations
0.9.0/0.9.11788423271and exact sorted authorization issues[167,168,169,170,172]0.9.0PLANS.mdto its inactive templateValidation
fda7a7c5a09e836f20692ff20f1449ee8114749da0be248ff24680367e0d9f60; sdist720825c10dcdc38e403b66c18ab17dd9b2fd8a36919a96973634b5ed08fd391cocr-ci --helppassed on Python 3.12, 3.13, and 3.14External handoff
Stable TestPyPI/PyPI publication, registry and Release byte equality, PEP 740 provenance, GitHub attestations, annotated tag, immutable five-asset GitHub Release, release receipt validation, supported-Python readback installs, issue receipts/closure, milestone closure, and branch cleanup remain pending until this exact reviewed release head is squash-merged.