fix: recover Codex review with the v1.11 action pin - #22
Merged
Conversation
Owner
Author
|
Ordinary CI passed: https://github.com/dexsword/dextech/actions/runs/34144428441 on head |
dexsword
enabled auto-merge (squash)
September 7, 2026 16:47
dexsword
disabled auto-merge
September 7, 2026 16:49
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Codex action v1.12 can leave Linux reviews hanging after Codex has produced its completed result. Roll back only the action pin to the verified v1.11 commit
52fe01ec70a42f454c9d2ebd47598f9fd6893d56.Upstream: openai/codex-action#150 and openai/codex-action#151. This uses the released v1.11 commit, not the unmerged repair PR. CLI
0.153.4, the 20-minute timeout, reasoning effort, read-only/drop-sudo configuration, permissions, triggers and all review/auto-merge controls are unchanged. Exactly one workflow line changes.Validation: clean npm ci; all 56 Node tests on current main; 9 deployment-control tests; CI smoke and synthetic health; actionlint; ShellCheck; YAML, JSON Schema, TOML and JavaScript/Python/shell syntax checks; production audit. All passed. Audit: zero high/critical, one existing low and one moderate advisory.
Bootstrap: pull_request_target uses main, so this PR's automatic review still loads the broken v1.12 pin. That review must not be treated as a successful check or repeatedly retried. Ordinary CI must pass and a human must review this one-line rollback before an authorized break-glass merge. The live Protect main ruleset is enforcing all required checks and currently has no bypass actors; no break-glass procedure was found in the repository docs. No ruleset, setting, secret or production change is part of this PR.
After the human-approved recovery reaches main, synchronize PR #17 with that main (its strict base/ancestry guards require this), update its pin documentation, and run its base-controlled review using v1.11. Verify the action's end marker, downstream jobs starting automatically, and no manual cancellation. Then validate with a small meaningful PR. Preserve all required checks and remove any temporary authorized exception after recovery.
This PR has not been merged. A human merge to main will trigger the existing production deployment workflow; plan that separately. PR #17's SHA placement, stale-run and duplicate-check fixes remain separate.