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

---

This PR was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.39%. Comparing base (4de1fd1) to head (6f2c919).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1675      +/-   ##
==========================================
- Coverage   83.40%   83.39%   -0.02%     
==========================================
  Files         395      395              
  Lines       39218    39218              
==========================================
- Hits        32710    32705       -5     
- Misses       4571     4574       +3     
- Partials     1937     1939       +2     

Flag	Coverage Δ
integration	7.29% <ø> (ø)
unit	81.47% <ø> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ALRubinger]

🤖 renovate-shepherd: escalating for human review

This is a major version bump (actions/cache → v6), which the shepherd never auto-merges — major bumps can carry breaking changes that require a human call.

• Functional CI is green (unit/integration/E2E/lint all pass).
• The only red check is codecov/project (no coverage delta on a CI-workflow-only change), which is not a code-correctness signal here.

Action needed: review the actions/cache v6 release notes / migration guide for breaking changes (notably the underlying @actions/cache major and any cache-key/restore-behavior changes), confirm our workflows are compatible, then merge manually if good.

Leaving open for a human decision.

[ALRubinger]

🛑 renovate-shepherd: escalated — needs human review

This is a major version bump (actions/cache → v6), which the unattended shepherd never auto-merges. Major GitHub Action bumps can change inputs/outputs, cache key behavior, or runtime requirements.

Please review the actions/cache v6 release notes for breaking changes (notably any cache-backend/service-version changes), confirm CI is green, then merge by hand.

[ALRubinger]

Renovate Shepherd — escalating for human review.

This is a major bump: actions/cache v5 → v6.1.0. v6.0.0 migrates the action to ESM (#1760). The unattended shepherd never auto-merges major bumps, since they can carry breaking changes (here, a runtime/packaging change to a CI action used across the workflows).

Please review the v5→v6 changelog and confirm our cache steps still behave, then merge manually. No CI failures are blocking — this is purely the major-version gate.

[ALRubinger]

renovate-shepherd: escalation — needs a human

This is a major bump (actions/cache v5 → v6) and the config does not automerge majors. A major action bump can change defaults or drop inputs, so it needs a human to read the v6 release notes and confirm the workflows still behave.

Also note codecov/project is currently red on this PR — verify whether that resolves on a re-run (codecov posts a preliminary FAILURE until all uploads land) or reflects a real dip before merging.

Leaving this open for review. Not auto-merged.

[ALRubinger]

Renovate shepherd — escalating (major bump, human review required)

This bumps actions/cache v5 → v6, a major version. All 19 CI checks are green, including every job that uses the action (Lint, all Unit Tests, Integration, Windows Release Smoke). The action's uses: interface is unchanged — v6.0.0 migrates internals to ESM and v6.1.0 adds read-only cache access handling.

The shepherd never auto-merges majors. Risk looks low given the fully-green matrix, but this needs a human to merge: gh pr merge 1675 --squash --admin --delete-branch.

[ALRubinger]

🤖 renovate-shepherd: status update — the codecov question has resolved

Following up on the open item from the earlier note rather than repeating it.

codecov/project is now green. That check was red when this PR was last triaged, and the note left it ambiguous whether it was codecov's preliminary-FAILURE behaviour or a real coverage dip. It was the former — the full rollup is now passing.

Current state: all 21 checks pass, MERGEABLE, mergeStateStatus: BLOCKED solely on REVIEW_REQUIRED. There is no CI signal left to wait on.

Status: still escalated. actions/cache v5 → v6 is a major, and majors are never auto-merged. The only thing standing between this PR and merge is a human reading the v6 release notes and confirming the cache inputs this repo uses are unchanged. Green CI is good evidence but not proof — a dropped or renamed input can degrade to a cache miss, which is silent and still green.

— renovate-shepherd