Skip to content

ci: bump actions/cache v2 → v4 so the GitHub workflows can run#18

Open
leeguooooo wants to merge 1 commit into
mCaptcha:masterfrom
leeguooooo:ci-bump-actions-cache-v4
Open

ci: bump actions/cache v2 → v4 so the GitHub workflows can run#18
leeguooooo wants to merge 1 commit into
mCaptcha:masterfrom
leeguooooo:ci-bump-actions-cache-v4

Conversation

@leeguooooo

Copy link
Copy Markdown

Follow-up to the offer in #17.

linux.yml still pins actions/cache@v2. Since Dec 2024 GitHub auto-fails any run using actions/cache@v1/v2 before the job even starts (the toolkit cache service was shut down), so the stable/nightly jobs go red without ever reaching the build. v4 is a drop-in replacement — same path/key inputs, no other changes needed.

This is just the companion to your e3f456f (which refreshed actions/checkout); cache was the one GitHub still hard-fails on.

Out of scope (left alone on purpose — yours to decide): the actions-rs/* actions are archived/Node12 and emit deprecation warnings, and actions-rs/clippy-check@v1 can't post annotations from fork PRs (Resource not accessible by integration). Those only warn; they don't hard-fail the run like cache@v2 does.

GitHub now auto-fails any workflow run that uses actions/cache@v1/v2
before the job starts (toolkit cache package shutdown, Dec 2024), so the
stable/nightly jobs in linux.yml never reach the build step. Bumping to
v4 (drop-in: same path/key inputs) lets them run again. Companion to
e3f456f which refreshed actions/checkout.
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