Repository navigation
chore(codex): release v2.1.0 - #219
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: cefc7f970d
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "Codex (@codex) address that feedback".
| { | ||
| "name": "trace-codex", | ||
| "version": "2.0.2", | ||
| "version": "2.1.0", |
There was a problem hiding this comment.
When this release commit is merged, both CI and the publication run fail because src/plugins/codex/validate.sh:66-71 requires the hook set to equal a list that omits the existing Interrupt and SessionEnd hooks. I reproduced this with make validate-codex, which exits at that assertion; moreover, _release.yml creates the source tag/release before publish.sh:48-52 invokes the failing validator, leaving a partially recorded release that cannot deploy from the required exact merge SHA. Fix the validator on main and regenerate this release commit before approving the version bump.
AGENTS.md reference: AGENTS.md:L104-L108
Useful? React with 👍 / 👎.
Prepare
codexversion2.1.0.Production destination:
braintrustdata/braintrust-codex-plugin.Cursor releases also publish
braintrustdata.braintrustto Open VSX using trusted publishing.Human approval and merge into
mainauthorize tagging the merge commit and publishing this version to the production destination. This preparation does not tag or deploy anything.