[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-7246

[gitar-bot]

Code Review ✅ Approved

🟡 Medium risk · Updating the pinned mise action changes cache-key handling; hashing config fragments may trigger cache misses and slower workflow runs.

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 them invalidate the cache. No issues found.

Verification Rules 3/3 met

Functional validation No results

Rules 3 passed

✅ Approved GitHub Actions runners
✅ Internal artifact registries
✅ Repository license compliance

Auto-approval Not enabled

Set up

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

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

[vdiez]

Auto-approved: Renovate dependency update.