Self-hosted runner version enforcement date has moved
Summary
The enforcement date for GitHub Actions minimum version requirements for self-hosted runners on GitHub Enterprise Cloud has changed. The change ships Monday, September 28, 2026, and full enforcement now begins… The post Self-hosted runner version enforcement date has moved appeared first on The GitHub Blog .
Original Text
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> The enforcement date for GitHub Actions minimum version requirements for self-hosted runners on GitHub Enterprise Cloud has changed. The change ships Monday, September 28, 2026, and full enforcement now begins Tuesday, September 29, 2026. This is instead of the date that was previously announced.
The requirements themselves are unchanged:
Self-hosted runners below version 2.329.0 won’t be able to register or reregister.
Existing runners below the minimum version required to execute workflow jobs (which is a higher version than the registration minimum) will stop running jobs, even if they were previously registered.
If you haven’t upgraded your self-hosted runners yet, do so before September 29, 2026 to avoid disruption to your workflows. See the self-hosted runner documentation for upgrade guidance. You can also use the new REST API for runner version deprecations to check the registration and runtime deprecation dates for any runner version and build automated alerts for fleets nearing their deadline.
This shift only affects GitHub Enterprise Cloud. GitHub Enterprise Server isn’t impacted. Enforcement already began for GitHub Enterprise Cloud with Data Residency on July 31, 2026.
The post Self-hosted runner version enforcement date has moved appeared first on The GitHub Blog.
Lotu Radar provides attributed news summaries and links to the original publisher. Full reporting and copyright remain with the source.