[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending
jdx/mise-action	action	patch	v5.2.1 → v5.2.2	v5.2.3

---

Release Notes

jdx/mise-action

v5.2.2: : Include conf.d config fragments in the cache key

Compare Source

The cache key now includes mise conf.d/*.toml config fragments, so changing one of them invalidates the cache.

Fixed

• Editing a conf.d fragment now invalidates the cache. mise can load config from single-file fragments in conf.d/ directories, but the action didn't hash those files when it built the cache key. As a result, adding or changing tools in a fragment could restore an outdated cache. The cache key now also hashes conf.d/*.toml files under .config/mise/, .mise/ and mise/. If your repo already uses these fragments, the cache will miss once after you upgrade. (#​698 by @​rileymichael)

New Contributors

• @​rileymichael made their first contribution in #​698

Full Changelog: jdx/mise-action@v5.2.1...v5.2.2

---

Configuration

📅 Schedule: (in timezone CET)

• 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: 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: SONARJAVA-7244

[gitar-bot]

CI failed: The one CI failure is an infrastructure outage: the SonarQube server returned HTTP 503 for /api/server/version, so the Maven Sonar scanner failed during bootstrap after tests passed. It is unrelated to the mise-action v5.2.2 update.

Overview

One unique error template was analyzed from 1 log (job 121542757004). The build and tests passed, and the failure is a transient SonarQube server unavailability (HTTP 503) during scanner bootstrap. Overall assessment: infrastructure failure, not caused by this change.

Failures

SonarQube server returned HTTP 503 during scanner bootstrap (confidence: high)

• Type: infrastructure
• Affected jobs: 121542757004
• Related to change: no (related_to_pr: no)
• Root cause: The sonar-maven-plugin failed with Failed to query server version: GET <server>/api/server/version failed with HTTP 503 Service Unavailable, which caused the SonarJava module to fail with BUILD FAILURE. The mise setup steps completed successfully and the logs contain no evidence linking the jdx/mise-action bump to the 503 response.
• Suggested fix: Verify the SonarQube server health at the configured SONAR_HOST_URL and rerun the job once /api/server/version responds successfully. No repository code change is indicated.

Summary

• Change-related failures: None. The only failure is unrelated to the PR's mise-action update.
• Infrastructure/flaky failures: 1 (SonarQube HTTP 503 during scanner bootstrap).
• Recommended action: Rerun the CI job after confirming SonarQube availability. The mise-action v5.2.2 update does not need to be reverted based on this log.

Code Review ✅ Approved

🟡 Medium risk · Updating the pinned mise action across CI workflows changes cache keys for conf.d configs, which could cause cache misses and slower jobs.

Bumps the jdx/mise-action GitHub Action from v5.2.1 to v5.2.2, which includes conf.d/*.toml config fragments in the cache key so edits to those fragments invalidate the cache. No issues found.

Verification Rules 2/3 met

Rules 1 failed 2 passed

❌ Approved GitHub Actions runners - Retired label sonar-xs-public is used in build.yml (line 484) and PrepareNextIteration.yml (line 13); replace with approved sonar-xs (see https://xtranet-sonarsource.atlassian.net/wiki/spaces/Platform/pages/3694231566/GitHub+Actions+Runners+-+GitHub).
✅ Internal artifact registries
✅ Repository license compliance

Functional validation No results

Auto-approval Not enabled

Set up

_{For more verification details, comment gitar display:verbose.}

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing compact verification results.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[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
0.0% Duplication on New Code

See analysis details on SonarQube