Registry/feed protocol
GitHub Actions cache legacy service shutting down obsolete client protocol retries occasionally pass final shutdown actions/cache v1 v2 upgrade v4
Retries occasionally pass before the final shutdown, obscuring that the client protocol is obsolete.
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: Cache brownout misdiagnosed as flaky network
Likely root cause: Retries occasionally pass before the final shutdown, obscuring that the client protocol is obsolete.
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
Retries occasionally pass before the final shutdown, obscuring that the client protocol is obsolete.
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 legacy service shutting down obsolete client protocol retries occasionally pass final shutdown actions/cache v1 v2 upgrade v4
site:github.com/actions/cache cache service v2 migration February 1 2025
https://github.com/actions/cacheSource Trail
GitHub source file/reference: