[dependabot]

Bumps the actions-all group with 3 updates: jdx/mise-action, cloudsmith-io/cloudsmith-cli-action and zizmorcore/zizmor-action.

Updates jdx/mise-action from 5.2.2 to 5.2.4

Release notes

Sourced from jdx/mise-action's releases.

v5.2.4: Reuse cached signed checksums when restoring mise

Jobs that restore mise from the cache no longer have to download its signed checksums from GitHub on every run, so a network failure at that step no longer fails a job that otherwise restored correctly.

Fixed

• Restoring a cached mise no longer needs a network download of the checksums. The action checks the cached mise binary against the signed SHASUMS256.txt and its .minisig. Before this release it downloaded both files from GitHub on every run, even when the cache restored correctly. When that download failed, for example after repeated curl errors, the job failed. Now, once the signature checks out, the action saves both files as SHASUMS256-<version>.txt and .minisig in <mise_dir>/bin, which is part of the mise cache. On later runs it reads them from the restored cache and checks the minisign signature again before using them. If the files are missing, corrupt or tampered with, the action downloads them as it did before. There are no new inputs. (#708 by @​jdx)
  • Caches saved by earlier versions don't contain these files. The main cache is only saved on a cache miss, so runs keep downloading the checksums until the cache is saved again or its key changes.

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

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

Changelog

Sourced from jdx/mise-action's changelog.

Changelog

---

5.2.6 - 2026-11-02

🐛 Bug Fixes

• exit after run and post so a failed cache restore can't hang the step (#718) by @​jdx in #718

---

5.2.5 - 2026-10-31

🔍 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

... (truncated)

Commits

• 6be3c7e chore: release v5.2.4 (#709)
• 40dafec fix(cache): reuse signed checksums saved with a cached mise (#708)
• ed63289 chore(deps): lock file maintenance (#707)
• 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)
• See full diff in compare view

Updates cloudsmith-io/cloudsmith-cli-action from 3.1.1 to 3.2.1

Changelog

Sourced from cloudsmith-io/cloudsmith-cli-action's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

---

[3.2.1] - 2026-10-28

---

Changed

• Pin the default cli-version to Cloudsmith CLI 1.30.1.

[3.2.0] - 2026-10-27

---

Changed

• cli-version now defaults to a pinned Cloudsmith CLI version (1.30.0) instead of latest. A workflow that pins this action to a commit SHA now installs the same CLI version on every run. Set cli-version: latest to keep the previous floating behavior.
• Each Cloudsmith CLI release now opens a pull request that pins the new CLI version. When the pull request merges, the action publishes a patch release, or a minor release if unreleased changes are pending, and moves the v3 tag.

[3.1.1] - 2026-09-10

---

Fixed

• export-auth-token with OIDC: a second invocation of the action no longer reuses the token that an earlier invocation exported. The credential helper inherited CLOUDSMITH_API_KEY from the environment and returned it unchanged, so setup for a second organization kept the first organization's credential. The wrapper scripts now clear the inherited CLOUDSMITH_API_KEY before they call the helper. An explicit api-key input is still honored.

[3.1.0] - 2026-08-03

---

Added

• export-auth-token now resolves the effective credential through cloudsmith credential-helper generic, validates its version-1 JSON response, exports password as CLOUDSMITH_API_KEY, exports the helper's username as CLOUDSMITH_USERNAME, and preserves the masked oidc-token compatibility output. oidc-auth-only remains a deprecated alias that enables the same flow.

[3.0.0] - 2026-07-30

---

Breaking Changes

• Composite action - The action is now a composite action that installs the standalone Cloudsmith CLI binary via bundled installer scripts. No Python or Node.js runtime is required.
• CLI-native OIDC - The CLI performs the OIDC token exchange on its first authenticated command; the action only exports CLOUDSMITH_ORG, CLOUDSMITH_SERVICE_SLUG, and CLOUDSMITH_OIDC_AUDIENCE. The default audience remains https://github.com/{repository-owner}.
• Removed inputs - pip-install, oidc-auth-only, oidc-auth-retry, oidc-token-validate, and executable-path. See the README migration table.
• Removed output - oidc-token. The action never holds a Cloudsmith token.
• No config file - api-host, api-proxy, api-ssl-verify, and api-user-agent are exported as CLOUDSMITH_* environment variables instead of being written to a config file.

Added

• install-directory input to control where versioned CLI installations live.
• verify-auth input to run cloudsmith whoami after setup.
• cli-version, target, cli-path, and bin-directory outputs.

... (truncated)

Commits

• 92b1383 Bump cloudsmith-cli to v1.30.1 (#51)
• ebed5fc ci: merge the CLI bump pull request when the checks pass (#50)
• 595d225 feat(ENG-14534): pin the CLI version and release on each CLI bump (#49)
• See full diff 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

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

[Copilot]

🟢 Approval recommended

No active review issues were identified for the SHA-pinned GitHub Actions updates.

No open issues 🎉

What changed in this PR

Updates three SHA-pinned GitHub Actions used by the repository’s linting, testing, release, and workflow-security checks.

Changes:

• Bumps jdx/mise-action from 5.2.2 to 5.2.4, incorporating cache improvements.
• Bumps cloudsmith-io/cloudsmith-cli-action from 3.1.1 to 3.2.1, which defaults to Cloudsmith CLI 1.30.1.
• Bumps zizmorcore/zizmor-action from 0.7.1 to 0.8.0, adding optional prerelease support without changing the default.

File	Description
.github/​workflows/​zizmor.yml	Updates the zizmor security-scanning action.
.github/​workflows/​test.yml	Updates Cloudsmith CLI and mise setup actions.
.github/​workflows/​release.yml	Updates the Cloudsmith CLI action used for publishing.
.github/​workflows/​lint.yml	Updates mise in both tool-setup steps.

_{Review effort: Balanced}