Skip to content

runner-exceptions: github-policy's hosted and reusable workflows (WI-3087) - #10

Open
thedancingdeveloper wants to merge 1 commit into
mainfrom
vogt-agent/ci-guardrails-runner-exceptions
Open

thedancingdeveloper wants to merge 1 commit into
mainfrom
vogt-agent/ci-guardrails-runner-exceptions

Conversation

@thedancingdeveloper

Copy link
Copy Markdown
Contributor

Precursor to #9. It carries only #9's commit fe43624, cherry-picked.

Why a separate PR: the required runner-policy gate reads runner-exceptions.json from github-policy main (runner-policy-reusable.yml, the second checkout uses ref: main). So exceptions added on #9's branch can't suppress #9's own findings, and #9 stays red (run 41534830234) even though the gate passes locally with the branch's file.

What it adds: dated exceptions, expiring 2027-04-30, for github-policy's new workflows:

  • audit.yml and ci-auditor.yml: hosted runners in a public repo (operator decision, 2026-11-02).
  • The reusable policy.yml, rust-ci.yml, image.yml and release-dry-run.yml: the legacy line parser reads their runs-on input key as a runner selection, and it flags dynamic runs-on.

ci-auditor CI-05 judges these files instead.

Checked: scripts/runner_policy.py on this branch gives ok. On #9's tree with these exceptions it gives ok: 8 workflow file(s) audited, 13 excused.

Merge order: merge this first (rebase), then re-run runner-policy on #9. #9's rebase merge drops the duplicate commit.

🤖 Generated with Claude Code

…3087)

The legacy runner-policy gate (still the required check here) predates the
2026-11-02 decision allowing hosted runners in public repos, and its
line-based parser reads a reusable workflow's `runs-on` input key as a
runner selection. Dated exceptions until the legacy gate is retired;
ci-auditor CI-05 judges these files.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant