Reconcile v0.9.0 external closure - #174
Merged
Merged
Conversation
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
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.
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 synchronizedmainalready existed.This is a
no-releasedocumentation/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
.release-reconciled-version=0.9.0as the single machine-readable external-closure marker..release-versionand a pending current archive section; its post-publicationno-releaseclosure PR aligns both markers and completes that section.PLANS.mdto its inactive template after validation and self-review.Validation
uv run pytest -q tests/test_operations_docs.py— 30 passeduv run pytest -q tests/test_distribution_contents.py tests/test_release_authorization.py— 26 passedgit diff --check./scripts/gitleaks.sh origin/main HEADExternal evidence already read back
v0.9.0target:39ff90a5eb58072f4a5ef5ea6657ba4cadbe1bb0v0.9.01cc0d0641ea76675f403084c21e0f35b97c611e1ea11ea8328d3af7de6236857v0.9.0: closed with 0 open / 5 closedmain == origin/main == v0.9.0^{}at stable release closure; release branch deletedNo closing keywords are used; the release issues are already closed.