GitHub Actions enforces minimum self-hosted runner versions starting July/September 2026
GitHub Actions is resuming enforcement of minimum version requirements for self-hosted runners on github.com and GitHub Enterprise Cloud. This change is necessary to support the new backend architecture that has increased reliability and performance. Users must ensure runners are on version 2.329.0 or later for registration and updated within 30 days of new releases to continue executing jobs. Enforcement begins with brownouts in July/August 2026, with full enforcement on July 31, 2026, for Data Residency instances and September 25, 2026, for others.
- →Two key version requirements for self-hosted runners
- →GitHub Actions resumes minimum self-hosted runner version enforcement
- →New tooling to identify and manage runner versions
- →Audit logs provide visibility into runner registrations
- →Action required to avoid workflow disruption
Breaking changes (1) ›
- Two key version requirements for self-hosted runners
To register or re-register, runners must be on version 2.329.0 or later. To continue executing workflow jobs, runners must be updated to the latest release within 30 days of its publication; otherwise, job queuing will be paused.
Enhancements (2) ›
- New tooling to identify and manage runner versions
GitHub Actions will provide runtime job annotations, APIs, and tooling to help users identify outdated runner versions. The runner version has been added to the REST API for easier querying.
- Audit logs provide visibility into runner registrations
For organizations using GitHub Enterprise Cloud, owners can query audit logs for runner registration events to identify currently registering runner versions. This helps in planning upgrades for large fleets.
Notes (2) ›
- GitHub Actions resumes minimum self-hosted runner version enforcement
GitHub Actions is reintroducing version enforcement for self-hosted runners to ensure compatibility with its newly rearchitected backend services. This migration has already improved job execution scalability and reliability.
- Action required to avoid workflow disruption
Users need to upgrade all self-hosted runners to the latest supported version, update installation scripts, and recreate runners built from older images. GitHub Enterprise Server is not affected by this change.
https://github.blog/changelog/2026-06-12-github-actions-minimum-version-enforcement-timeline-for-self-hosted-runners