ci: pin codex-action to v1.11 - #1667
Merged
Merged
Conversation
junmo-kim
force-pushed
the
fix/codex-action-pin
branch
from
August 21, 2026 16:00
a34005b to
428e546
Compare
…-home The floating @v1 tag picked up v1.12, whose protected-run validation rejects model_providers.* overrides passed through codex-args under drop-sudo, breaking all three Codex workflows. Pin the action to v1.12 and seed a trusted codex-home config.toml with the same settings in an earlier step instead - the action preserves existing config content.
junmo-kim
force-pushed
the
fix/codex-action-pin
branch
from
August 21, 2026 16:01
428e546 to
bec4607
Compare
Contributor
Author
|
@tiann This PR fixes the repo-wide |
This was referenced Aug 22, 2026
junmo-kim
added a commit
to junmo-kim/hapi
that referenced
this pull request
Aug 22, 2026
tiann#1667 pinned @v1.12 and moved the flaky-relay stream retry tuning from codex-args into a seeded codex-home config.toml, but the action appends its own [model_providers.codex-action-responses-proxy] table instead of merging, so every Codex workflow fails with a TOML duplicate key error. The overrides cannot be expressed on v1.12 at all. Pin all three workflows to v1.11, the last release that accepts these deliberate codex-args overrides under drop-sudo, restoring the original behavior.
tiann
pushed a commit
that referenced
this pull request
Aug 23, 2026
#1667 pinned @v1.12 and moved the flaky-relay stream retry tuning from codex-args into a seeded codex-home config.toml, but the action appends its own [model_providers.codex-action-responses-proxy] table instead of merging, so every Codex workflow fails with a TOML duplicate key error. The overrides cannot be expressed on v1.12 at all. Pin all three workflows to v1.11, the last release that accepts these deliberate codex-args overrides under drop-sudo, restoring the original behavior.
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
2 participants
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.
All three Codex workflows (
codex-pr-review,codex-mention-response,issue-auto-response) have been failing since codex-action v1.12 landed (~2026-08-20 16:00 UTC): its new protected-run validation rejects the deliberatemodel_providers.codex-action-responses-proxy.*stream-retry overrides incodex-argsunderdrop-sudo.This pins all three workflows to v1.12 and moves the retry tuning into a trusted
codex-homeconfig.toml seeded by an earlier step — the action preserves existing config content, so the settings survive intact and the validation is satisfied. Pinning also stops the workflows from floating, which is what turned an upstream release into a repo-wide outage.