Repository navigation
docs: record the published 0.0.95 release - #225
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.
Codex installation component 0.0.95 is published at 2026-10-26T07:21:48Z from signed tag 0.0.95 / source bbb0077. Replace only the pending heading with its actual release/date; preserve the entry and every historical ledger entry.
Release workflow 40284868695, PyPI 40284868774 and crates 40284868728 succeeded. Public readback matched six binary digests against SHA256SUMS, provenance metadata against the tagged source, six non-yanked wheels and the non-yanked crate. Native consumer cryptographic/install acceptance remains separate.
Only CHANGELOG.md changes. Source-only diff review and git diff --check passed; no local component build/runtime. Exact ledger head 1e3a30b passed all 27 accepted existing CI/security checks, including the three-OS component and source-package gates. Rollback is a normal corrective ledger PR; published tag/assets remain immutable. This does not authorize an ai-stp client release.