GitHub Actions · Deprecation

GitHub Actions deprecation

Read from GitHub Actions's own page on 2026-11-09. 7 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.

Minimum notice

We will provide advance notice before releasing breaking changes.
Read from GitHub Actions's own page on 2026-11-09

Support window

period: 24 months
API versions are supported for 24 months after a newer API version is released.
Read from GitHub Actions's own page on 2026-11-09

Announcement channels

channel: changelog
Before upgrading to a new REST API version, you should read the changelog of breaking changes for the new API version
Read from GitHub Actions's own page on 2026-11-09
channel: other
GitHub will communicate such changes through release notes, changelogs, and direct communication explaining what changed and why.
Read from GitHub Actions's own page on 2026-11-09

Deprecation / Sunset headers

deprecation: truesunset: true
GitHub includes the following headers in API responses to help you prepare for migration: Deprecation — The date when the API version will be closing down
Read from GitHub Actions's own page on 2026-11-09

Versioning scheme

value: date-based
The API version name is based on the date when the API version was released.
Read from GitHub Actions's own page on 2026-11-09

Breaking change definition

Breaking changes are changes that can potentially break an integration.
Read from GitHub Actions's own page on 2026-11-09

Document

Download YAML · schema: API Commons Deprecation 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page