ST-2026-066 · Enforcement & amendments
GitHub resumes self-hosted-runner minimum-version enforcement
GitHub applies runner registration and job-execution enforcement first to Enterprise Cloud with Data Residency and later to Enterprise Cloud.
GitHub Actionsself-hosted runnersminimum versionenforcement
Previous state
Minimum-version enforcement was paused and older runners could continue beyond the resumed boundaries.
Current state
Data Residency enforcement begins 31 July; Enterprise Cloud enforcement begins 25 September after brownouts, with v2.329.0 registration and 30-day update rules.
Affected users
Who needs to care
GitHub Enterprise Cloud self-hosted-runner fleets; GHES is excluded.
Required response
What to do
Upgrade registration hosts to v2.329.0 or later and operationalise installation of each release within 30 days.
Evidence boundary
What the source does not prove
The dates and rules are plan-specific and do not apply to GitHub Enterprise Server in this notice.
Lifecycle history
Dated event sequence
- Data Residency enforcement
Full configuration and runtime enforcement begins.
- Enterprise Cloud enforcement
Full enforcement begins after scheduled brownouts.
Evidence ledger
First-party sources
- 01GitHub Changelog — GitHub Actions minimum version enforcement timeline for self-hosted runners
Official enforcement notice · 2026-06-12
Open official source ↗