Summary
In its early-September 2026 updates (September 3), GitHub Actions shipped a REST API that reports when registration and runtime support end for a given runner version, so teams can plan self-hosted runner upgrades before deprecation. Full minimum-version enforcement on GitHub Enterprise Cloud begins September 25, 2026.
What changed
GitHub added GET /actions/runners/deprecations/{version}, callable at the repository, organization, or enterprise level, returning runner_version, runtime_deprecates_at, and registration_deprecates_at. This gives programmatic visibility into runner deprecation timelines ahead of full enforcement for self-hosted runners.
Why it matters
Fleets of self-hosted CI runners increasingly execute AI coding agents and automated pipelines, where a silently deprecated runner can break agentic workflows at scale. A queryable deprecation API lets platform teams automate upgrade planning and avoid enforcement-day outages as GitHub tightens minimum-version rules.
Evidence excerpt
"A new REST API returns when registration and runtime support end for a given runner version." Call GET /actions/runners/deprecations/{version} at repository, organization, or enterprise level; the response includes runner_version, runtime_deprecates_at, and registration_deprecates_at. Full enforcement on GitHub Enterprise Cloud begins September 25, 2026.