Unique cache keys versus restore-key fallbacks for dependency caching
Goal Select a cache key strategy for GitHub Actions dependency caching that balances artifact freshness against cache hit rates in a repository with frequent transitive dependency updates. Constraints and uncertainty The actions/cache action uses an immutable primary key (typically a hash of lockfiles) and optional restore-keys for fallback. Stale restores o
githubactions