[dependabot]

Bumps jdx/mise-action from 5.2.0 to 5.2.3.

Release notes

Sourced from jdx/mise-action's releases.

v5.2.3: Faster cache key computation in large workspaces

The cache key no longer comes from searching the whole workspace for mise config files. In repos that already contain node_modules or vendor/bundle, this removes a delay of several minutes in "Restoring mise cache".

Fixed

• "Restoring mise cache" no longer takes minutes after installing dependencies. To build the cache key, the action used to match about 25 **/… glob patterns. That meant it walked every subdirectory of the workspace, including node_modules and vendor/bundle, before checking the cache at all. When the action ran after a step like pnpm install or ruby/setup-ruby with bundler-cache: true, this could take 3–7 minutes. The action now looks for mise config files the same way mise does: only in the working directory and each parent directory up to the workspace root. It checks for mise.toml, .mise.toml, .config/mise/…, conf.d fragments, .tool-versions, and their local, env-specific and .lock variants. The step also logs Hashed mise config files in N.Ns. (#703 by @​jdx and @​corsicanec82)
  • If you set a custom cache_key that doesn't use {{file_hash}} or {{default}}, the action no longer hashes config files at all.
  • Config files in subdirectories, such as monorepo sub-projects, no longer affect the cache key. mise only loads them with --monorepo.
  • Cache keys change, so the first run after you upgrade will miss the cache.

New Contributors

• @​corsicanec82 made their first contribution in 91e7f82 (#703)

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

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

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

v5.2.1: Require the signed packslip for mise 2026.9.3 and later

The action now refuses to install mise 2026.9.3 or later if the release's signed packslip is missing. This closes a gap where verification could be downgraded to the weaker checksum check.

Fixed

• A missing packslip no longer weakens the check on recent mise releases. v5.2.0 started checking the mise binary against the release's signed packslip.sigstore.json. If that file wasn't found, though, the action quietly fell back to the minisign-signed SHASUMS256 checksums. Anyone who could hide the file could force the weaker check. Every mise release from 2026.9.3 on includes a packslip, so for those versions a missing bundle now stops the install with an error like this:

  mise v2026.10.11 must ship a signed packslip, but https://github.com/jdx/mise/releases/download/v2026.10.11/packslip.sigstore.json was not found
  

  Releases before 2026.9.3 don't include a packslip, so they're still checked against the signed checksums. A version string that isn't three dot-separated numbers also requires a packslip. If you set the sha256 input, it still takes precedence over both checks. A packslip that fails verification still never falls back to the checksums. (#695 by @​jdx)

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

Changelog

Sourced from jdx/mise-action's changelog.

Changelog

---

5.2.4 - 2026-10-26

🐛 Bug Fixes

• (cache) reuse signed checksums saved with a cached mise (#708) by @​jdx in #708

---

5.2.3 - 2026-10-24

🐛 Bug Fixes

• (cache) hash mise config files without walking the workspace (#703) by @​jdx in #703

---

5.2.2 - 2026-10-21

🐛 Bug Fixes

• hash conf.d config fragments in cache key (#698) by @​rileymichael in #698

New Contributors

• @​rileymichael made their first contribution in #698

---

5.2.1 - 2026-10-19

🐛 Bug Fixes

• require the signed packslip for mise 2026.9.3 and later (#695) by @​jdx in #695

---

5.2.0 - 2026-10-16

🚀 Features

• (cache) rebuild the cache every 30 days by default (#689) by @​jdx in #689
• (cache) retry throttled cache restores and saves (#692) by @​jdx in #692
• verify the mise binary against its signed packslip (#693) by @​jdx in #693

🐛 Bug Fixes

• export the PATH entries mise reports with mise env --paths (#685) by @​jdx in #685

🔍 Other Changes

• Use monorepo install when configured (#679) by @​zeitlinger in #679

... (truncated)

Commits

• 82a612c chore: release v5.2.3 (#704)
• 2d0418b chore(deps): update dependency hk to latest (#705)
• e891dde chore(deps): update jdx/mise-action action to v5.2.0 (#706)
• 91e7f82 fix(cache): hash mise config files without walking the workspace (#703)
• 9a35c22 chore(deps): update github actions (#701)
• 8418fed chore: release v5.2.2 (#699)
• bb33e9b chore(deps): update communique, hk in mise.lock (#700)
• 0cc9f84 fix: hash conf.d config fragments in cache key (#698)
• 7ce9a02 chore(deps): lock file maintenance (#697)
• fc42bcc chore: release v5.2.1 (#696)
• Additional commits viewable in compare view

[qawatake]

@dependabot rebase

[qawatake]

@dependabot recreate

[qawatake]

Update review: jdx/mise-action 5.2.0 → 5.2.3

Final decision: Proceed (実施)
Risk: Low — all axes low: patch-level action update, workflow-only, mise and tool versions are pinned so CI/release toolchain does not drift; supply chain checked (see below)
Review type: Approve
Release/deploy: Not needed (no-release) — workflow-only change (.github/workflows/*); no build input changes. This repo has no release workflow.

Changes reviewed (2.1)

• Note: after @dependabot recreate (the rebase request was not acted on) this PR was regenerated from 5.2.2 to 5.2.3, so the review covers 5.2.3.
• Primary sources: release notes v5.2.1, v5.2.2, v5.2.3; compare v5.2.0...v5.2.2 (action.yml, src/index.ts, dist/index.js grep; upstream research for 5.2.2 reused, basis: tag commit 8418fedb verified earlier) and compare v5.2.2...v5.2.3 read for this review (5 commits: renovate chores, fix(cache): hash mise config files without walking the workspace (#703), release commit; src/config-hash.ts / src/index.ts patches read: path/glob logic only, no new network access or command execution). The SHA pinned in this PR, 82a612c5ab8bcda7cc5db6b7e81a8e7584c3dc6e, equals the upstream v5.2.3 tag commit (lightweight tag, contained in main, commit verified).
• Version range: 5.2.0 → 5.2.1 → 5.2.2 → 5.2.3.
• Behavior changes: 5.2.1 — for mise ≥ 2026.9.3 a missing packslip.sigstore.json is now a hard error (no downgrade to minisign); 5.2.2 — cache key also hashes conf.d/*.toml fragments; 5.2.3 — config files for the cache key are looked up only in the working dir and its parents (no more walking node_modules), cache keys change once (one cache miss after upgrade). No change to inputs' defaults, outputs, permissions or node runtime (node24).

Impact and adequacy (2.2, 2.3)

Change	Affected / not affected	Basis	PR handling adequate?
packslip mandatory for mise ≥ 2026.9.3	Not affected	every jdx/mise-action step pins version: 2026.8.3 (git grep -A3 jdx/mise-action .github)	Yes
cache key computation (5.2.2/5.2.3)	One cache miss only	the repo has only a root mise.toml (no conf.d, .config/mise/, .tool-versions, sub-project configs), so the hashed set is the same file; versions come from the pinned mise and mise.toml, not from the cache	Yes
tool versions across 30-day cache rotation (introduced in 5.2.0, already on main)	Known constraint	mise.toml pins pnpm 10.34.7 but node only as "24", so node 24.x minor can change when the cache rotates; unchanged by this PR	n/a (pre-existing)
all uses updated	Yes	all 3 jdx/mise-action uses in ci.yml now point to 82a612c5… (diff against current main)	Yes

Verification (2.4)

• CI on the recreated head 80d1889 (base = current main 31e7bec, after the electron fix #58): build, e2e, test-e2e-tools passed (run 41180285787).
• node scripts/check-actions-pinned.mjs passes in CI (all actions SHA-pinned).
• This PR's own CI runs the new action (the ci.yml jobs use it), so mise install/cache with v5.2.2 is exercised directly.

Rollback, supply chain, license (2.5, 2.6, 2.7)

• Rollback: revert the commit; no side effects (cache entries are just re-created).
• Supply chain: release by github-actions[bot] via release-plz (same as previous releases), immutable releases, tag commits signed/verified (jdx), contained in main; v5.2.3 published 2026-10-24 (7 days), v5.2.2 10 days. dist/ grows with the bundled packslip/sigstore-js (introduced in 5.2.0, already on main).
• License: MIT → MIT (same LICENSE blob).

Block conditions

• Hit: none.

Requests

• None.

Unverified / notes for reviewers (2.9)

• dist/index.js was not rebuilt from source to confirm reproducibility (upstream release workflow commits the bundle).
• Merge order: workflow-only PRs do not touch the lockfile; landed after the electron security fix so CI could run past the pnpm audit step.