ci: open release PRs ready for review - #5227
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. |
|
Codex Review: Something went wrong. Try again later by commenting “@codex review”. ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
|
@codex review |
🛡️ Codex Security Review · Automatically triggeredSecurity review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
![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: 37dbb52fbf
ℹ️ 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".
markstuart-oai
left a comment
markstuart-oai
left a comment
There was a problem hiding this comment.
Reviewed 37dbb52fbf6bc8c7f996a3ec29c87686b5666576. No actionable findings.
The pinned Release Please action carries the explicit draft-pull-request: false through to PR creation. The release instructions and existing config assertion agree with that change, while snapshot preparation, required checks/code-owner review, and manual publication remain required. I also verified that the existing release PR #5226 is already open and non-draft, addressing the earlier migration concern.
Validation: source review of all three changed files, the pinned action's configuration path, and the surrounding release/snapshot workflows. All 22 hosted checks pass on this commit, including the Python/Windows test matrices, packaged/prospective contract checks, lint/type checks, docs, and CodeQL. I did not run tests or builds locally.
2 participants
Summary
This pull request makes Release Please open release PRs ready for review by setting
draft-pull-requesttofalse. It updates the existing config assertion and maintainer guidance so API snapshot regeneration remains required before merging, alongside checks and code-owner approval. Versioning, changelog sections, workflow permissions, and manual publication are unchanged.Test plan
draft: falseand consistent project, lockfile, manifest, and source versions.Checks
.agents/skills/code-change-verification/scripts/run.sh.