Skip to content

Require the full label contract #26

Closed

Description

@sodre

Parent

#18

What to build

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:

  1. 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.
  2. 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".
  • GLOSSARY.md matches: no defaults.

Activity

  1. sodre commented on Nov 14, 2026

    @sodre
    MemberAuthor

    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.

  2. sodre commented on Nov 14, 2026

    @sodre
    MemberAuthor

    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.

  3. added 2 commits that reference this issue on Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions