You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The contract step: the size and architecture labels become required, with no defaults. A swap can then only happen between runners of the same shape. Rollout order:
Open PRs on every repo that already uses our runners (at least zeroae/ci-runner-canary and the first consumer), adding ci-cpu-4 and x64 to each moved job's runs-on. Merge them. The webhook already accepts the labels, so nothing breaks.
Drop the defaults in the webhook. A job without a size label, or without an architecture label, is outside the contract.
Acceptance criteria
Consumer PRs are merged before the webhook change deploys. List them on this ticket.
Webhook tests: a missing size label or a missing architecture label is outside the contract.
make hand-launch requires a size and an architecture.
The README's examples show the full contract for each capacity, and the traps table covers "missing size or architecture label".
Consumer draft PRs (do not merge until the integration branch, with the expand step from #22/#24, is deployed): zeroae/ci-runner-canary#2, zeroae/foresight#1194. The webhook change is on ticket/26-require-labels and is held out of the integration branch until those merge.
Consumers (swept via the runner group API: ci-runner-canary, foresight, zae-zcm): ci-runner-canary#2 merged; zae-zcm#37 merged and its main run passed on our runners with the new labels; foresight#1194 ready but not merged, because its gate job runs on ubuntu-latest and the org's GitHub-hosted billing block stops it from starting. The webhook change (ticket/26-require-labels, cabcc32) stays out of the integration branch until foresight#1194 merges.
Activity
sodre commentedon Nov 14, 2026
Consumer draft PRs (do not merge until the integration branch, with the expand step from #22/#24, is deployed): zeroae/ci-runner-canary#2, zeroae/foresight#1194. The webhook change is on
ticket/26-require-labelsand is held out of the integration branch until those merge.sodre commentedon Nov 14, 2026
Consumers (swept via the runner group API: ci-runner-canary, foresight, zae-zcm): ci-runner-canary#2 merged; zae-zcm#37 merged and its main run passed on our runners with the new labels; foresight#1194 ready but not merged, because its gate job runs on ubuntu-latest and the org's GitHub-hosted billing block stops it from starting. The webhook change (
ticket/26-require-labels, cabcc32) stays out of the integration branch until foresight#1194 merges.Merge ticket #26: require the full label contract
Webhook test: a Fargate job needs its size and architecture too