New API Version Release

GitHub has released REST API version 2026-03-10, the first calendar-versioned API release to introduce breaking changes. This milestone represents a shift in GitHub's API evolution strategy, which was previously introduced to provide clear versioning and upgrade paths for integrators.

Breaking Changes and Migration Path

Version 2026-03-10 includes a set of breaking changes detailed in the official breaking changes documentation. Developers should review this documentation to understand the impact on their integrations before upgrading.

Non-breaking changes—such as new endpoints, optional parameters, and additional response fields—continue to be available across all supported API versions.

Backward Compatibility and Support Timeline

The previous version 2022-11-28 will remain fully supported for at least 24 months from the release date. API requests without an explicit X-GitHub-Api-Version header will continue to default to 2022-11-28, ensuring existing integrations function without immediate action.

Upgrading to the New Version

To migrate to 2026-03-10, developers should:

1. Review the breaking changes documentation to understand what modifications their integration requires
2. Update the X-GitHub-Api-Version header to 2026-03-10 in their API requests
3. Test thoroughly to verify integration compatibility with the new API version

The API documentation includes a version picker to view docs for all available versions.

Looking Forward

GitHub encourages adoption of 2026-03-10 to benefit from the latest enhancements and features, though there is no immediate pressure to upgrade. Future API versions will continue to be communicated through the GitHub changelog.