Use Node 24-native cache action#6
Conversation
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — a one-line bump of setup-nub's internal cache step from actions/cache@v4 to actions/cache@v6 to move off the deprecated Node 20 runtime.
- Bump
actions/cachev4 → v6 —action.yml:252now pinsactions/cache@v6, whoseaction.ymldeclaresusing: 'node24', eliminating GitHub's Node 20 deprecation warnings emitted byv4(using: node20) when caching is enabled.
I verified compatibility against the v6 tag directly rather than main: setup-nub consumes only path, key, and restore-keys (inputs) plus the cache-hit output (re-exported at action.yml:78 and asserted in .github/workflows/smoke.yml). All of these are present and unchanged at actions/cache@v6, so the bump is functionally transparent for this usage.
ℹ️ actions/cache v5+ drops the legacy v1 cache service
actions/cache v5 and later use the v2 cache backend exclusively; the legacy Azure-backed v1 service is no longer supported. On github.com-hosted runners this is a non-issue. It can matter for consumers running on older GitHub Enterprise Server versions whose cache service doesn't yet expose the v2 API — for them, v6 would fail to save/restore. No change requested; flagging for awareness since setup-nub is a published, externally consumed action.
Claude Opus | 𝕏

Summary
actions/cache@v4toactions/cache@v6Why
actions/cache@v4declaresusing: node20, which now produces GitHub Actions Node.js 20 deprecation warnings when setup-nub caching is enabled.actions/cache@v6declaresusing: node24with the same inputs/outputs used by setup-nub here.Validation
action.ymland all workflows with Ruby YAMLaction.ymlcontainsactions/cache@v6and noactions/cache@v4actions/cache@v6metadata declaresusing: node24git diff --checkactionlint; existing smoke workflow shellcheck warnings are unchanged fromorigin/main