build(deps): Bump actions/cache from 4 to 5

[dependabot]

Bumps actions/cache from 4 to 5.

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

v4.3.0

What's Changed

• Add note on runner versions by @​GhadimiR in actions/cache#1642
• Prepare v4.3.0 release by @​Link- in actions/cache#1655

New Contributors

• @​GhadimiR made their first contribution in actions/cache#1642

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

v4.2.4

What's Changed

• Update README.md by @​nebuk89 in actions/cache#1620
• Upgrade @actions/cache to 4.0.5 and move @protobuf-ts/plugin to dev depdencies by @​Link- in actions/cache#1634
• Prepare release 4.2.4 by @​Link- in actions/cache#1636

New Contributors

• @​nebuk89 made their first contribution in actions/cache#1620

Full Changelog: actions/cache@v4...v4.2.4

v4.2.3

What's Changed

• Update to use @​actions/cache 4.0.3 package & prepare for new release by @​salmanmkc in actions/cache#1577 (SAS tokens for cache entries are now masked in debug logs)

New Contributors

• @​salmanmkc made their first contribution in actions/cache#1577

Full Changelog: actions/cache@v4.2.2...v4.2.3

... (truncated)

Changelog

Sourced from actions/cache's changelog.

Releases

How to prepare a release

[!NOTE]
Relevant for maintainers with write access only.

1. Switch to a new branch from main.
2. Run npm test to ensure all tests are passing.
3. Update the version in https://github.com/actions/cache/blob/main/package.json.
4. Run npm run build to update the compiled files.
5. Update this https://github.com/actions/cache/blob/main/RELEASES.md with the new version and changes in the ## Changelog section.
6. Run licensed cache to update the license report.
7. Run licensed status and resolve any warnings by updating the https://github.com/actions/cache/blob/main/.licensed.yml file with the exceptions.
8. Commit your changes and push your branch upstream.
9. Open a pull request against main and get it reviewed and merged.
10. Draft a new release https://github.com/actions/cache/releases use the same version number used in package.json
    1. Create a new tag with the version number.
    2. Auto generate release notes and update them to match the changes you made in RELEASES.md.
    3. Toggle the set as the latest release option.
    4. Publish the release.
11. Navigate to https://github.com/actions/cache/actions/workflows/release-new-action-version.yml
    1. There should be a workflow run queued with the same version number.
    2. Approve the run to publish the new version and update the major tags for this action.

Changelog

5.0.3

• Bump @actions/cache to v5.0.5 (Resolves: https://github.com/actions/cache/security/dependabot/33)
• Bump @actions/core to v2.0.3

5.0.2

• Bump @actions/cache to v5.0.3 #1692

5.0.1

• Update @azure/storage-blob to ^12.29.1 via @actions/cache@5.0.1 #1685

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

... (truncated)

Commits

• cdf6c1f Merge pull request #1695 from actions/Link-/prepare-5.0.3
• a1bee22 Add review for the @​actions/http-client license
• 4695763 Add licensed output
• dc73bb9 Upgrade dependencies and address security warnings
• 345d5c2 Add 5.0.3 builds
• 8b402f5 Merge pull request #1692 from GhadimiR/main
• 304ab5a license for httpclient
• 609fc19 Update licensed record for cache
• b22231e Build
• 93150cd Add PR link to releases
• 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 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: dependencies, github-actions. Please create them before Dependabot can add them to a pull request.

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

[czprz]

Security/CI gate: I can’t approve while required checks are red.

Observed systemic issues on Dependabot PRs in this repo:

1. Dependency Review job fails with: “Dependency review is not supported on this repository… ensure Dependency graph is enabled”. This is a repo setting (Security analysis) — please enable Dependency Graph so dependency-review-action can run.
2. Docker Build job fails on .NET 10 with NETSDK1018 Invalid NuGet version string because the workflow passes a raw git SHA into -p:Version= inside the Docker build. Please switch to a SemVer-compatible version (e.g. 0.0.0+sha.<sha> or use SourceRevisionId separately).

Once those are fixed and checks rerun green, I’m happy to re-review and approve.

[czprz]

Security/CI gate: I can’t approve while required checks are red.

Observed systemic issues on Dependabot PRs in this repo:

1. Dependency Review job fails with: “Dependency review is not supported on this repository… ensure Dependency graph is enabled”. This is a repo setting (Security analysis) — please enable Dependency Graph so dependency-review-action can run.
2. Docker Build job fails on .NET 10 with NETSDK1018 (Invalid NuGet version string) because the workflow passes a raw git SHA into -p:Version= inside the Docker build. Please switch to a SemVer-compatible version (e.g. 0.0.0+sha.) and/or use SourceRevisionId separately.

Once those are fixed and checks rerun green, I’m happy to re-review and approve.

[czprz]

🔧 Needs work before merge: required checks are failing on this PR. Please fix/adjust the workflows (Dependabot permissions/secrets, dependency-review/title validation) so CI can run to green, then re-run checks. I’m not comfortable approving a dependency bump that can’t be validated by CI.

[czprz]

Looks good: actions/cache bump. Low risk.

[czprz]

✅ Looks good. Diff is limited to dependency/action version bumps; no functional code changes detected in this PR. Please ensure CI passes before merge.

[czprz]

🔧 NEEDS WORK: CI is currently failing on this PR (see checks). I can’t approve dependency bumps until the pipeline is green.

Likely themes (based on multiple open Dependabot PRs in this repo):

• PR title validation rejecting Dependabot titles
• formatting check failures
• Docker build failures
• (for Helm bumps) dependency/tooling version skew

Action:

• Please fix the underlying CI expectations (or add Dependabot exceptions where appropriate), then re-run.

I’ve looped in Legolas (code/tooling) and Aragorn (Helm/infra) to diagnose the recurring failures across these PRs.