GitHub Releases REST API Version 2026-03-10 with First Calendar-Based Breaking Changes

Summary

GitHub has announced the availability of REST API version 2026-03-10, marking the first calendar-versioned release to include breaking changes. The new version introduces a set of modifications to the API, with comprehensive documentation and upgrade guidance provided to help integrators transition smoothly. Existing integrations using version 2022-11-28 will continue to be fully supported for at least 24 months, with requests defaulting to the older version unless the X-GitHub-Api-Version header is explicitly updated.

The release demonstrates GitHub's commitment to API evolution while maintaining backward compatibility through a clear versioning strategy. Integrators are encouraged to review breaking changes documentation, update their implementations accordingly, and switch to the new version to access the latest enhancements and features. Non-breaking changes, such as new endpoints and optional parameters, remain available across all supported API versions.

• Non-breaking additions continue across all supported versions, allowing for gradual API evolution

Editorial Opinion

GitHub's approach to API versioning with a clear 24-month support window and transparent breaking changes documentation sets a good example for developer-facing platforms. The calendar-based versioning scheme provides predictability for integrators, though the significant gap between the current supported version (2022-11-28) and the new breaking-changes version (2026-03-10) suggests substantial platform evolution has occurred. This measured approach to introducing breaking changes, combined with maintained backward compatibility, balances innovation with stability—a critical consideration for an infrastructure tool upon which countless developers depend.