[dependabot]

Bumps the github-actions group with 2 updates: jdx/mise-action and alibaba/open-code-review.

Updates jdx/mise-action from 5.2.0 to 5.2.2

Release notes

Sourced from jdx/mise-action's releases.

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

• 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)
• 720e96a fix: require the signed packslip for mise 2026.9.3 and later (#695)
• See full diff in compare view

Updates alibaba/open-code-review from 1.13.1 to 1.13.3

Release notes

Sourced from alibaba/open-code-review's releases.

v1.13.3

🐛 Bug Fixes

• fix(tool): report an empty code_comment batch instead of success (#1773)
• fix(mcp): follow tools/list pagination when caching server tools (#1770)
• fix(ci): prevent PR policy checkout state pollution (#1783)

Other Changes

• include pkgs/ as a provider directory for NixPkgs (#1642)

Full Changelog: alibaba/open-code-review@v1.13.2...v1.13.3

v1.13.2

🚀 Features

• feat(allowlist): add Shader Languages support (#975)
• feat(language): support for Nushell language (#956)
• feat(rules): add PowerShell review support (#970)

🐛 Bug Fixes

• fix(scan): resolve --path like the filesystem and reject nonexistent paths (#1709)

📖 Documentation

• docs(contributing): update directory structure and descriptions across multiple languages (#1729)
• docs(contributing): refresh Project Structure and add chatgptauth (#1721)

Other Changes

• ci: enforce PR commit policy (#1775)
• terraform: adding .tofu extension used by opentofu (#1464)

Full Changelog: alibaba/open-code-review@v1.13.1...v1.13.2

Commits

• 375f64c fix(tool): report an empty code_comment batch instead of success (#1773)
• 410ddb8 fix(mcp): follow tools/list pagination when caching server tools (#1770)
• 313519f include pkgs/ as a provider directory for NixPkgs (#1642)
• c0d623a fix(ci): prevent PR policy checkout state pollution (#1783)
• 55450a9 ci: enforce PR commit policy (#1775)
• 1325261 feat(allowlist): add Shader Languages support (#975)
• 27def86 fix(scan): resolve --path like the filesystem and reject nonexistent paths (#...
• 6d68b1a feat(language): support for Nushell language (#956)
• 46790d9 feat(rules): add PowerShell review support (#970)
• 0ac5b40 docs(contributing): update directory structure and descriptions across multip...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.