API · SDK · runtime · authentication lifecycle intelligence

Last updated · 9 September 2026

SchemaTrace

Breaking changes, enforcement dates and migration requirements.

ST-2026-200 · API versions & compatibility

GitHub REST API calendar version 2026-03-10 becomes available

GitHub released REST API calendar version 2026-03-10 on 12 March 2026 as the first calendar version containing breaking changes, while keeping 2022-11-28 supported and as the default for requests without an explicit version header.

GitHubREST APIAPI versioningbreaking changes2026-03-10

Previous state

The 2022-11-28 REST API calendar version remained the default and GitHub had not yet released the 2026-03-10 breaking-change calendar version.

Current state

REST API calendar version 2026-03-10 is available for integrations that explicitly select it; requests without X-GitHub-Api-Version continue to default to 2022-11-28, which remains supported for at least 24 months from the announcement.

Who needs to care

GitHub REST API integrations that explicitly select an API calendar version or need to evaluate the breaking changes in 2026-03-10.

What to do

Review the documented breaking changes and test integration compatibility before opting into 2026-03-10; no immediate migration is required.

What the source does not prove

The source proves availability of REST API version 2026-03-10 and its breaking-change status. It does not retire 2022-11-28, force immediate adoption, or imply that every GitHub Enterprise Server deployment exposed the version on 12 March 2026.

Lifecycle history

Dated event sequence

  1. REST API version 2026-03-10 announced

    GitHub released calendar version 2026-03-10 and documented it as the first calendar version containing breaking changes.

Evidence ledger

First-party sources

  1. 01
    GitHub — REST API version 2026-03-10 is now available

    Official GitHub changelog · 2026-03-12

    Open official source ↗