GitHub Actions Resumes Strict Enforcement of Self-Hosted Runner Version Requirements

GitHub Actions is moving forward with stricter enforcement of minimum version requirements for its self-hosted runners, a critical step in bolstering the platform's overall reliability and availability. This renewed push comes after a period of adjustments and delays earlier in the year, with GitHub now providing clear and firm deadlines for compliance. The primary goal is to ensure that all self-hosted runners are compatible with a re-architected backend infrastructure that has significantly improved job execution and runner communication capabilities, now handling over 120 million jobs daily. The enforcement strategy includes a series of 'brownouts' – intermittent periods where unsupported runner versions will experience disruptions. These brownouts will initially block the registration of outdated runners and later extend to intermittently blocking job execution. This phased approach is designed to give organizations ample time to identify and rectify non-compliant runners before full enforcement takes effect. For GitHub Enterprise Cloud with Data Residency, brownouts are scheduled to begin on June 29, leading to full enforcement by July 31, 2026. GitHub Enterprise Cloud users will see brownouts starting August 24, with complete enforcement mandated by September 25, 2026. GitHub Enterprise Server installations are not affected by these specific changes at this time. To remain compliant, self-hosted runners must meet two key requirements: they need to be on version 2.329.0 or newer for initial registration and must continue to install new runner releases within 30 days of their publication. Runners configured with auto-update enabled will generally meet the 30-day requirement, provided they can reach the update service. However, manually updated runners require a consistent upgrade cadence. GitHub has also introduced an additional layer of urgency: critical security updates will now pause job queuing to a runner until the update has been applied, emphasizing the importance of keeping runners current for security and operational continuity. GitHub has also rolled out new tooling to assist enterprise owners in auditing their runner inventory. This includes the ability to query audit logs for runner registration events, which now include version information, and access to runner version data via the REST API. Teams are advised to upgrade all self-hosted runners to the latest supported version, update installation scripts, VM images, container images, and deployment automation, and recreate any runners built from older cached images or templates to ensure seamless operation.