Repository navigation
Feature: Handle 503/500s from GitHub #2210
Description
Pre-submission checks
- I am not reporting a bug (crash, false positive/negative, etc). These must be filed via the bug report template.
- I have looked through both the open and closed issues for a duplicate request.
- I affirm that I have followed the AI policy and that this request constitutes my own words and understanding.
What's the problem this feature will solve?
Caused by:
0: error in 'known-vulnerable-actions' audit
1: request error while accessing GitHub API
2: HTTP status server error (503 Service Unavailable) for url (https://api.github.com/advisories?ecosystem=actions&affects=actions%2Fcache%40v5.0.5)
Describe the solution you'd like
Possibly retrying? (with backoff?) Possibly caching?
Additional context
No response
Activity
woodruffw commentedon Jul 20, 2026
Thanks for the report. I suspect we might need to tweak the retry middleware slightly to make sure it's treating 5xx as retryable. But fundamentally this is a form of service instability from GitHub, so if they exhaust our retries there isn't much we can do about it.
(zizmor does cache requests, although the cache doesn't get shared across CI runs because GitHub's own caching headers are very short and thus the hit rate would be very low.)