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

[thomhurst]

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: Enabled.

♻ 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 has been generated by Mend Renovate.

[claude]

Review: Dependency update — actions/cache v5 → v6

This is a routine Renovate-generated bump of actions/cache from v5 to v6 across all four workflow files:

• .github/workflows/cloudshop-example.yml
• .github/workflows/deploy-pages-test.yml
• .github/workflows/dotnet.yml
• .github/workflows/link-check.yml

Assessment

The change is minimal, mechanical, and consistent — all four occurrences are updated in lockstep. The v6 release (v6.0.0) is a non-breaking update that migrates the action's internals to ESM; it carries no API surface changes that would affect the cache key, path, or restore-keys configurations used here.

No concerns:

• All usages retain their existing continue-on-error: true guards where appropriate.
• Cache key strategies and paths are unchanged.
• No pinned SHAs to update (the repo uses floating major-version tags consistently).

One minor observation (non-blocking)

Some actions in these workflows pin to exact versions (e.g., actions/checkout@v7.0.0) while others use floating major tags (e.g., actions/cache@v6). This inconsistency is pre-existing and out of scope here, but worth aligning on a policy at some point — either pin everything to SHAs for full reproducibility, or accept floating major tags uniformly. Not something to fix in this PR.

Approved. Safe to merge.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[claude]

Code Review

This PR is a straightforward Renovate-generated dependency update bumping actions/cache from v5 to v6 across 4 CI workflow files.

Summary of Changes

• .github/workflows/cloudshop-example.yml: actions/cache@v5 → v6
• .github/workflows/deploy-pages-test.yml: actions/cache@v5 → v6
• .github/workflows/dotnet.yml: actions/cache@v5 → v6
• .github/workflows/link-check.yml: actions/cache@v5 → v6

Assessment: ✅ LGTM

The change is clean and appropriate:

1. Consistency — all 4 usages of actions/cache are updated together. No stragglers on the old version.
2. Low risk — the v6 release notes indicate the only change is an internal migration to ESM; the action interface (inputs/outputs, path/key/restore-keys) is unchanged, so no workflow logic needs to be updated.
3. Existing safety nets preserved — the two continue-on-error: true settings (in cloudshop-example.yml and dotnet.yml) are untouched, which is correct since cache misses should never block a build.
4. Scope is appropriate — purely CI tooling, no production code touched.

No issues found. Safe to merge.

[claude]

Code Review

This PR is a straightforward Renovate-generated dependency update bumping actions/cache from v5 to v6 across 4 CI workflow files.

Summary of Changes

• .github/workflows/cloudshop-example.yml: actions/cache@v5 → v6
• .github/workflows/deploy-pages-test.yml: actions/cache@v5 → v6
• .github/workflows/dotnet.yml: actions/cache@v5 → v6
• .github/workflows/link-check.yml: actions/cache@v5 → v6

Assessment: LGTM

The change is clean and appropriate:

1. Consistency — all 4 usages of actions/cache are updated together. No stragglers on the old version.
2. Low risk — the v6 release notes indicate the only change is an internal migration to ESM; the action interface (inputs/outputs, path/key/restore-keys) is unchanged, so no workflow logic needs to be updated.
3. Existing safety nets preserved — the two continue-on-error: true settings (in cloudshop-example.yml and dotnet.yml) are untouched, which is correct since cache misses should never block a build.
4. Scope is appropriate — purely CI tooling, no production code touched.

No issues found. Safe to merge.