Track Codex 0.145.0 candidate - #138
Conversation
5fd37b7 to
675522b
Compare
![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: 5fd37b778c
ℹ️ 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.144.5", | ||
| "candidate_state": "published", | ||
| "candidate_state_status": "ready_to_publish", | ||
| "candidate_state_status": "build_dispatched", |
There was a problem hiding this comment.
Set this to codex_build_dispatched when the Codex Android build has been dispatched. In the inspected .github/workflows/auto-stage-candidate.yml, the branch is staged only when candidate_state_status exactly equals codex_build_dispatched (lines 116–125); with build_dispatched, every completed 0.145.0 build is classified as should_stage=false, so the manifest and package never advance to ready_to_publish.
Useful? React with 👍 / 👎.
| "support_status": "active", | ||
| "latest_audited_version": "0.144.6", | ||
| "latest_candidate_version": "0.144.6", | ||
| "latest_candidate_version": "0.145.0", |
There was a problem hiding this comment.
Update packages/codex-termux/config/codex-termux-release-manifest.json alongside this field. This commit leaves that bundled manifest at candidate 0.144.6 and ready_to_publish, despite scripts/update-codex-candidate-manifest.js and the version-watch workflow explicitly updating and committing both manifests together. Auto-stage later changes only the root manifest and package.json, while config/ is included in the npm package, so a subsequently published 0.145.0 candidate would carry stale candidate metadata.
Useful? React with 👍 / 👎.
|
Build for 0.145.0 succeeded. Manifest and package.json staged as ready_to_publish on |
…ge-candidate.yml package-manifest gap)
1 participant
Automated upstream Codex intake.\n\n- upstream latest: 0.145.0\n- private Android build dispatched\n- manifest candidate state: build_dispatched