GitHub Actions: Minimum Version Enforcement for Self-Hosted Runners Resumes

GitHub Actions is re-establishing its minimum version enforcement policy for self-hosted runners, impacting users on github.com and GitHub Enterprise Cloud with Data Residency. This strategic decision is a crucial component of a broader effort by the GitHub Actions team to significantly improve the platform's overall reliability and availability. The team initiated a comprehensive re-architecture of the backend services responsible for job execution and runner communication in early 2024. This foundational investment has already yielded substantial results, with the new architecture now processing over 120 million jobs daily, a threefold increase from previous volumes, and enabling enterprises to initiate jobs seven times faster per minute. The resumption of version enforcement marks the next phase in this migration. As all runners transition to the new, more robust platform, older runner versions that are incompatible with the updated infrastructure will no longer be supported. To maintain seamless operation, self-hosted runner users must adhere to two primary requirements. Firstly, for configuration or re-registration, runners must be running version 2.329.0 or newer. This specific version is the minimum threshold required for the new architecture to recognize and connect with the runner. Secondly, to ensure continuous execution of workflow jobs, runners must be kept up-to-date by installing each new runner release within 30 days of its publication. While this 30-day update requirement has always existed, its enforcement has not been consistently applied in all scenarios. It is important to note that version 2.329.0 serves solely as the minimum requirement for initial registration and to receive subsequent updates. It does not represent a static minimum for job execution. The effective minimum version for job execution will progressively advance as new runner releases become available. Runners configured with auto-update enabled will generally meet the 30-day requirement automatically, provided they can access the update service. Conversely, users with auto-update disabled will need to manually upgrade their runners on a regular schedule. Simply meeting the registration minimum is insufficient; a runner pinned to version 2.329.0 that never updates will eventually cease to pick up jobs. Any new release, whether major, minor, or patch, qualifies as an available update. If a runner is not updated within 30 days of an update's availability, the GitHub Actions service will stop queuing jobs to it. Furthermore, in instances of critical security updates, GitHub Actions will temporarily suspend job queuing to the affected runner until the update has been successfully applied. The enforcement process will commence with "brownouts," which involve intermittently blocking the registration and later the execution of jobs on unsupported runner versions. These brownouts are designed to help users identify and address outdated runners proactively before full enforcement takes effect. The full enforcement timeline is set for July 31, 2026, for GitHub Enterprise Cloud with Data Residency, and September 25, 2026, for GitHub Enterprise Cloud. After these respective dates, self-hosted runners below the minimum required version for registration (e.g., older than 2.329) will be unable to register or re-register. Existing runners that fall below the minimum version required for executing workflow jobs (which may be a higher version than the registration minimum) will stop processing jobs, even if they were previously registered. This phased approach aims to provide users with ample time to prepare and ensure their self-hosted runner fleets are compliant.