BREAKING CHANGE(github-action): Update Codex-/await-remote-run action v2.1.0 → v3.0.0 - #3329
Open
truecharts-admin wants to merge 1 commit into
Open
BREAKING CHANGE(github-action): Update Codex-/await-remote-run action v2.1.0 → v3.0.0#3329truecharts-admin wants to merge 1 commit into
truecharts-admin wants to merge 1 commit into
Conversation
truecharts-admin
requested review from
Crow-Control and
alfi0812
as code owners
August 26, 2026 12:43
Crow-Control
approved these changes
Aug 26, 2026
Crow-Control
left a comment
Member
There was a problem hiding this comment.
Auto approved automated PR
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.
This PR contains the following updates:
3dbfaaf→bb04140Add the preset
:preserveSemverRangesto your config if you don't want to pin your dependencies.Release Notes
Codex-/await-remote-run (Codex-/await-remote-run)
v3.0.0Compare Source
v3 now more broadly applies the usage of etags, reducing the number of requests that contribute to usage limits, and also brings
improvements driven by requests from the community (and probably organisations using it in a trench coat).
Await specific jobs
Thanks for requesting this, @jbelien (#212)
The new
jobsinput awaits named jobs within the run rather than the run itself, one name per line.Useful when the remote run continues past the part you actually need, such as gating on
buildwhile itsdeploycarries on.Resolves once every listed job has concluded with
success, leaving the rest of the run in flight. Any other conclusion,skippedincluded, fails immediately. Names must match what GitHub reports rather than the workflow's job key, so a matrix job is
build (ubuntu-latest, 20)and a reusable workflow call isbuild / inner-job-name. A name that never matched fails once the run concludes,listing every job the run did produce.
Cancel the remote run
Thanks for requesting this, @oskar-s9s (#215)
Timing out previously left the remote run going, which is a problem when your workflow then tears down something that run depends on.
Set
cancel_timeout_secondsto request cancellation once that much time has elapsed:It must be less than
run_timeout_seconds, the difference being how long the action keeps polling to observe the resultingcancelledconclusion. Combined with
jobs, an awaited job failing also cancels the run, as it can no longer succeed. A run whose awaited jobs allsucceeded is never cancelled.
Cancellation is a write and
GITHUB_TOKENcannot be grantedActionswrite on another repository, so this input always needs a PAT withActionswrite.Fewer requests against your rate limit
The etag handling was rewritten as a
fetchwrapper around the Octokit client, so every request the action makes is now conditional and a304costs nothing against the primary rate limit. Previously only the run state fetch was covered. The wrapper preserves any proxy fetch@actions/githubresolved, so self-hosted runners behind a proxy keep working.Upgrading from v2
There are no intended breaking changes. Bumping the tag should be sufficient. Two behaviours changes worth noting:
failure, so acancelledortimed_outjob now gets reported.skippedjobs are excluded as they bury the causal failure.Cancellation and awaiting jobs are both opt-in. Leave both inputs unset and the action behaves as it did in v2.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.