Registry/feed protocol
GitHub Actions cache service v2 self-hosted runner 2.231.0 protocol auth errors cache official
Hosted runners pass, but a self-hosted runner receives protocol/auth errors from cache.
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: Outdated self-hosted runner cannot use new cache service
Likely root cause: Hosted runners pass, but a self-hosted runner receives protocol/auth errors from cache.
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
Hosted runners pass, but a self-hosted runner receives protocol/auth errors from cache.
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 service v2 self-hosted runner 2.231.0 protocol auth errors cache official
site:github.blog changelog actions cache v2 self hosted runners 2.231.0 cache service
https://github.com/actions/cacheSource Trail
GitHub source file/reference: