Deprecation notice: code_scanning_upload field will be removed from rate_limit API endpoint

On May 19, 2026, we’ll remove the code_scanning_upload field from the rate_limit REST API endpoint response.

Why did we make this change?

The code_scanning_upload field in the rate_limit response has been a source of confusion. While it appeared as a separate rate limit category, it shares the same limit pool as core. This led customers to incorrectly interpret their rate limit status.

What you need to do

If your code or scripts parse the /rate_limit endpoint and reference the code_scanning_upload field, update them before May 19, 2026 to avoid failures.

Before:

{
  "resources": {
    "core": { "limit": 5000, "used": 1, "remaining": 4999, "reset": 1372700873 },
    "code_scanning_upload": { "limit": 5000, "used": 1, "remaining": 4999, "reset": 1372700873 }
  }
}

{
  "resources": {
    "core": { "limit": 5000, "used": 1, "remaining": 4999, "reset": 1372700873 },
    "code_scanning_upload": { "limit": 5000, "used": 1, "remaining": 4999, "reset": 1372700873 }
  }
}

After May 19, 2026:

{
  "resources": {
    "core": { "limit": 5000, "used": 1, "remaining": 4999, "reset": 1372700873 }
  }
}

{
  "resources": {
    "core": { "limit": 5000, "used": 1, "remaining": 4999, "reset": 1372700873 }
  }
}

The standard core rate limit continues to govern GitHub code scanning uploads. No replacement field is needed.

For more information about rate limits, see Rate limits for the REST API.