[dependabot]

Bumps the actions-all group with 2 updates in the / directory: jdx/mise-action and zizmorcore/zizmor-action.

Updates 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.5 - 2026-10-30

🔍 Other Changes

• bump versions (#710) by @​deining in #710

---

5.2.4 - 2026-10-27

🐛 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

... (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

Updates zizmorcore/zizmor-action from 0.7.1 to 0.8.0

Release notes

Sourced from zizmorcore/zizmor-action's releases.

v0.8.0

The action now supports prereleases.

The default has not changed, but you can pass a prerelease version of zizmor or version: prerelease to get whatever latest prerelease the action knows about.

What's Changed

• Support prereleases by @​woodruffw in zizmorcore/zizmor-action#182
• Sync zizmor versions by @​github-actions[bot] in zizmorcore/zizmor-action#184

Full Changelog: zizmorcore/zizmor-action@v0.7.1...v0.8.0

Commits

• 53290ba Sync zizmor versions (#184)
• 76da2ee Support prereleases (#182)
• fb1d87b chore(deps): bump the github-actions group with 2 updates (#180)
• be36601 README: bump pins (#179)
• See full diff in compare view

[Copilot]

🟢 Approval recommended

No active review issues are reported for the GitHub Actions version updates.

No open issues 🎉

What changed in this PR

Updates two SHA-pinned GitHub Actions used for tool setup and workflow security scanning.

Changes:

• Bumps jdx/mise-action from 5.2.0 to 5.2.3 in lint and binding-generation workflows.
• Bumps zizmorcore/zizmor-action from 0.7.1 to 0.8.0.
• Preserves existing workflow configuration and full commit-SHA pinning.

File	Description
.github/​workflows/​zizmor.yml	Updates the zizmor security-scanning action.
.github/​workflows/​update-bindings.yml	Updates mise setup for binding generation.
.github/​workflows/​lint.yml	Updates mise setup in both lint jobs.

_{Review effort: Balanced}

[cloudsmith-bot]

@dependabot rebase