Previously, we introduced calendar-based versioning for our REST API, giving us a path to evolving our API while giving integrators plenty of time and clear guidance for upgrading.

Now, we’re releasing calendar version 2026-03-10, the newest version of the GitHub REST API. This is the first calendar version to include breaking changes.

What’s in this release

Version 2026-03-10 introduces a set of breaking changes to the REST API. You can find the full list of changes, along with upgrade guidance, in our breaking changes documentation. 

As a reminder, non-breaking changes (e.g., new endpoints, optional parameters, additional response fields) continue to be available across all supported API versions.

What this means for existing integrations

Version 2022-11-28 will continue to be fully supported for at least 24 months from today, and requests that don’t include the X-GitHub-Api-Version header will continue to default to 2022-11-28.

When you’re ready to upgrade, it’s straightforward. After reviewing the new version documentation and making any necessary changes to your integration to account for breaking changes, update the X-GitHub-Api-Version header to 2026-03-10 and verify that your integration works as expected with the new API version.

Use the version picker in our API documentation to view the docs for all available versions.

What’s next

We’ll continue to communicate future API version releases through the GitHub changelog. 

We’d love for integrators to adopt 2026-03-10 to take advantage of the latest enhancements and features. While there’s no pressure to upgrade immediately, moving to the new version will help ensure your integration remains compatible and benefits from ongoing improvements as we continue to release new versions over time.