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

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/cache	action	major	v4 -> v5

---

Release Notes

actions/cache (actions/cache)

v5

Compare Source

---

Configuration

📅 Schedule: 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
commitsar	Ready	Preview, Comment	Dec 14, 2025 10:30am

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 8b8cca7 in 45 seconds. Click for details.

• Reviewed 35 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 2 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. .github/workflows/linters.yml:15

• Draft comment:
  Update to actions/cache v5: Verify that any behavioral changes in v5 (e.g. caching restoration) don’t affect your workflow.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to verify behavioral changes in a dependency update, which violates the rule against asking the author to ensure behavior is intended or tested. It does not provide a specific suggestion or point out a specific issue.

2. .github/workflows/test.yml:15

• Draft comment:
  Update to actions/cache v5: Ensure the new version’s behavior (including restore keys) works as expected; note similar change later in the file.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to ensure that the new version's behavior works as expected, which violates the rule against asking the author to ensure behavior is intended or tested. It also mentions a similar change later in the file, which is purely informative.

Workflow ID: wflow_WdX5ymVo7Yf5uKL4

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}