Skip to content

chore: upgrade Codex to 0.162.0 - #13

Closed
reonokiy wants to merge 1 commit into
mainfrom
chore/codex-0.162.0
Closed

reonokiy wants to merge 1 commit into
mainfrom
chore/codex-0.162.0

Conversation

@reonokiy

@reonokiy reonokiy commented Oct 8, 2026

Copy link
Copy Markdown
Owner

Summary

Upgrade directly from current main (8ae930e) to stable Codex 0.162.0.

  • Release: https://github.com/openai/codex/releases/tag/rust-v0.162.0
  • Annotated tag object: 1f3f93473394b620b35580859b7e6864f7a9f948
  • Peeled release commit: c1382380de69521303b416720a52f42d51af6248 (not upstream main HEAD).
  • Update all Codex dependency pins, Cargo.lock seeded from the release lockfile, release asset SHA-256 baselines, version constants, vendor crate and related documentation.
  • Preserve gateway raw transport extensions; rebase the patch onto upstream's shared WebSocket connector. New upstream modules/tests are included unchanged.
  • Match upstream's developer-message base-instruction prefix for standard and lite requests, preserve stable message IDs, and omit empty lite additional_tools.
  • Update regression assertions. Explicitly close stdin for noninteractive official CLI tests: 0.162.0 otherwise waits for additional input in this environment.

Supersedes the upgrade targets in #12 (0.161.0) and #6 (0.160.1); neither PR is closed or modified.

Validation

All final commands below exited 0:

  • cargo setup: verified pinned source, official CLI and companion SHA-256 checksums; installed locked Python clients.
  • cargo fmt --all -- --check
  • cargo check --workspace --all-targets --locked
  • cargo clippy --workspace --locked --all-targets -- -D warnings
  • cargo test --workspace --locked: 297 passed, 12 ignored, 0 failed.
  • cargo test --locked --test gateway actual_ -- --ignored: all 5 passed, including actual official CLI HTTP/WebSocket and image/search, plus Python SDK compatibility suites.
  • cargo test --locked --test source_audit -- --ignored: 1 passed; 66 pinned Codex git packages, 980 registry packages, 42 identical upstream source files and 5 identical integration-test files verified. Only the 6 documented gateway source patches plus raw.rs extension differ.
  • git diff --check: passed; reviewed dependency/vendor/application/test/doc diffs and scanned for private-key/token patterns.

Failures encountered and fixed

  • Initial patch rejected the old WebSocket factory signature; adapted to upstream's shared connector.
  • Initial compilation identified removed requires_separate_message and ResponsesApiRequest.instructions; migrated to upstream's new instruction representation.
  • Intermediate regression/SDK assertions assumed old input offsets and empty additional_tools; corrected and reran, retaining original failure logs.
  • Official CLI tests initially timed out after “Reading additional input from stdin...”; explicit null stdin fixed both CLI suites, without extending timeouts or skipping tests.
  • Cargo shim was unconfigured; used the already-installed Rust 1.95.0 toolchain via /home/coder/.cargo/bin, with no global environment changes.

Evidence and remaining validation

Logs remain on the execution host in:
/home/coder/github.com/reonokiy/codex-api-upgrade-0.162.0/artifacts/upgrade-0.162.0/

Final evidence: final-results.txt, final-{fmt,check,clippy,test,official,audit}.log, setup.log, fetch.log. Original failures: check-initial.log, test.log, previous-*.log, cli-diagnostic.log, cli-stderr.log. Source report: artifacts/protocol/source-audit.json.

Real subscription/upstream credentialed suites were not run. Local container build/smoke/publish were not run; repository CI must validate these. Keeping this PR Draft pending those checks/review; no merge requested. Cargo reports the existing unused crossterm patch warning (not a Rust/clippy failure).

The user's original fix/json-schema-description worktree remains clean and untouched. All changes were made in a separate worktree. Recurring task T-1 was not changed.

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