ci: bump actions/checkout from 6.0.2 to 7.0.1 - #890
Conversation
Bumps [actions/checkout](https://github.com/actions/checkout) from 6.0.2 to 7.0.1. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@de0fac2...3d3c42e) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 7.0.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
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. |
mldangelo-oai
left a comment
There was a problem hiding this comment.
Reviewed the exact checkout 6.0.2 to 7.0.1 source and input/runtime changes against all 27 workflow uses. Existing refs and credential settings remain compatible. The Windows deadline fix is confirmed by successful full-suite runs taking approximately 33 and 36 minutes, followed by a passing inventory comparison. Current-head CI passed all 57 executed jobs, with two expected conditional skips: https://github.com/openai/codex-security/actions/runs/34641857881 . All required checks pass, no unresolved review threads remain, and the merge tree preserves the already-merged dependency upgrades. Public PR content and final CI logs reviewed.
Summary
Update actions/checkout from 6.0.2 to 7.0.1 across CI and release workflows.
Changes
persist-credentials: falsesettings.Testing
git diff --checkpassed.Risk and rollout
Checkout v7 blocks unsafe fork PR checkouts under privileged PR events. The release
workflow_runjob is restricted to successful pushes tomain; no privileged fork checkout is required. Hosted runner versions satisfy the unchanged action runtime requirement. No application or CLI changes are required. No obsolete compatibility workaround was found in the affected invocations.Public disclosure review