Repository navigation
fix(ci): separate main readiness from qualified publication - #206
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
After #205 changed plugin implementation bytes, main’s nonpublishing Release workflow tried restoring the old qualified 10.0.0 artifact and failed its exact-content check. Main should build the development candidate and report readiness without claiming it is qualified.
Use the existing release decision to reserve v2 restoration in the verification job for publishing invocations. Main keeps metadata/canary dry-run reporting. The publishing job, strict artifact validators, historical evidence, and 9.x behavior are unchanged.
Proof: the new main regression fails against the original workflow and passes with this correction; tag and publishing controls still restore exact artifacts and reject mismatches. All 45 focused tests, typecheck, actionlint, and canonical push preflight pass (5,746 tests, 27 skipped, zero failures). Actual workflow shell preparation/readiness reports the changed candidate NOT VERIFIED without failure.
Reviewed with sol-loop: 1 round with gpt-6.1-sol on high. Sol verdict: approved.
Created with gpt-6.1-sol in T3 Code through the Codex harness.