Add concurrency_suffix input to check-synchronization#12
Merged
BDevParity merged 1 commit intomainfrom Apr 13, 2026
Merged
Conversation
BDevParity
commented
Apr 13, 2026
Comment on lines
-34
to
+38
| group: ${{ github.repository }}-${{ github.workflow }}-${{ github.ref }} | ||
| group: ${{ github.repository }}-${{ github.workflow }}-${{ github.ref }}${{ inputs.concurrency_suffix && format('-{0}', inputs.concurrency_suffix) || '' }} |
Contributor
Author
There was a problem hiding this comment.
Did it like this so we do not have "-" at the end if suffix is "", just so future runs have identical concurency sufix as old ones if we do not set this field
BDevParity
added a commit
to paritytech/polkadot-sdk
that referenced
this pull request
Apr 13, 2026
Each caller now passes a unique concurrency_suffix so parallel check-synchronization invocations within the same workflow run get distinct concurrency groups and don't cancel each other. Also restores check-synchronization in release-reusable-publish-packages with the concurrency suffix and inline org/killswitch guard. Depends on: paritytech-release/sync-workflows#12
EgorPopelyaev
approved these changes
Apr 13, 2026
When multiple callers invoke check-synchronization in parallel within the same workflow run, they all resolve to the same concurrency group and GitHub randomly cancels the competing jobs. Adding an optional concurrency_suffix input lets callers provide a unique value so their concurrency groups don't collide.
BDevParity
force-pushed
the
bd-add-concurrency-suffix
branch
from
1868cd9 to
b6d8f55
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
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.
Summary
check-synchronizationin parallel within the same workflow run (e.g. from a combined publish workflow), they all resolve to the same concurrency group (repo-workflow-ref) and GitHub randomly cancels competing jobs.concurrency_suffixinput (default: empty) that callers can use to make the concurrency group unique per caller.Related: paritytech/polkadot-sdk#11703
Test plan
concurrency_suffixbehave unchanged