chore(deps): bump actions/cache from 4.3.0 to 5.0.0

[dependabot]

Bumps actions/cache from 4.3.0 to 5.0.0.

Release notes

Sourced from actions/cache's releases.

v5.0.0

[!IMPORTANT] actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

If you are using self-hosted runners, ensure they are updated before upgrading.

---

What's Changed

• Upgrade to use node24 by @​salmanmkc in actions/cache#1630
• Prepare v5.0.0 release by @​salmanmkc in actions/cache#1684

Full Changelog: actions/cache@v4.3.0...v5.0.0

Changelog

Sourced from actions/cache's changelog.

Releases

Changelog

5.0.0

[!IMPORTANT] actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

4.3.0

• Bump @actions/cache to v4.1.0

4.2.4

• Bump @actions/cache to v4.0.5

4.2.3

• Bump @actions/cache to v4.0.3 (obfuscates SAS token in debug logs for cache entries)

4.2.2

• Bump @actions/cache to v4.0.2

4.2.1

• Bump @actions/cache to v4.0.1

4.2.0

TLDR; The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.

The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.

We are deprecating some versions of this action. We recommend upgrading to version v4 or v3 as soon as possible before February 1st, 2025. (Upgrade instructions below).

If you are using pinned SHAs, please use the SHAs of versions v4.2.0 or v3.4.0

If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.

Upgrading to the recommended versions will not break your workflows.

4.1.2

• Add GitHub Enterprise Cloud instances hostname filters to inform API endpoint choices - #1474
• Security fix: Bump braces from 3.0.2 to 3.0.3 - #1475

4.1.1

... (truncated)

Commits

• a783357 Merge pull request #1684 from actions/prepare-cache-v5-release
• 3bb0d78 docs: highlight v5 runner requirement in releases
• 054c1f2 readme note
• 0762978 docs: update README for v5 release with Node 24 and runner version requirements
• 9e02f8f Prepare v5.0.0 release
• ffd11d2 Merge pull request #1630 from salmanmkc/node24
• 5bb537b undo readme changes
• 94a1e4b chore: regenerate package-lock.json
• 70a5ee3 chore: rebuild dist with version 4.3.0
• 5267c61 chore: set version to 4.3.0 for prepare release PR
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: skip news. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0%. Comparing base (e1ec0a7) to head (4492250).

Additional details and impacted files

@@     Coverage Diff     @@
##   main   #248   +/-   ##
===========================
===========================

🚀 New features to boost your workflow:

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

[Artmann]

@CodeRabbit Please review this

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Find all GitHub workflow files
fd -e yml -e yaml . .github/workflows

# Display their contents to see actions/cache usage and runner configuration
echo "=== Workflow files content ==="
fd -e yml -e yaml . .github/workflows --exec cat {}

Length of output: 15812

---

🏁 Script executed:

#!/bin/bash
# Get the PR diff to see what's actually being changed
gh pr view 248 --json files --jq '.files[] | {path: .path, additions: .additions, deletions: .deletions}'

# Get the actual diff
gh pr diff 248

Length of output: 1002

---

@Artmann

Summary: The dependency update looks good. GitHub-hosted runners will automatically meet the v5.0.0 requirements (Node.js 24, runner version 2.327.1+).

Issue Found:

The inline version comments weren't updated. Both instances still show # v4 when they should reflect # v5 or # v5.0.0:

- name: Cache npm files
  uses: actions/cache@a7833574556fa59680c1b7cb190c1735db73ebf0 # v5
  
- name: Cache the out/ directory  
  uses: actions/cache@a7833574556fa59680c1b7cb190c1735db73ebf0 # v5

Compatibility: ✅ No concerns. The workflow uses ubuntu-latest, which will have the required runner version.

[Artmann]

@coderabbitai I've update the comments

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@Artmann Thanks! The version comments are now accurate. 👍

---

If you found this review helpful, would you consider giving us a shout-out on X?

Thank you for using CodeRabbit!