ci: refresh ci concurrency group

This commit is contained in:
Peter Steinberger
2026-04-22 15:53:37 +01:00
parent ed97cc7210
commit fb70d3ac67
2 changed files with 2 additions and 1 deletions

View File

@@ -54,6 +54,7 @@ On pushes, the `checks` matrix adds the push-only `compat-node22` lane. On pull
The slowest Node test families are split into include-file shards so each job stays small: channel contracts split registry and core coverage into eight weighted shards each, auto-reply reply command tests split into four include-pattern shards, and the other large auto-reply reply prefix groups split into two shards each. `check-additional` also separates package-boundary compile/canary work from runtime topology gateway/architecture work.
GitHub may mark superseded jobs as `cancelled` when a newer push lands on the same PR or `main` ref. Treat that as CI noise unless the newest run for the same ref is also failing. Aggregate shard checks use `!cancelled() && always()` so they still report normal shard failures but do not queue after the whole workflow has already been superseded.
The CI concurrency key is versioned (`CI-v2-*`) so a GitHub-side zombie in an old queue group cannot indefinitely block newer main runs.
## Runners