GitHub Self-Hosted Runner Brownouts Start Sept 2026
GitHub announces permanent shutdown of outdated self-hosted runners on September 25, 2026, with brownout test dates scheduled this September.
Stock photo for illustration only, not from the actual event
- GitHub will permanently stop queuing jobs for outdated runners on September 25, 2026.
- Brownout test periods are scheduled for September 7, 9, 11, 14, 16, and 18.
- The failure mode is silent, leaving targeted jobs stuck indefinitely in a Queued status.
- Developers can use the gh-runner-eol extension to audit runners and pinned versions.
Administrators managing self-hosted GitHub Actions runners must prepare for a major deprecation timeline, as GitHub has set September 25, 2026, as the permanent cutoff date to stop queuing jobs to outdated runner versions. Leading up to this deadline, GitHub will enforce a series of brownout periods on September 7, 9, 11, 14, 16, and 18. During these specific Config and Runtime days, outdated runners will fail to register and execute incoming tasks.
This failure mode occurs entirely silently without throwing explicit workflow errors. Affected runner logs will state that the version is deprecated and cannot receive messages, causing every assigned job to sit indefinitely in a Queued state. Furthermore, if you rely on the Actions Runner Controller, auto-update is disabled by default, meaning image tags defined within your Helm values act essentially as unscheduled outages waiting to happen.
"Runner version v2.xxx.0 is deprecated and cannot receive messages and every job targeting it sits in Queued ."
GitHub Actions Runner Log
To help mitigate this issue, GitHub has introduced an official endpoint that returns the precise end-of-life date for any given runner version. Developers can integrate this data into their workflows to proactively catch deprecations before they disrupt production pipelines.
Stock photo for illustration only, not from the actual event
A developer has wrapped these API endpoints into an open-source GitHub CLI extension called gh-runner-eol. Running the audit command scans repositories for outdated runners, returning clear categorization ranging from overdue versions to those with active support. Additionally, the tool includes a scan flag that greps through Dockerfiles, ARC Helm values, environment variables, and download URLs to uncover hidden pinned versions that a live runner dashboard cannot detect.
Managing self-hosted infrastructure requires rigorous visibility into version control dependencies. Hidden pinned references in infrastructure-as-code files are a common blind spot during major runtime deprecations, making automated CI/CD auditing tools essential for preventing unexpected production downtime.
The extension also functions seamlessly as a GitHub Action with SARIF output, allowing pinned version risks to trigger code-scanning annotations directly inside pull requests while ensuring automated alerts for overdue components.
Source: Dev.to
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment