chore(cli-version): verify codex against 0.149.0 - #922
Merged
Conversation
All three gates pass against the real 0.149.0 binary. Gate A (contract): 380 -> 401 schema files, ServerNotification 72 -> 75, ClientRequest 141 -> 150, nothing removed and no enum value dropped. Gate B (live e2e): 11/11, 264.78s. The suite's own log proves it ran the candidate rather than the installed binary -- 'direct CLI version detected cli=codex version=codex-cli 0.149.0', with the matching drift lines that only appear when the binary disagrees with the constant. Run through a PATH shim; the operator's own CLIs were not touched. Gate C (release notes): CLEAR over 255 notes, 9 filtered as risk verbs touching none of our dependency tokens, 0 REVIEW items. The three pinned fixtures moved to versions the constant has not passed rather than being loosened, and the literal verified-release assertion now names 0.149.0 so a future bump that forgets to re-verify still breaks the test. Record: ~/aion/protocols/samples/codex-cli/0.149.0/
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.
Moves
VERIFIED_CODEX_VERSIONfrom 0.148.0 to 0.149.0. All three gates pass against the real binary.ServerNotification72 → 75,ClientRequest141 → 150, nothing removed, no enum value droppedThe candidate is proven from the suite's own log
A green run against the binary you meant to replace certifies the wrong version, so this is checked rather than assumed:
The drift lines only appear because the candidate disagrees with the constant that had not been bumped yet. The run went through a PATH shim (
npm install @openai/codex@0.149.0into a temp dir); the operator’s own CLIs were not modified.Tests
Three pinned fixtures in
cli_versionnamed versions the constant has now passed. Each was re-pointed above the new constant rather than loosened, and the literal verified-release assertion now namescodex-cli 0.149.0, so a future bump that forgets to re-verify still breaks the test.cargo test -p aionui-session --lib cli_version: 13/13. Clippy clean, fmt clean.Note on 0.147.0
Still deliberately unverified — it never completes a turn (
httpStatusCode: null, three observations). The gate walks over it rather than through it, so it never becomes an accepted floor.Record:
~/aion/protocols/samples/codex-cli/0.149.0/Constants and record only — no source change.