GitHub – REST API version 2026-03-10 is now available
quality 2/10 · low quality
0 net
AI Summary
GitHub released REST API version 2026-03-10, the first calendar-versioned API release to include breaking changes, with migration guidance for existing integrations from the currently-supported 2022-11-28 version.
Entities
GitHub
2026-03-10
2022-11-28
X-GitHub-Api-Version
REST API version 2026-03-10 is now available - GitHub Changelog Back to changelog 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. Related Posts Feb.03 Release The Dependabot Proxy is now open source with an MIT license ecosystem & accessibility supply chain security ... +1 Jan.12 Improvement Selectively showing "act on your behalf" warning for GitHub Apps is in public preview ecosystem & accessibility Nov.07 Retired GraphQL Explorer removal from API documentation on November 7, 2025 ecosystem & accessibility Oct.31 Retired Deprecated models in GitHub Models ecosystem & accessibility Sep.22 Release Open sourcing the GitHub Annotation Toolkit community engagement ecosystem & accessibility ... +1 Sep.11 Retired Deprecated Microsoft models in GitHub Models ecosystem & accessibility Sep.05 Release GitHub Actions: AI labeler and moderator with the GitHub Models inference API ecosystem & accessibility Sep.04 Release Remote GitHub MCP Server is now generally available copilot ecosystem & accessibility ... +1 Aug.26 Improvement Template URLs for fine-grained PATs and updated permissions UI ecosystem & accessibility Subscribe to our developer newsletter Discover tips, technical guides, and best practices in our biweekly newsletter just for devs. Enter your email * Subscribe By submitting, I agree to let GitHub and its affiliates use my information for personalized communications, targeted advertising, and campaign effectiveness. See the GitHub Privacy Statement for more details. Back to top