Registry/feed protocol
GitHub Actions cache old versions retired cache service backend brownouts shutdown actions/cache v1 v2 February 2025
Restore/save begins failing during brownouts or after shutdown while other steps pass.
Agent Quick Fix
Repair against the current GitHub Actions cache contract, then keep the change narrow and source-backed.
Product: GitHub Actions cache
Current-contract area: Old actions/cache release targets retired cache backend
Likely root cause: Restore/save begins failing during brownouts or after shutdown while other steps pass.
Repair direction: Verifier checks continuity, cursor advancement, de-duplication, and compatibility with the current feed. Verify an updated action/runner protocol and correct restore/save behavior.Symptom
Restore/save begins failing during brownouts or after shutdown while other steps pass.
Why This Happens
The consumer code is locally valid under the old feed contract; only the live registry's current routing, cursor, or response semantics disambiguate the fix.
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.
GitHub Actions cache old versions retired cache service backend brownouts shutdown actions/cache v1 v2 February 2025
actions/cache legacy cache service shutdown brownout v1 v2
site:github.com/actions/cache cache service will be retired February 1 2025
"cache service" "February 1, 2025" "actions/cache"
https://github.com/actions/cacheSource Trail
GitHub source file/reference: