chore(ci): Update actions/cache action to v5 - autoclosed

[kthy]

@coderabbitai ignore

This PR contains the following updates:

Package	Type	Update	Change
actions/cache	action	major	v1 → v5

---

Release Notes

actions/cache (actions/cache)

v5

Compare Source

v4

Compare Source

v3

Compare Source

v2

Compare Source

---

Configuration

📅 Schedule: (in timezone Europe/Berlin)

• Branch creation
  • "before 9am"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated the GitHub Actions cache step in the R-CMD-check workflow from version 1 to version 5. The cache configuration (path, key, restore-keys inputs) remains unchanged. This is a routine dependency update to leverage improvements in the newer action version.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/R-CMD-check.yaml	Updated actions/cache from @v1 to @v5; cache configuration inputs unchanged

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A cache so swift, now version five,
Dependencies kept fresh and alive,
No logic changed, just cleaner ways,
To speed the checks through build-time days,
Small hops improve the GitHub dance!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title accurately describes the main change: updating the actions/cache GitHub Action from v1 to v5, which is clear, specific, and concise.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.github/workflows/R-CMD-check.yaml (1)

21-25: Update ubuntu-20.04 to avoid workflow failures after April 15, 2025.

Ubuntu 20 hosted runner image is being retired by April 15, 2025, and GitHub recommends updating workflows to use ubuntu-22.04 or ubuntu-24.04.

While this is not part of the current PR, it's critical to address soon to prevent workflow failures.

🔧 Proposed fix

        config:
          - {
-              os: ubuntu-20.04,
+              os: ubuntu-22.04,
              r: release,
              rspm: 'https://packagemanager.rstudio.com/cran/__linux__/focal/latest'
            }

Note: You may also need to update the RSPM URL from focal (Ubuntu 20.04) to jammy (Ubuntu 22.04).

🧹 Nitpick comments (1)

.github/workflows/R-CMD-check.yaml (1)

32-32: Consider updating other actions in this workflow.

While reviewing the cache action update, I noticed other actions that could benefit from updates:

• Line 32: actions/checkout@v2 → Consider updating to @v4
• Line 90: actions/upload-artifact@master → Artifact actions v3 are being deprecated by January 30th, 2025, consider updating to @v4

These updates can be addressed in a separate PR but are worth considering for consistency and to avoid future deprecation issues.

Also applies to: 90-90

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 13a062d and f933624.

📒 Files selected for processing (1)

• .github/workflows/R-CMD-check.yaml

🔇 Additional comments (1)

.github/workflows/R-CMD-check.yaml (1)

47-53: LGTM! Essential update to prevent workflow failures.

The cache action v1 was fully retired on March 1st, 2025, and workflows using deprecated versions will fail. This update is fully backward compatible and will not break your workflow.

Additional benefits of v5:

• Up to ~80% faster cache upload duration on GitHub-hosted runners
• Integrates with the new cache backend service for improved performance and reliability

The existing cache configuration (path, key, restore-keys) works without modification.