Calendar-Based Versioning Milestone

GitHub has released REST API version 2026-03-10, the first calendar-versioned API release to introduce breaking changes. This represents a significant milestone in GitHub's API evolution strategy, which previously relied on date-based versioning without breaking updates.

Breaking Changes and Migration

The new version includes a set of breaking changes detailed in GitHub's documentation. Developers can find the complete list of modifications and step-by-step upgrade guidance in the breaking changes documentation. Non-breaking changes—such as new endpoints, optional parameters, and additional response fields—continue to roll out across all supported versions.

Clear Upgrade Path

For existing integrations, the transition is straightforward:

• Version 2022-11-28 will remain fully supported for at least 24 months
• Requests without an explicit X-GitHub-Api-Version header will continue defaulting to 2022-11-28
• When ready, developers can update the X-GitHub-Api-Version header to 2026-03-10 after reviewing the breaking changes
• Use GitHub's API documentation version picker to view docs for all supported versions

Next Steps

While there's no immediate pressure to upgrade, GitHub encourages developers to adopt 2026-03-10 to benefit from the latest enhancements and ensure long-term compatibility. Future API versions will be announced through the GitHub changelog.