ST-2026-012 · SDKs, clients & toolchains
GitHub schedules self-hosted runner version enforcement for July and September 2026
GitHub Actions first extended its self-hosted runner registration deadline to 16 March 2026, paused that enforcement days before it was due, then published a replacement schedule with full enforcement starting 31 July for Enterprise Cloud with Data Residency and 25 September for Enterprise Cloud.
Previous state
GitHub had announced a March 2026 registration floor for runner version 2.329.0, while the separate rolling support policy could already stop sufficiently outdated registered runners from executing jobs.
Current state
The March registration block was paused and replaced by a staged brownout and enforcement calendar: 31 July 2026 for Enterprise Cloud with Data Residency and 25 September 2026 for standard Enterprise Cloud, with runtime execution also subject to the rolling update policy.
Affected users
Who needs to care
GitHub Enterprise Cloud organizations operating self-hosted runners, custom runner images, Actions Runner Controller fleets or update-disabled runner installations.
Required response
What to do
Audit runner versions, update images and installation automation, enable or operationalise regular upgrades, test brownout exposure, and avoid pinning fleets permanently to the registration minimum.
Evidence boundary
What the source does not prove
The pause applied to configuration and registration enforcement, not to the separate rolling rule that can reject already-registered runners from executing workflows when they are too far behind. GitHub Enterprise Server remains outside this schedule.
Connected NeoLinks intelligence
Related evidence across the network
Curated because the records share a publisher, platform, control, sector or procurement context. Each destination keeps its own evidence boundary.
GitHub Actions runner pricing and postponed self-hosted fee
The runner-version enforcement calendar affects operability; SkuTrace preserves the separate hosted and self-hosted pricing change.
Lifecycle history
Dated event sequence
- Registration deadline extended
GitHub moved the configuration-time enforcement date by one week to 16 March and clarified that it concerned registration rather than the runtime support floor.
- March enforcement paused
GitHub temporarily paused the v2.329.0 registration block and said a replacement plan would follow.
- Replacement schedule published
GitHub published separate brownout and full-enforcement calendars for Data Residency and standard Enterprise Cloud.
- Data Residency enforcement
Full registration and runtime enforcement is scheduled to begin for GitHub Enterprise Cloud with Data Residency.
- Enterprise Cloud enforcement
Full enforcement is scheduled to begin for standard GitHub Enterprise Cloud.
Evidence ledger
First-party sources
- 01GitHub Changelog — GitHub Actions: Self-hosted runner minimum version enforcement extended
Official amended enforcement notice · 2026-02-20
Open official source ↗ - 02GitHub Changelog — Self-hosted runner minimum version enforcement paused
Official pause and clarification notice · 2026-03-17
Open official source ↗ - 03GitHub Changelog — GitHub Actions: Minimum version enforcement timeline for self-hosted runners
Official replacement enforcement schedule · 2026-06-12
Open official source ↗