Prepare v0.3.2 release candidate - #131
Merged
Merged
Conversation
Release and wheel workflows now verify the pushed tag matches the Cargo package version before any build runs, with contract coverage protecting both workflows. Constraint: Keep the canary as the first release gate and avoid adding dependencies Rejected: Trust tag naming convention alone | a mismatched tag can publish artifacts under the wrong version Confidence: high Scope-risk: narrow Reversibility: clean Directive: Update Cargo.toml and the release tag together for every publication Tested: github_canary_contract, fmt, diff check Not-tested: Live GitHub Actions execution
The repository already publishes v0.3.1, so this candidate advances the package and lockfile versions together for the next compatible release. Constraint: Release workflows now reject tags that do not match Cargo.toml Rejected: Reuse 0.3.0 or 0.3.1 | those versions are already represented by existing release history Confidence: medium Scope-risk: narrow Reversibility: clean Directive: Create the release from tag v0.3.2 after the candidate is reviewed Tested: cargo check --all-targets --all-features Not-tested: crates.io publication and tag push
The current upstream branch already contains the native-stack repair and coverage batches, but its generic PR merge path still downgraded a native stack to the legacy single-PR endpoint on HTTP 404. Route native merges through an async-only helper while retaining the legacy fallback for ordinary PRs. Constraint: GitHub's stacked merge API is asynchronous and the legacy endpoint cannot represent an atomic stack merge Rejected: Rebase the whole transfer commit onto current main | it conflicts with upstream's inline-test architecture and would discard current repair work Confidence: high Scope-risk: narrow Reversibility: clean Directive: Do not route native-stack merges through merge_pr without proving the async-only invariant Tested: targeted GitHub and command-layer 404 regression tests Not-tested: full suite and release workflow checks after this commit Co-authored-by: OmX <omx@oh-my-codex.dev>
rohoswagger
force-pushed
the
codex/release-candidate
branch
from
August 6, 2026 19:46
807ef8b to
ffbfe22
Compare
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.
Part of a stack managed by
ez.