chore(deps): update actions/cache action to v6

[renovate]

This PR contains the following updates:

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

---

Release Notes

actions/cache (actions/cache)

v6.0.0

Compare Source

What's Changed

• Update packages, migrate to ESM by @​Samirat in #​1760

Full Changelog: actions/cache@v5...v6.0.0

v6

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

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

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

Summary by CodeRabbit

• Chores
  • Updated build infrastructure components to enhance system stability and compatibility with current platform standards.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 8c758544-318a-44d6-be98-0d70566d39b1

📥 Commits

Reviewing files that changed from the base of the PR and between 7dd3765 and fb19cd5.

📒 Files selected for processing (2)

• .github/actions/artifact-cache/action.yml
• .github/workflows/agents-auto-pilot.yml

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• stranske/Workflows (auto-detected)

📜 Recent review details

⏰ Context from checks skipped due to timeout. (1)

• GitHub Check: one-pdf-pilot-golden

🧰 Additional context used

📓 Path-based instructions (2)

**/.github/workflows/*.yml

📄 CodeRabbit inference engine (CLAUDE.md)

Reference reusable workflows from stranske/Workflows with @main unless intentionally pinning to an exact commit SHA for a controlled reason.

Reference reusable workflows with @main unless intentionally pinning to an exact commit SHA for a controlled reason.

Files:

• .github/workflows/agents-auto-pilot.yml

{**/.github/workflows/agents-*.yml,**/.github/workflows/autofix.yml,**/.github/codex/**}

📄 CodeRabbit inference engine (CLAUDE.md)

For synced workflows, prompts, scripts, and consumer docs (e.g., agents-*.yml, autofix.yml, .github/codex/ prompts) — fix them in stranske/Workflows first, not locally in the consumer repo.

Files:

• .github/workflows/agents-auto-pilot.yml

🔀 Multi-repo context stranske/Workflows

Based on my comprehensive exploration of the stranske/Workflows repository, I have gathered sufficient cross-repository context to inform the review.

Summary of Findings

The PR updates actions/cache from v5 to v6 in only 2 locations, creating an incomplete migration pattern across the repository. Here are the key findings:

stranske/Workflows [::stranske/Workflows::]

1. Partial v6 Migration - Inconsistency Risk

The PR updates:

• .github/actions/artifact-cache/action.yml:62 — composite action wrapper uses actions/cache@v5 → v6
• .github/workflows/agents-auto-pilot.yml:225 — direct cache step uses actions/cache@27d5ce7f... (v5 commit) → v6

But leaves these workflows on v5:

• .github/workflows/health-42-actionlint.yml — 2 v5 references (not updated)
• .github/workflows/maint-52-validate-workflows.yml — 1 v5 reference (not updated)
• .github/workflows/reusable-10-ci-python.yml — 7 v5 references (not updated)
• .github/workflows/reusable-agents-verifier.yml — 2 v5 references (not updated)

Implication: Post-merge, the repository will have mixed v5/v6 usage across workflows, potentially causing inconsistent caching behavior and making future maintenance harder.

2. Active Consumers of Updated artifact-cache Action

The artifact-cache composite action (which embeds the cache action) is actively used by:

• .github/workflows/agents-weekly-metrics.yml — weekly metrics artifact caching
• .github/workflows/maint-coverage-guard.yml — coverage trend/history/payload artifact caching (3 invocations)
• .github/workflows/reusable-10-ci-python.yml — CI artifact caching via .workflows-lib reference
• .github/workflows/selftest-reusable-ci.yml — self-test report artifact caching

Implication: Updating the artifact-cache action to v6 will affect caching behavior in these workflows upon merge.

3. Compatible Interface Design

The artifact-cache action maintains full parameter compatibility between v5 and v6 (no breaking changes in path and key configuration), suggesting the upgrade should be transparent for all consumers.

🔇 Additional comments (2)

.github/actions/artifact-cache/action.yml (1)

62-62: LGTM!

.github/workflows/agents-auto-pilot.yml (1)

225-225: 📐 Maintainability & Code Quality

Update agents-auto-pilot.yml in stranske/Workflows first, not in this consumer repo.

This is a synced workflow file (agents-*.yml pattern). Per coding guidelines, synced workflows must be fixed in stranske/Workflows first, then synced to consumers. The PR updates this file in Pension-Data to actions/cache v6, but the source file in stranske/Workflows remains on v5. Revert this change here and apply the upgrade in stranske/Workflows instead.

			> Likely an incorrect or invalid review comment.

---

📝 Walkthrough

Walkthrough

Two GitHub Actions configuration files are updated to use actions/cache@v6 instead of actions/cache@v5. The composite artifact-cache action and the agents-auto-pilot workflow each change a single line referencing the cache action version; no other logic or configuration is modified.

Changes

actions/cache v5 → v6 upgrade

Layer / File(s)	Summary
Update actions/cache to v6 .github/actions/artifact-cache/action.yml, .github/workflows/agents-auto-pilot.yml	Both the composite artifact-cache action's restore step and the agents-auto-pilot workflow's pip-caching step replace their actions/cache@v5 reference with actions/cache@v6; all surrounding step names, ids, and with configuration remain unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• stranske

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title clearly and accurately describes the main change: updating the actions/cache action to version 6.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/actions-cache-6.x

---

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

[github-actions]

Workflow state fingerprint for Agents Gate Followups. Do not edit.

[github-actions]

Workflow state fingerprint for Keepalive Loop Reporter. Do not edit.

[agents-workflows-bot]

Workflow source needed

PR #606 needs either a linked GitHub issue or one valid non-issue Workflow Source before PR metadata automation can manage it safely.

Please do one of:

• Add <!-- meta:issue:123 --> or a normal Closes #123 / Related to #123 line.
• Check one Workflow Source option in the PR body.
• Add a hidden marker such as <!-- workflow-source:local_request -->, <!-- workflow-source:manual_remote -->, <!-- workflow-source:review_followup -->, <!-- workflow-source:sync_campaign -->, or <!-- workflow-source:dependabot -->.
• Add a workflow source label such as workflow:source-direct-pr, workflow:source-local-request, workflow:source-review-followup, workflow:source-sync, or workflow:no-automation.

Once a valid source is present, this warning will not be reposted.

[stranske]

Closing as superseded: superseded by stranske/Workflows#2520, which updates actions/cache v6 in the Workflows source/template before Maint 68 syncs consumers. Direct consumer PRs for synced workflow files would create ownership drift; the replacement should come from the Workflows source PR and the next Maint 68 sync wave.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 6.x releases. But if you manually upgrade to 6.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.