Update jdx/mise-action action to v4.1.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
jdx/mise-action	action	minor	v4.0.1 → v4.1.0

---

Release Notes

jdx/mise-action (jdx/mise-action)

v4.1.0: : automatic --locked installs

Compare Source

This release adds automatic locked installs when a mise.lock is present, and fixes a long-standing cache-key collision that could poison tool installs when workflows migrate between runner providers.

Added

Automatic --locked install when mise.lock exists (#​495) by @​zeitlinger

When a repo contains mise.lock, the action now automatically passes --locked to mise install (on mise versions that support it). This removes the need to manually set install_args: --locked and prevents mise install from silently mutating the lockfile in CI. Explicit install_args and older mise versions are still respected.

Note: workflows with a stale lockfile may now fail earlier and more explicitly instead of silently updating mise.lock mid-run — this surfaces lockfile drift rather than hiding it.

Fixed

• Cache key collisions across runner providers (#​456) — the default cache key now includes the runner image (e.g. macos15, ubuntu24 for GitHub-hosted runners; self-hosted otherwise). Previously, repos migrating between providers like github-hosted, namespace.so, BuildJet, and self-hosted runners with the same OS/arch could restore a peer provider's ~/.local/share/mise/installs/*, causing failures like does not have an executable named '…' or SIGILL crashes from binaries built against a different glibc/CPU featureset. Expect a one-time cache miss after upgrading; thereafter the cache stays scoped per image.
• mise-shim.exe missing on Windows (#​476) by @​risu729 — the action now installs mise-shim.exe alongside mise.exe and repairs restored caches that lack the shim. Fixes #​475.

Changed

• Migrated the bundled action build from ncc (CommonJS) to Rollup (ESM) (#​436). No user-facing behavior change.

Full Changelog: jdx/mise-action@v4.0.1...v4.1.0

---

Configuration

📅 Schedule: (in timezone America/Chicago)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 4172fab4-df28-4997-ae7a-8330dd925cea

📥 Commits

Reviewing files that changed from the base of the PR and between 64eb2a7 and 271f359.

📒 Files selected for processing (1)

• .github/actions/mise-setup/action.yml

📜 Recent review details

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Pre-Commit / Pre-Commit Run
• GitHub Check: CI / Build

🧰 Additional context used

📓 Path-based instructions (1)

.github/actions/mise-setup/*

📄 CodeRabbit inference engine (AGENTS.md)

Set MISE_LOCKED=1 in mise-setup so mise install fails on mise.toml ↔ mise.lock drift

Files:

• .github/actions/mise-setup/action.yml

🧠 Learnings (3)

📓 Common learnings

Learnt from: CR
Repo: gtbuchanan/tooling PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-06-04T20:00:49.800Z
Learning: Applies to .github/actions/mise-setup/* : Set `MISE_LOCKED=1` in mise-setup so `mise install` fails on `mise.toml` ↔ `mise.lock` drift

Learnt from: CR
Repo: gtbuchanan/tooling PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-06-04T20:00:49.800Z
Learning: Applies to .github/workflows/*.yml : Every job that needs Node, pnpm, or prek must prepend `mise-setup` to install exact versions pinned in `mise.toml` / `mise.lock`

📚 Learning: 2026-06-04T20:00:49.800Z

Learnt from: CR
Repo: gtbuchanan/tooling PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-06-04T20:00:49.800Z
Learning: Applies to .github/actions/mise-setup/* : Set `MISE_LOCKED=1` in mise-setup so `mise install` fails on `mise.toml` ↔ `mise.lock` drift

Applied to files:

• .github/actions/mise-setup/action.yml

📚 Learning: 2026-06-04T20:00:49.800Z

Learnt from: CR
Repo: gtbuchanan/tooling PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-06-04T20:00:49.800Z
Learning: Applies to .github/workflows/*.yml : Every job that needs Node, pnpm, or prek must prepend `mise-setup` to install exact versions pinned in `mise.toml` / `mise.lock`

Applied to files:

• .github/actions/mise-setup/action.yml

🔇 Additional comments (1)

.github/actions/mise-setup/action.yml (1)

35-35: LGTM!

---

📝 Walkthrough

Walkthrough

The mise-setup composite GitHub Action updates the jdx/mise-action dependency from version v4.0.1 to v4.1.0. No caching, configuration logic, or mise install behavior is modified.

Changes

mise-action version update

Layer / File(s)	Summary
mise-action version update .github/actions/mise-setup/action.yml	The jdx/mise-action step reference is bumped from v4.0.1 to v4.1.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise, descriptive, and directly describes the main change—updating jdx/mise-action to v4.1.0.
Description check	✅ Passed	The description is related to the changeset, providing detailed release notes and context about the jdx/mise-action version update.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}