ci: drop the codex-home config seed that breaks TOML parsing - #1670
Merged
Conversation
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.
junmo-kim
force-pushed
the
fix/codex-action-seed-duplicate
branch
from
August 22, 2026 10:31
140a980 to
8a12e64
Compare
Contributor
Author
|
@tiann Sorry, the fix from yesterday (#1667) didn't hold. The config seed it added collides with the action's own |
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.
Follow-up to #1667: its codex-home config seed doesn't work — the action appends its own
[model_providers.codex-action-responses-proxy]table toconfig.tomlinstead of merging, so every Codex workflow fails with a TOML duplicate key error (verified on an external PR run). And since v1.12 rejects the flaky-relay retry overrides incodex-args, the tuning cannot be expressed on v1.12 at all.This pins all three workflows to v1.11, the last release that accepts those deliberate overrides under
drop-sudo, and drops the seed — restoring the original behavior fully intact. Once the action either merges existing config or exposes first-class inputs for proxy tuning (same root cause as openai/codex-action#80), upgrading should be straightforward.