GitHub enforces minimum self-hosted runner versions from 29 September
Serguey Asael Shinder1 min readGitHub has changed the date on which it enforces minimum versions for self-hosted GitHub Actions runners on GitHub Enterprise Cloud. According to its changelog, the change shipped on Monday 28 September and full enforcement begins on Tuesday 29 September, instead of the date announced earlier.
The requirements themselves are unchanged. Self-hosted runners below version 2.329.0 cannot register or re-register. Runners that are already registered but sit below a separate, higher minimum required to execute jobs will stop running workflow jobs, even though they were registered before. GitHub points to a new REST API for runner version deprecations, which returns the registration and runtime cut-off dates for any runner version and can feed automated alerts for fleets nearing a deadline.
The change applies only to GitHub Enterprise Cloud. GitHub Enterprise Server is not affected, and enforcement for Enterprise Cloud with data residency already began on 31 July.
What it means
A runner that silently stops picking up jobs looks like a stuck queue, not like a version problem. Teams with pinned runner images, autoscaling groups built from old AMIs or runners on machines nobody patches should check versions today, because the failure mode is jobs waiting forever. The deprecation API is the durable fix: it turns the next cut-off into an alert instead of an outage.