Self-hosted runner version enforcement date has moved
GitHub moved the enforcement date for self-hosted runner minimum versions to September 29, 2026. Runners older than 2.329.0 can no longer register, and older runtime versions stop executing jobs. The changelog provides the new timeline and a REST API for checking deprecation dates.
GitHub announced that the enforcement date for minimum version requirements on self‑hosted runners in GitHub Enterprise Cloud has shifted. The change will be shipped on Monday, September 28, 2026, with full enforcement beginning on Tuesday, September 29, 2026. Runners with a version lower than 2.329.0 will no longer be able to register or reregister, and those below the higher runtime minimum will cease executing workflow jobs. The new timeline tightens the window for organizations to upgrade their runner fleets before workflow interruptions occur. A REST API now lets administrators query deprecation dates for any runner version and set up alerts, helping to manage large deployments. The adjustment applies only to GitHub Enterprise Cloud; GitHub Enterprise Server remains unaffected. It is not yet clear whether GitHub will modify the version thresholds or extend the deadline further, as the announcement only confirms the moved date. The impact on customers who already faced enforcement on July 31, 2026 for Data Residency remains unspecified, and GitHub has not detailed any additional mitigation measures.