Release v0.9.1 - #179
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.
Scope
Prepare and authorize stable toolkit v0.9.1 for the completed OCR 1.11.4/1.11.5 qualification and diagnostic-safety work tracked by:
This release PR contains repository-side release preparation only. Stable publication and external reconciliation remain pending until this exact PR is merged and the protected Release workflow completes.
Reviewed implementation
b47fa551b5de42dcfe9cd5b316a32f4184525be6de9055e699ff8a7bc0806c6eae5bdf6666e95160de9055e699ff8a7bc0806c6eae5bdf6666e951604a3847af59b7597975e0daeb1f2867cee3077d01Development publication
0.9.1.dev872cb519f4e54b25bf1e64416fdacd17ccbba7eba99a758ec0437bbd3021ba28299872ea9fcb8c81fd42264af325705e717f311265becffeab192e6ec28c07fd0eReview receipts
ae0a9ac..029cdf0: 9 selected, 9 completed, 0 failed/reused/waived, 77 tool calls, no GitLab posting; result SHA-2563a5374a846c3033734da0c66d7a9032e54043e96b8a8322fd9724f37691c2873.5db2da0c-3f84-46a4-b4dd-cf3521fd1402and90628f3c-10aa-4ce9-a3fa-b8c497e504d4: 8/8 combined surfaces closed, 0 reportable findings.Release validation
uv lock --check, diff checks, and pinned Gitleaks passed.c1343b2eba77378d2c4a143bad445e47a762e0e67e3a916cb8f69e2f748f45fb32ef050255aa9dc0056935bb4280fde9ace0490df0a0affb82a98655f14ce994Release preparation
0.9.10.9.21788768251[176, 177]CHANGELOG.md.0.9.1.docs/engineering/execution_history/releases.md#plan-toolkit-0-9-1with stable external delivery pending..release-reconciled-versionintentionally remains0.9.0until independent external readback is complete.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, release receipt, supported-Python registry installs, Actions-owned issue receipts, issue/milestone closure, release-branch cleanup, and synchronized
main. A separate protectedno-releasereconciliation PR will then record those facts and advance.release-reconciled-versionwithout creating or mutating another stable release.