chore: cache-assets

[MohamedH1998]

Summary

The Astro assets cache is configured with a static, immutable key: key: static

GitHub Actions caches are immutable, once created, a cache entry with a given key is never updated. This means the cache was created once and never refreshed, so changed or new assets are reprocessed on every build. This also caused the deploy preview to re-upload +6,000 assets per run instead of only changed files.

Fix

Replace the static cache key with a content-based key and restore-keys fallback:

key: astro-assets-${{ hashFiles('src/assets/**') }}
restore-keys: |
  astro-assets-

• No asset changes (most PRs): exact cache hit, zero reprocessing
• Assets added/changed: partial restore via restore-keys, only new/changed assets processed, updated cache saved

[github-actions]

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners
/.github/	@cloudflare/content-engineering, @kodster28, @mvvmm, @colbywhite, @ahaywood, @MohamedH1998

[github-actions]

Preview URL: https://ea6817dc.preview.developers.cloudflare.com
Preview Branch URL: https://chore-cache-assets.preview.developers.cloudflare.com

[mvvmm]

/bonk Does this work make sense? How did the old static key not break things when we added new assets?

[ask-bonk]

Looking at the changes to .github/workflows/ci.yml, the fix correctly addresses the GitHub Actions cache immutability issue. The static key was indeed problematic since GitHub Actions caches are immutable and the static key would prevent cache updates.

Changes reviewed:

• Lines 125-127: Changed from key: static to key: astro-assets-${{ hashFiles('src/assets/**') }} with restore-keys: astro-assets-

This follows GitHub Actions caching best practices:

• Content-based key ensures cache invalidation when assets change
• restore-keys provides partial cache hits to avoid full reprocessing
• Proper namespacing with astro-assets- prefix

The change is minimal, targeted, and correctly solves the described problem of redundant asset reprocessing and excessive deploy preview uploads. LGTM.

github run