Skip to content

Prepare the v0.2.0 stable release - #56

Merged
Hyper66666 merged 1 commit into
mainfrom
codex/v0-2-release-sequence
Jul 26, 2026
Merged

Prepare the v0.2.0 stable release#56
Hyper66666 merged 1 commit into
mainfrom
codex/v0-2-release-sequence

Conversation

@Hyper66666

Copy link
Copy Markdown
Owner

Summary

  • advance all workspace tools and runtime crates from

Candidate two proved the frozen v0.2 Stable surface on all four release hosts, including package installation, TLS composition, compatibility, and rollback. Advance the coherent workspace version to 0.2.0 and make the user-facing truth sources describe that verified release surface without promoting experimental backends.

Constraint: Stable publication must use a new one-SHA main matrix and a complete four-target tag run; RC2 results establish compatibility but cannot stand in for the stable artifact set.

Rejected: Tag the RC2 commit directly as v0.2.0 | Its workspace identity is 0.2.0-rc.2 and its documentation still describes prerelease state.

Confidence: high

Scope-risk: moderate

Directive: Do not mark stable publication or archive this change until the v0.2.0 tag assets, provenance, installed smokes, and rollback to RC2 are independently audited.

Tested: cargo fmt --all -- --check; cargo test -p sgc --test language_reference_doctests -- --nocapture --test-threads=1; cargo test -p sgpm -- --test-threads=1; cargo clippy -p sgpm -p sgc --all-targets -- -D warnings; openspec validate v0-2-release-candidate-closure --strict; openspec validate --all --strict

Not-tested: Stable main/tag host matrices and published v0.2.0 assets; those are the next transactional release gates.

Co-authored-by: OmX <omx@oh-my-codex.dev>
@Hyper66666
Hyper66666 merged commit 92c8f39 into main Jul 26, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant