Vendor coverage
GitHub API changes & breaking changes
Track changes to GitHub's published REST API contracts for your apps and automations. Inspect endpoint and parameter changes, check the version your requests select, and review the evidence before upgrading.
Last checked Oct 20, 2026, 10:49 PMLast change detected Oct 18, 2026, 4:15 AM
1 catalog dependency on Free · Email digests · No card required.
Detected changes
Latest GitHub API changes
Inspect each finding's source, channel, and before-and-after evidence. API and documentation changes appear first within each page; SDK activity is listed separately.
API and documentation changes
- InfoResponse non success status added
openapi:POST /orgs/{}/code-security/configurations/{}/attach::response.422.application.json.body - InfoResponse non success status added
openapi:POST /orgs/{}/code-security/configurations/{}/attach::response.409.application.json.body - InfoResponse non success status added
openapi:POST /orgs/{}/code-security/configurations/{}/attach::response.404.application.json.body - InfoResponse non success status added
openapi:POST /orgs/{}/code-security/configurations/{}/attach::response.400.body - InfoResponse non success status added
openapi:POST /orgs/{}/code-security/configurations/{}/attach::response.422.application.json.body - InfoResponse non success status added
openapi:POST /orgs/{}/code-security/configurations/{}/attach::response.409.application.json.body - InfoResponse non success status added
openapi:POST /orgs/{}/code-security/configurations/{}/attach::response.404.application.json.body - InfoResponse non success status added
openapi:POST /orgs/{}/code-security/configurations/{}/attach::response.400.body - InfoEndpoint added: PATCH /agents/repos/{}/{}/automations/{}
openapi:PATCH /agents/repos/{}/{}/automations/{}::operation.endpoint-added - InfoEndpoint added: GET /agents/repos/{}/{}/automations/{}
openapi:GET /agents/repos/{}/{}/automations/{}::operation.endpoint-added
Review checklist
Review a GitHub REST API change
Use the evidence to decide what needs testing in your integration.
Find the version your client requests
Check X-GitHub-Api-Version in your HTTP client or SDK configuration. Consult GitHub's supported-version list if the header is missing or the selected version is approaching retirement.
Match the finding to an endpoint
Inspect the method, path, changed parameter or response field, and source link. Similar findings can come from different versioned contracts; check the source before deciding whether both apply.
Test your automation on the target version
Use GitHub's breaking-change guide to review an upgrade, then test the endpoints your automation calls. Declare those operations in Detektu to review future matching findings.
Coverage
What Detektu monitors
Catalog contracts configured for monitoring. Check each source link for its version and channel.
Change model
How GitHub ships changes
The release patterns that shape your integration risk.
GitHub uses the X-GitHub-Api-Version request header to select a date-based REST API version. Breaking changes normally arrive in a new version; additive changes can reach all supported versions. GitHub documents exceptions and support deadlines in its versioning policy.
Detektu monitors the catalog's versioned GitHub.com REST OpenAPI descriptions as separate sources and compares successive observations of each source. This history helps you review changes to the endpoints you use. It is not a comparison of arbitrary versions, and this catalog product does not cover GitHub's GraphQL API.
Official GitHub references
Versioning guidance reviewed . Check the official references for current policy and dates.
Monitored for you
Do GitHub's changes affect your integration?
Choose the operations and fields your services use. Detektu matches GitHub findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.