ST-2026-084 · API endpoints & versions
GitHub removes code_scanning_upload from the rate-limit API response
GitHub removed the code_scanning_upload object from the /rate_limit REST response because code-scanning uploads share the standard core limit pool.
Previous state
The /rate_limit response exposed code_scanning_upload as a separate resource category even though it shared the core rate-limit pool.
Current state
The code_scanning_upload object is absent from /rate_limit responses and the existing core resource continues to govern code-scanning uploads.
Affected users
Who needs to care
Scripts, SDK wrappers and monitoring integrations that parse /rate_limit and reference resources.code_scanning_upload.
Required response
What to do
Remove dependencies on the deleted object and read the core rate-limit resource for code-scanning upload capacity.
Evidence boundary
What the source does not prove
GitHub states that no replacement field is needed because uploads continue to use the core pool. The change does not remove code-scanning uploads or create a new rate-limit category.
Lifecycle history
Dated event sequence
- Removal announced
GitHub published the before-and-after response contract and migration guidance.
- Field removed
The code_scanning_upload object was removed from the /rate_limit response.
Evidence ledger
First-party sources
- 01GitHub Changelog — Deprecation notice: code_scanning_upload field will be removed from rate_limit API endpoint
Official REST API contract and removal notice · 2026-05-05
Open official source ↗