ST-2026-241 · APIs & integration
GitHub adds runner-version deprecation timestamps to the Actions REST API
GitHub Actions now exposes repository-, organization- and enterprise-level REST endpoints that report registration and runtime deprecation timestamps for a supplied runner version.
Previous state
GitHub Actions administrators did not have the source-described REST endpoint for retrieving both registration and runtime deprecation timestamps for a specified runner version.
Current state
GET /actions/runners/deprecations/{version} is available at repository, organization and enterprise scope and returns runner_version, runtime_deprecates_at and registration_deprecates_at.
Affected users
Who needs to care
GitHub Actions administrators and automation that track self-hosted runner upgrade readiness across repositories, organizations or enterprises.
Required response
What to do
Query the endpoint for deployed runner versions and use the returned registration and runtime timestamps to plan upgrades before the applicable support boundary.
Evidence boundary
What the source does not prove
GitHub proves availability and the documented response fields of this observability API. The announcement does not itself deprecate a runner version or establish any particular version's timestamps.
Lifecycle history
Dated event sequence
- Runner-version deprecation API announced
GitHub added repository, organization and enterprise endpoints for version-specific registration and runtime dates.
Evidence ledger
First-party sources
- 01GitHub — GitHub Actions: Early September 2026 updates
Official GitHub Changelog · 2026-09-03
Open official source ↗