Versioned API schema
GitHub REST API rate limit endpoint response rate resources core
Client raises KeyError/null dereference after switching X-GitHub-Api-Version to 2026-03-10.
Agent Quick Fix
Repair against the current GitHub REST API contract, then keep the change narrow and source-backed.
Product: GitHub REST API
Current-contract area: GET /rate_limit no longer returns top-level rate
Likely root cause: Client raises KeyError/null dereference after switching X-GitHub-Api-Version to 2026-03-10.
Repair direction: Verifier exercises the changed field/status/enum plus an unaffected endpoint to prevent a brittle one-off patch. Exercise strict and permissive parsing plus one downstream behavior tied to the changed field.Symptom
Client raises KeyError/null dereference after switching X-GitHub-Api-Version to 2026-03-10.
Why This Happens
Several historical response shapes are locally plausible; only the selected current API version determines fields, enums, media types, and status codes.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
site:docs.github.com REST API rate limit response resources core rate 2026-03-10 X-GitHub-Api-Version
GitHub REST API rate limit endpoint response rate resources core
https://docs.github.com/en/rest/rate-limit/rate-limit?apiVersion=2022-11-28Source Trail
GitHub source file/reference: