Skip to content

Bump jdx/mise-action from 2.4.4 to 5.1.2 - #17

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/jdx/mise-action-5.1.1
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/jdx/mise-action-5.1.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

Bumps jdx/mise-action from 2.4.4 to 5.1.2.

Release notes

Sourced from jdx/mise-action's releases.

v5.1.2: mise_dir now sets MISE_DATA_DIR; auto_update handles a locked mise binary

The mise_dir input now also sets where mise installs tools, so those tools end up in the cache. With auto_update: true, the action no longer crashes on Windows when the mise binary is still in use.

Fixed

  • mise_dir now exports MISE_DATA_DIR. Before this release, mise_dir moved the mise binary and the cache path, but mise kept installing tools to ~/.local/share/mise. The saved cache didn't include the tools. On runners where ~/.local isn't writable, the step failed with EACCES: permission denied. When mise_dir is set, the action now exports MISE_DATA_DIR=<mise_dir>, so tools are installed into the directory that gets cached. If your workflow sets a different MISE_DATA_DIR, the mise_dir input overrides it. If mise_dir isn't set, nothing changes. mise's state directory (~/.local/state/mise) stays where it is. If that path also can't be written, set MISE_STATE_DIR yourself. (#672 by @​jdx, fixes #668)
    - uses: jdx/mise-action@v5
      with:
        mise_dir: ${{ runner.tool_cache }}/mise/data
  • auto_update no longer crashes when it can't replace mise.exe. On Windows, the step used to fail with a bare EPERM: operation not permitted, unlink '…\mise.exe' if another process was still using the binary. Now, if version isn't pinned and the existing binary passes verification against its recorded version, the action prints a warning and continues with that version. In any other case, the step fails with a message that says the file is in use and how to fix it. A pinned version never quietly keeps an older binary. (#665 by @​jdx, fixes #664)

Documentation

  • The README explains how to use mise's MISE_ENABLE_TOOLS setting as a job-level allowlist. Unlike install_args, the allowlist applies to the action's install and to later mise commands. If jobs use different allowlists, add the value to a custom cache_key. (#667 by @​zeitlinger)
  • The Rust cache section is updated for mise 2026.9.2 and later, where mise install repairs a restored toolchain instead of leaving rustfmt missing. Swatinem/rust-cache now works alongside mise-managed Rust. (#670 by @​jdx)

Full Changelog: jdx/mise-action@v5.1.1...v5.1.2

v5.1.1: GitHub token is no longer exported to later steps by default

mise-action no longer exports its GitHub token as MISE_GITHUB_TOKEN to every later step in the job. A new persist_github_token input lets you turn that back on, or pass a different token to later steps. This changes the default behavior. If later steps need the token, see Breaking Changes below.

Fixed

  • The GitHub token now stays inside the action by default. Before this release, the github_token input (which defaults to ${{ github.token }}) was written to GITHUB_ENV as MISE_GITHUB_TOKEN. That let any later step read the token and call the GitHub API with the job's permissions, even if the step never asked for a credential. Now the token is set only for the mise-action step and the processes it starts. The action masks the token in logs. (#658 by @​jdx, reported in #657)

Added

  • persist_github_token input (default false). It takes one of three values:

    • false: the token stays inside the action.
    • true: the token the action used is exported to later steps. If env.MISE_GITHUB_TOKEN is already set, it takes precedence over github_token.
    • A token value: that token is exported to later steps instead, for example a read-only token. The action still installs tools with github_token, or with MISE_GITHUB_TOKEN if it's already set.

    Setting false doesn't clear a MISE_GITHUB_TOKEN that was already set at the job level or exported by an earlier step. (#658 by @​jdx)

Breaking Changes

Check your workflow if a later step needs MISE_GITHUB_TOKEN, such as mise shims, mise exec, mise run or lazy tool installs that call the GitHub API. Those steps no longer get the token automatically and may hit GitHub API rate limits. To get the old behavior back, opt in:

- uses: jdx/mise-action@v5
  with:
    persist_github_token: true

Or give later steps a separate token:

- uses: jdx/mise-action@v5
</tr></table> 

... (truncated)

Changelog

Sourced from jdx/mise-action's changelog.

Changelog


5.1.2 - 2026-10-10

🐛 Bug Fixes

  • continue with the existing mise when auto-update cannot replace it (#665) by @​jdx in #665
  • export mise_dir as MISE_DATA_DIR so mise installs tools there (#672) by @​jdx in #672

📚 Documentation

⚙️ Miscellaneous Tasks


5.1.1 - 2026-10-04

🐛 Bug Fixes


5.1.0 - 2026-10-04

🚀 Features

🐛 Bug Fixes

  • (cache) keep a cached mise instead of re-downloading when version is unset (#642) by @​jdx in #642
  • save cache after inexact cache restore (#646) by @​jdx in #646
  • extract mise zip with PowerShell instead of unzip on Windows (#650) by @​jdx in #650
  • cache mise binary for caches saved without a version record (#648) by @​jdx in #648

📚 Documentation

  • explain the Rust cache caveat and workarounds (#651) by @​jdx in #651
  • add matrix and external cache guides; warn on shadowed mise_toml (#654) by @​jdx in #654

... (truncated)

Commits
  • 08ae2a0 chore: release v5.1.2 (#660)
  • 4c1c6f9 chore(ci): switch to jactionlint v2 and drop zizmor (#674)
  • 58185d8 chore(ci): lint workflows with jactionlint (#673)
  • 0e078e4 fix: export mise_dir as MISE_DATA_DIR so mise installs tools there (#672)
  • 64b792f docs: update the Rust cache section for mise 2026.9.2 (#670)
  • d7c6373 ci: fix the upload-artifact version comment (#671)
  • 3df3d8b docs: explain MISE_ENABLE_TOOLS in GitHub Actions (#667)
  • 1ea734b chore(deps): update jdx/renovate-config action to v1.0.2 (#666)
  • 6a90a24 fix: continue with the existing mise when auto-update cannot replace it (#665)
  • b3d6388 chore(deps): update github/codeql-action action to v4.38.2 (#662)
  • Additional commits viewable in compare view


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Oct 11, 2026
@vercel

vercel Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
fieldsofrevik-web Ready Ready Preview Oct 16, 2026 8:05am UTC

@dependabot dependabot Bot added the github_actions Pull requests that update GitHub Actions code label Oct 11, 2026
@dependabot dependabot Bot changed the title Bump jdx/mise-action from 2.4.4 to 5.1.1 Bump jdx/mise-action from 2.4.4 to 5.1.2 Oct 16, 2026
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/jdx/mise-action-5.1.1 branch from c534450 to d3ad7ca Compare October 16, 2026 04:44
Bumps [jdx/mise-action](https://github.com/jdx/mise-action) from 2.4.4 to 5.1.2.
- [Release notes](https://github.com/jdx/mise-action/releases)
- [Changelog](https://github.com/jdx/mise-action/blob/main/CHANGELOG.md)
- [Commits](jdx/mise-action@c37c932...08ae2a0)

---
updated-dependencies:
- dependency-name: jdx/mise-action
  dependency-version: 5.1.1
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/jdx/mise-action-5.1.1 branch from d3ad7ca to be9b25a Compare October 16, 2026 08:05

This branch was successfully deployed

1 active deployment
Preview — be9b25a9 Deployed Oct 16, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants