ci: make release child dispatch idempotent#102858
Merged
Merged
Conversation
Contributor
Author
|
Land-ready proof for exact head
The dispatch contract now covers CI, Plugin Prerelease, Release Checks, Performance, and focused npm Telegram. Ambiguous POST failures are never retried; exact child correlation adopts a single accepted run and fails closed on duplicates. |
Contributor
Author
|
Merged via squash.
|
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 10, 2026
steipete
added a commit
that referenced
this pull request
Jul 10, 2026
Backports the release pipeline speedups from main (ace2407 and ancestors) so the 2026.7.1 train benefits immediately: - metadata-only evidence reuse with input/harness/child-run matching - Docker runtime-assets preflight runs in parallel with lanes - release/* umbrella runs supersede in-progress duplicates - beta profile treats live-provider suites as advisory Syncing the umbrella workflow also picks up the main-only dispatch idempotency and transient-read retries (#102858, #102896).
steipete
added a commit
that referenced
this pull request
Jul 10, 2026
…ella The synced Full Release Validation umbrella dispatches children with a dispatch_id and adopts runs by exact name (#102858), so ci.yml, npm-telegram-beta-e2e.yml, and plugin-prerelease.yml need the matching input; applies that commit's hunks plus its ci-workflow-guards update, syncs scripts/ci-live-command-retry.sh, and ports the guard test blocks that pin the synced workflow text.
wheakerd
pushed a commit
to wheakerd/clawdbot
that referenced
this pull request
Jul 15, 2026
(cherry picked from commit 11dda0e)
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
1 participant
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.
What Problem This Solves
Full Release Validation could fail when GitHub accepted a child
workflow_dispatchrequest butgh workflow runreturned an HTTP 500. In run 29019783765, the plugin dispatcher failed while the exact child run 29020317666 had already been created and continued successfully. Retrying that POST would risk duplicate release matrices.Why This Change Was Made
dispatch_idand unique run name.User Impact
Release validation no longer reports a false failure or creates duplicate child matrices when GitHub returns an ambiguous dispatch response. Existing manual workflow titles and child test behavior remain unchanged when no parent dispatch identifier is supplied.
Evidence
tbx_01kx3ghv24pb17nzzsm5zaa893: 92 focused workflow tests passed.node scripts/check-workflows.mjs: actionlint, zizmor, and workflow guards passed.oxfmt --check: all changed workflow/test files passed.git diff --check: passed.