ci: cancel superseded workflow runs on PR pushes#581
Merged
Conversation
Add a top-level concurrency group (github.workflow + github.ref) to the push/pull_request workflows that lacked one, cancelling in-progress runs only for pull_request events. Reduces wasted runner minutes from superseded PR pushes while staying safe for main/tag deploy paths. Part of the org CI-cost audit. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
claude-dataviking
requested review from
openclaw-dv and
the-data-viking
as code owners
July 18, 2026 14:49
claude-dataviking
added a commit
that referenced
this pull request
Jul 18, 2026
#583) PR #581 merged without a semver label, so its Auto Semver Tag run failed (as designed). The recovery rerun — after labeling semver:minor — got as far as pushing the bump commit, but the rerun replays the original event payload: its checkout pinned main at PR #581's merge, and main has since advanced (PR #582), so the push was rejected non-fast-forward. Reruns always replay the same stale SHA, so that path cannot succeed anymore. This PR takes auto-tag.yml's documented escape hatch instead: pre-bump every version artifact to 1.6.0 in the PR itself. On merge, the auto-tag run finds the artifacts already at the new version, skips the release-bot push, and proceeds straight to tag + GitHub Release + publish dispatch. Rendered via the same scripts auto-tag runs (render_site.py, render_site_markdown.py, render_server_card.py). Also picks up server.json, which render_server_card.py rewrites but auto-tag's git-add list does not stage. Co-authored-by: njord <njord@njords-Mac-mini.localdomain> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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.
From the org CI-cost audit: cut wasted GitHub Actions runner minutes.
Every
push/pull_requestworkflow that lacked a top-levelconcurrency:key now gets one:cancel-in-progressis scoped topull_requestevents only, so a superseded PR push cancels its in-flight run, while pushes tomainand tag-triggered deploy/publish/release runs are never cancelled (they serialize instead of aborting).Workflows changed:
ci.yml,codeql.yml,dependency-review.yml,docker.yml,publish-test.yml.Left untouched:
auto-tag.ymlandpublish.yml(already define concurrency).🤖 Generated with Claude Code