Release v0.10.0 - #185
Merged
Merged
Release v0.10.0#185
Conversation
xeonvs
added a commit
that referenced
this pull request
Sep 9, 2026
## Scope Complete the already-published **v0.10.0** lifecycle with a strict, documentation-only `no-release` reconciliation. No package/runtime source, stable/dev marker, release metadata, tag, distribution, registry publication, provenance, attestation, receipt, or GitHub Release asset is changed. ## Verified delivery - Release PR: #185 - Protected merge: `f33674ebe88eab10406123299e8a9c8728171781` - Successful idempotent recovery: [workflow 34348030036](https://github.com/xeonvs/open-code-review-toolkit/actions/runs/34348030036) - Immutable release: [v0.10.0](https://github.com/xeonvs/open-code-review-toolkit/releases/tag/v0.10.0) - Authorized issue set: #181, #182; each has one GitHub Actions-owned receipt and is closed. - Milestone `v0.10.0` is closed with zero open issues. The first release workflow, [34347350040](https://github.com/xeonvs/open-code-review-toolkit/actions/runs/34347350040), passed its build, registry, provenance, attestation and supported-Python gates, but GitHub returned an `Internal Server Error` while accepting the new tag; no tag, Release, receipt, or issue receipt had been created. The recovery dispatch reused the exact authorization tuple and completed idempotently. ## Changes 1. Advance `.release-reconciled-version` from `0.9.1` to `0.10.0`. 2. Replace the pending v0.10.0 archive state with concise, independently-read-back facts. 3. Update the archive index from stable-delivery handoff to completed external reconciliation. 4. Document and test the rule that release PRs list tracked issues only in non-closing prose: the Release workflow is their sole post-receipt closure owner. 5. Correct the closed #185 PR body to remove the accidental closing phrase that caused #181's premature merge-time closure; this does not mutate any published artifact. ## Local validation and self-review - `uv run pytest tests/test_operations_docs.py -q`: **31 passed** - `uv run ruff format --check tests/test_operations_docs.py`: passed - `uv run ruff check tests/test_operations_docs.py`: passed - `git diff --check origin/main...HEAD`: passed - `scripts/gitleaks.sh f33674e HEAD`: passed - Full scope review confirms exactly five files, all closure documentation/marker/test surfaces. No OCR or Codex Security rerun is appropriate for this no-release closure; the sole authorized final OCR review was already completed for the feature range, while hosted CI will validate this exact documentation head.
This branch was successfully deployed
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.
Scope
Prepare and authorize stable toolkit v0.10.0 for the completed OCR 1.11.6
qualification and standalone local-provider work tracked by:
This release PR contains repository-side preparation only. Stable publication
and external reconciliation remain pending until this exact PR is merged and
the protected Release workflow completes.
Reviewed implementation
d805df19a4f1e593a223b5a172b651c28209a7349cfa6b645119ed9230e790cca585376dd906dacc9cfa6b645119ed9230e790cca585376dd906dacc1192787b8a150964f0d99d832552273019163ac0Development publication
wheel/sdist installation smoke all passed. This is a development artifact,
not stable delivery.
Release preparation
0.10.00.10.11788952887[181, 182]CHANGELOG.md.0.10.0.docs/engineering/execution_history/releases.md#plan-toolkit-0-10-0withstable external delivery pending.
.release-reconciled-versionintentionally remains0.9.1untilindependent external readback is complete.
Release validation
scripts/quality.sh check: 1,712 tests, 408 subtests, 86.72% coverage.uv lock --check, OCR manifest validation,pip-audit, release-note extraction,git diff --check, and pinnedGitleaks 8.24.3 passed.
passed Twine. Wheel SHA-256:
8254b332993582d921c5ac12fc14e7e6496a85779a652ec3c3d215ba0740f1f1;sdist SHA-256:
5f0aa399cb2458e208ac5e7ae16e8b78f92fc493cc3a37fca11e4d63ae060e45.ocr-ci --helpsmoke checks.1.11.6 and
openai/gpt-5.6-terra; it is not repeated for release metadata.Post-merge gates
The protected Release workflow must independently prove registry bytes, PEP 740
provenance, GitHub attestations, annotated tag target, immutable GitHub Release
and exact assets, the release receipt, supported-Python registry installs, and
Actions-owned receipts for the tracked release issue set after immutable receipt
readback. After compact independent readback and milestone closure, one protected
documentation-only no-release reconciliation PR will record those facts and advance
.release-reconciled-versionwithout producing another stable release.