GitHub Actions cache size limit (10 GB) exceeded / evictions

GitHub keeps at most 10 GB of cache per repository and evicts least-recently-used entries when that fills, so large or numerous caches silently push out the ones you rely on and turn hits into misses.

What this error means

Caches that should hit start missing intermittently, and total cache usage hovers near 10 GB. Recently saved entries vanish as new ones are written.

github-actions

Cache not found for input keys: Linux-build-... (entry evicted: repository cache exceeded 10 GB)

Common causes

Too many large caches

Big caches (Docker layers, full target/ dirs, multiple OS variants) sum past 10 GB and trigger eviction.

Per-run unique keys pile up

Keys that change frequently create many entries that quickly fill the quota.

How to fix it

Shrink and consolidate caches

Cache only what is expensive to recompute, not whole build trees.
Stabilize keys so you keep fewer, reused entries.
Delete stale caches via the cache management API or UI.

Use larger managed caching

Managed runner caching is not bound by the 10 GB per-repo hosted limit, so large dependency and layer caches stay warm and hit reliably.

How to prevent it

Cache narrowly to stay under the quota.
Avoid keys that churn and create entry sprawl.
Prune stale caches periodically.