GitHub has moved the full enforcement date for minimum self-hosted runner versions on GitHub Enterprise Cloud to Tuesday, September 29, 2026. The requirements have not changed, so teams with outdated runners still face possible workflow disruption.
Deadline shift
The change ships Monday, September 28, replacing the previously announced enforcement date. GitHub says the revised schedule applies only to GitHub Enterprise Cloud. GitHub Enterprise Server is not affected by this update, while enforcement for GitHub Enterprise Cloud with Data Residency already began on July 31, 2026.
Registration will be blocked
Self-hosted runners below version 2.329.0 will no longer be able to register or register again once enforcement begins. That affects teams adding machines to a runner fleet as well as existing machines that need to reconnect or be re-registered.
Older runners may stop jobs
Registration is only the lower threshold. GitHub says the minimum version required to execute workflow jobs is higher than the registration minimum, meaning an already registered runner can still be prevented from running jobs if it falls below the runtime requirement. The source does not specify that higher version number.
Monitoring before the cutoff
GitHub recommends upgrading self-hosted runners before September 29 to avoid interruptions. It also points to a new REST API for runner version deprecations, which teams can use to check registration and runtime deprecation dates and create automated alerts for runner fleets approaching their deadlines.
AI-generated editorial illustration; not a documentary photograph.
Source: Self-hosted runner version enforcement date has moved
SIGNAL TITANS
Leave a Reply