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

[red-hat-konflux]

This PR contains the following updates:

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

---

Release Notes

actions/cache (actions/cache)

v6.1.0

Compare Source

What's Changed

• Bump @​actions/cache to v6.1.0 - handle read-only cache access by @​jasongin in #​1768

Full Changelog: actions/cache@v6...v6.1.0

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 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

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[coderabbitai]

Walkthrough

The GitHub Actions test workflow updates cache steps in the install, test-component, and test-storybook jobs from actions/cache@v5 to actions/cache@v6.

Changes

CI cache action upgrade

Layer / File(s)	Summary
Cache step version bumps .github/workflows/test.yml	The install, test-component, and test-storybook jobs switch their cache steps to actions/cache@v6, including the custom Cypress-related cache entries in test-component.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR has useful release notes, but it does not follow the template and is missing the required issue link and checklist/AI disclosure sections.	Add the required Description section with a 2-3 sentence summary, include the RHCLOUD issue link, and fill or explicitly mark the checklist and AI disclosure sections.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly states the main change: updating actions/cache from v5 to v6.
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.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

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

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/test.yml:
- Line 22: The workflow still uses tag-pinned actions/cache references, which
violates the unpinned-uses policy; update each actions/cache usage in the test
workflow to the intended release commit SHA instead of `@v6`. Make sure all four
occurrences are changed consistently so the cache step is pinned securely.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 579abfa5-8271-4e1f-a4a2-f9cebf4dea2f

📥 Commits

Reviewing files that changed from the base of the PR and between 472e460 and cce4f1f.

📒 Files selected for processing (1)

• .github/workflows/test.yml

[coderabbitai]

🔒 Security & Privacy | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

sed -n '1,140p' .github/workflows/test.yml

Repository: RedHatInsights/learning-resources

Length of output: 3760

---

🏁 Script executed:

sed -n '1,140p' .github/workflows/test.yml

Repository: RedHatInsights/learning-resources

Length of output: 3760

---

Pin actions/cache to a commit SHA.
All four uses: actions/cache@v6 entries are still tag-pinned, so the workflow remains vulnerable to tag retargeting and still violates the unpinned-uses policy. Replace them with the intended release commit SHA.

🧰 Tools

🪛 zizmor (1.26.1)

[error] 22-22: unpinned action reference (unpinned-uses): action is not pinned to a hash (required by blanket policy)

(unpinned-uses)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/test.yml at line 22, The workflow still uses tag-pinned
actions/cache references, which violates the unpinned-uses policy; update each
actions/cache usage in the test workflow to the intended release commit SHA
instead of `@v6`. Make sure all four occurrences are changed consistently so the
cache step is pinned securely.

Source: Linters/SAST tools