chore(deps): update sonarsource/ci-github-actions action to v1.3.30

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
SonarSource/ci-github-actions	action	patch	1.3.29 → 1.3.30

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

SonarSource/ci-github-actions (SonarSource/ci-github-actions)

v1.3.30

Compare Source

What's Changed

Improvements

• Update GitHub actions by @​renovate[bot] in #​239

  Package	Type	Update	Change
  SonarSource/gh-action_cache	action	patch	v1.4.2 → v1.4.3

  This release sets AWS S3 as the default cache backend for gh-action_cache.
  Use CACHE_BACKEND env var to use GitHub cache backend.
  Use CACHE_IMPORT_GITHUB env var to opt-in/out migration scenario from GitHub to S3.

Full Changelog: SonarSource/ci-github-actions@1.3.29...1.3.30

---

Configuration

📅 Schedule: Branch creation - "after 7am every weekday,before 7pm every weekday" in timezone CET, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, 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.

[hashicorp-vault-sonar-prod]

Renovate Jira issue ID: SLCORE-2268

[sonar-review-alpha]

Summary

Updates SonarSource/ci-github-actions action from v1.3.29 to v1.3.30 across all workflow files. The underlying change upgrades gh-action_cache to v1.4.3, which changes the default cache backend from GitHub cache to AWS S3. This is a dependency patch update that affects caching behavior in builds and QA workflows.

What reviewers should know

This is a routine dependency update. All 9 references to the action in build.yml and shadow_scans.yml were consistently updated. Review: Check whether the S3 default cache backend aligns with your infrastructure setup. If you need GitHub cache instead, set CACHE_BACKEND: github in workflow env vars. The cache step is used in build and test-and-promote jobs, so the change could affect build performance/caching behavior. No code logic changes, all updates are to action references and version comments.

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[sonar-review-alpha]

LGTM! ✅

🗣️ Give feedback

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube