Repository navigation
Track Codex 0.166.0 candidate - #240
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. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 21daf7684c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "previous_stable_version": "0.165.0", | ||
| "candidate_state": "published", | ||
| "candidate_state_status": "ready_to_publish", | ||
| "candidate_state_status": "build_dispatched", |
There was a problem hiding this comment.
When the 0.166.0 build completes, .github/workflows/auto-stage-candidate.yml:120 requires candidate_state_status to equal codex_build_dispatched; the new build_dispatched value instead sets should_stage=false. Consequently, even a successful build with the correct recorded run ID cannot advance this candidate to ready_to_publish. Use the state emitted by the existing version-watch workflow.
Useful? React with 👍 / 👎.
| "support_status": "active", | ||
| "latest_audited_version": "0.165.0", | ||
| "latest_candidate_version": "0.165.0", | ||
| "latest_candidate_version": "0.166.0", |
There was a problem hiding this comment.
This commit advances only the root manifest, leaving packages/codex-termux/config/codex-termux-release-manifest.json at candidate 0.165.0 with state ready_to_publish. Even after correcting the root state, .github/workflows/auto-stage-candidate.yml:150–154 checks the packaged manifest against the incoming build version and codex_build_dispatched, so staging 0.166.0 will exit with an error. Update both manifests together using scripts/update-codex-candidate-manifest.js.
Useful? React with 👍 / 👎.
5dc192f to
fea7798
Compare
Match the state expected by the staging workflow; the build run is already recorded. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
|
Build for 0.166.0 succeeded. Manifest and package.json staged as ready_to_publish on |
Automated upstream Codex intake.\n\n- upstream latest: 0.166.0\n- private Android build dispatched\n- manifest candidate state: build_dispatched