The dead r610 pools behind alkane-fast and alkane-verify were disabled after their SSD failure, leaving only offline runners on those labels. The required source-pr / source (pull_request) gate runs on alkane-fast, so every PR to main is unmergeable, and next-build/pages jobs on alkane-verify never run.
Repoint the four jobs to the healthy GARM-backed alkane-ci pool (main.yml already runs there):
The pinned runner-image digest is unchanged, so ci/check-runner-image.py still passes (verified locally), and the required check context source-pr / source is preserved. This PR's own gate runs the updated file on alkane-ci, so it self-validates.
The dead r610 pools behind alkane-fast and alkane-verify were disabled after their SSD failure, leaving only offline runners on those labels. The required `source-pr / source (pull_request)` gate runs on alkane-fast, so every PR to main is unmergeable, and next-build/pages jobs on alkane-verify never run.
Repoint the four jobs to the healthy GARM-backed alkane-ci pool (main.yml already runs there):
- fast-pr.yml (source-pr gate): alkane-fast -> alkane-ci
- next.yml (next-build): alkane-verify -> alkane-ci
- bench-pages.yml: alkane-verify -> alkane-ci
- ci-badge.yml: alkane-verify -> alkane-ci
The pinned runner-image digest is unchanged, so ci/check-runner-image.py still passes (verified locally), and the required check context source-pr / source is preserved. This PR's own gate runs the updated file on alkane-ci, so it self-validates.
Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01B1W6qKwKxq3oUPDKWicM6i
The dead r610 pools behind alkane-fast and alkane-verify were disabled
after their SSD failure, leaving only offline runners on those labels.
The required source-pr gate runs on alkane-fast, so every PR to main is
unmergeable (the check never gets a runner), and next-build/pages jobs on
alkane-verify never run either.
Repoint the four jobs on the dead pools to the healthy GARM-backed
alkane-ci pool, matching main.yml which already runs there:
- fast-pr.yml (source-pr gate) alkane-fast -> alkane-ci
- next.yml (next-build) alkane-verify -> alkane-ci
- bench-pages.yml alkane-verify -> alkane-ci
- ci-badge.yml alkane-verify -> alkane-ci
The pinned runner-image digest is unchanged, so ci/check-runner-image.py
still passes (verified locally), and workflow/job names are unchanged so
the required context source-pr / source is preserved.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1W6qKwKxq3oUPDKWicM6i
noah
merged commit c7cda3064e into main2026-11-16 14:57:42 -07:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The dead r610 pools behind alkane-fast and alkane-verify were disabled after their SSD failure, leaving only offline runners on those labels. The required
source-pr / source (pull_request)gate runs on alkane-fast, so every PR to main is unmergeable, and next-build/pages jobs on alkane-verify never run.Repoint the four jobs to the healthy GARM-backed alkane-ci pool (main.yml already runs there):
The pinned runner-image digest is unchanged, so ci/check-runner-image.py still passes (verified locally), and the required check context source-pr / source is preserved. This PR's own gate runs the updated file on alkane-ci, so it self-validates.
Generated with Claude Code
https://claude.ai/code/session_01B1W6qKwKxq3oUPDKWicM6i