Skip to content

ci: bump actions/cache v2 to v4#66

Draft
wcchang1115 wants to merge 1 commit into
mainfrom
fix/ci-cache-v4
Draft

ci: bump actions/cache v2 to v4#66
wcchang1115 wants to merge 1 commit into
mainfrom
fix/ci-cache-v4

Conversation

@wcchang1115

Copy link
Copy Markdown
Contributor

Background

GitHub has shut down the cache service backend for actions/cache v1/v2. Any workflow run that declares actions/cache@v2 is now automatically failed (not just warned), which is breaking every Go test run — e.g. run 29621107772.

Fix

Bump actions/cache@v2@v4 in .github/workflows/ci.yml.

Notes

  • No config migration needed. This workflow only uses path / key / restore-keys, which are unchanged from v2 to v4 — the bump alone is sufficient.
  • Why v4, not v3. The deprecation notice suggests v3 or v4, but v3's node16 runtime is itself deprecated, so v4 is the durable target.
  • Out of scope (deliberately). The run also warns that actions/setup-go@v2 and actions/checkout@v2 (it-test-s3 job) are on the deprecated Node 20 runtime. Those are warnings, not failures — left for a separate change to keep this PR to the one thing unblocking CI.

GitHub has shut down the cache service backend for actions/cache v1/v2,
so any run declaring actions/cache@v2 is now automatically failed.

The path/key/restore-keys inputs are unchanged from v2 to v4, so no
config migration is needed beyond the version bump. Use v4 rather than
v3 since v3's node16 runtime is also deprecated.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Wei-Chun, Chang <wcchang@infuseai.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant