feat(github-action)!: Update codex-/return-dispatch (v3.0.3 → v4.0.1) - #137
Open
home-infrastructure-renovate[bot] wants to merge 1 commit into
Open
feat(github-action)!: Update codex-/return-dispatch (v3.0.3 → v4.0.1)#137home-infrastructure-renovate[bot] wants to merge 1 commit into
home-infrastructure-renovate[bot] wants to merge 1 commit into
Conversation
denniseffing
force-pushed
the
main
branch
4 times, most recently
from
July 31, 2026 14:44
df56dce to
de2bdf7
Compare
home-infrastructure-renovate
Bot
force-pushed
the
renovate/codex-return-dispatch-4.x
branch
from
August 13, 2026 00:56
edceb89 to
4e630fd
Compare
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:
v3.0.3→v4.0.1Release Notes
codex-/return-dispatch (codex-/return-dispatch)
v4.0.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v4.0.0Compare Source
Github finally added proper support for returning the run ID when dispatching: https://github.blog/changelog/2026-02-19-workflow-dispatch-api-now-returns-run-ids/
This release focuses on using the changes made to the dispatch endpoints, removing the overhead of trawling/polling
for the distinct ID previously required.
Server support
return_run_detailsfield with a400, and the action fails with a message explaining the requirement.Removed inputs
distinct_idworkflow_timeout_secondsworkflow_job_steps_retry_secondsdistinct_idis no longer injected into the dispatched workflow's inputsYour receiving workflow no longer needs the
distinct_id:on: workflow_dispatch: inputs: - distinct_id: - required: true custom_inputs: jobs: test: runs-on: ubuntu-latest steps: - - name: echo distinct ID ${{ inputs.distinct_id }} - run: echo "${{ inputs.distinct_id }}"Migration checklist
distinct_id,workflow_timeout_seconds, andworkflow_job_steps_retry_secondsfrom the
return-dispatchstep.distinct_idinput and echo step from the receiving workflow (or mark it non-required as a preliminary step)actions: write(fine-grained PAT / GitHub App /GITHUB_TOKEN) orreposcope (classic PAT) is needed.🚀 Features
View changes on GitHub
v4Compare Source
Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 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 Mend Renovate.