GitHub changed the timing of its minimum-version enforcement for self-hosted Actions runners on September 28, 2026. Full enforcement on GitHub Enterprise Cloud now begins September 29. The required versions themselves have not changed. A self-hosted runner is a machine an organization operates to execute its GitHub Actions jobs. Teams managing such machines should check their deployed runner versions against the two separate restrictions before their next workflow runs. Source
Two thresholds to inspect
A runner older than version 2.329.0 will no longer be able to register or reregister. Existing runners also face a minimum version for executing jobs, and GitHub says that threshold is higher than the registration threshold. The short announcement does not state the numeric execution threshold. A runner still appearing in an inventory is therefore insufficient evidence that it can accept new jobs. Administrators can use GitHub’s runner documentation and its REST API for version deprecations to check registration and runtime dates for the versions they actually operate. Source
Which installations are covered
GitHub limits this particular date change to Enterprise Cloud. GitHub Enterprise Server is unaffected, while enforcement for Enterprise Cloud with Data Residency had already begun on July 31, 2026. An organization with several GitHub environments should identify which service hosts each runner before planning its updates. Version inventory and a test job after upgrading are practical checks derived from the two documented restrictions, rather than additional requirements announced by GitHub. Source