cache

You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

History

Jasperhino c0d02c4c23 Fix restore-keys to prefix-match on GCS like actions/cache restore-keys were checked with exact object existence, so prefix fallbacks (e.g. `nx-` matching `nx-<sha>`) never hit on GCS — they only worked via the GitHub cache fallback, which is empty when saves go to GCS. Rolling caches keyed on unique values (sha/run) were therefore never restored. Primary key stays exact-match to keep `cache-hit` semantics. Restore keys now list objects by prefix and pick the newest, mirroring the upstream actions/cache contract. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PkmyS2WfCHHdaQQRpfqvNi	3 days ago
..
index.js	Fix restore-keys to prefix-match on GCS like actions/cache	3 days ago

Jasperhino c0d02c4c23 Fix restore-keys to prefix-match on GCS like actions/cache

restore-keys were checked with exact object existence, so prefix
fallbacks (e.g. `nx-` matching `nx-<sha>`) never hit on GCS — they
only worked via the GitHub cache fallback, which is empty when saves
go to GCS. Rolling caches keyed on unique values (sha/run) were
therefore never restored.

Primary key stays exact-match to keep `cache-hit` semantics. Restore
keys now list objects by prefix and pick the newest, mirroring the
upstream actions/cache contract.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PkmyS2WfCHHdaQQRpfqvNi

index.js

Fix restore-keys to prefix-match on GCS like actions/cache