mxmehl/mehl.mx
1
0
Fork 0
Code Issues 3 Pull Requests 1 Actions Releases Wiki Activity

chore(deps): update https://github.com/jdx/mise-action action to v4.1.0 #20

Merged
mxmehl merged 1 commits from renovate/https-github.com-jdx-mise-action-4.x into main 2026-06-08 12:03:29 +02:00
Conversation 0 Commits 1 Files Changed 1
+1 -1
renovate-bot commented 2026-06-08 03:16:57 +02:00
Collaborator
Copy Link
Copy Source

This PR contains the following updates:

Package Type Update Change
https://github.com/jdx/mise-action action minor v4.0.1 → v4.1.0

Release Notes

jdx/mise-action (https://github.com/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: https://github.com/jdx/mise-action/compare/v4.0.1...v4.1.0

Configuration

📅 Schedule: (UTC)

  • 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 has been generated by Mend Renovate.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [https://github.com/jdx/mise-action](https://github.com/jdx/mise-action) | action | minor | `v4.0.1` → `v4.1.0` | --- ### Release Notes <details> <summary>jdx/mise-action (https://github.com/jdx/mise-action)</summary> ### [`v4.1.0`](https://github.com/jdx/mise-action/releases/tag/v4.1.0): : automatic --locked installs [Compare Source](https://github.com/jdx/mise-action/compare/v4.0.1...v4.1.0) 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 ([#&#8203;495](https://github.com/jdx/mise-action/pull/495)) by [@&#8203;zeitlinger](https://github.com/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** ([#&#8203;456](https://github.com/jdx/mise-action/pull/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** ([#&#8203;476](https://github.com/jdx/mise-action/pull/476)) by [@&#8203;risu729](https://github.com/risu729) — the action now installs `mise-shim.exe` alongside `mise.exe` and repairs restored caches that lack the shim. Fixes [#&#8203;475](https://github.com/jdx/mise-action/issues/475). #### Changed - Migrated the bundled action build from ncc (CommonJS) to Rollup (ESM) ([#&#8203;436](https://github.com/jdx/mise-action/pull/436)). No user-facing behavior change. **Full Changelog**: <https://github.com/jdx/mise-action/compare/v4.0.1...v4.1.0> </details> --- ### Configuration 📅 **Schedule**: (UTC) - 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMTQuMiIsInVwZGF0ZWRJblZlciI6IjQzLjIxNC4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
renovate-bot added 1 commit 2026-06-08 03:16:58 +02:00
chore(deps): update https://github.com/jdx/mise-action action to v4.1.0
renovate/stability-days Updates have met minimum release age requirement
Details
Website build and deploy / build (pull_request) Successful in 1m33s
Details
97aeea97ff
mxmehl merged commit 9d6d8eaf90 into main 2026-06-08 12:03:29 +02:00
mxmehl deleted branch renovate/https-github.com-jdx-mise-action-4.x 2026-06-08 12:03:29 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
renovate-bot mxmehl
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mxmehl/mehl.mx#20
Delete Branch "renovate/https-github.com-jdx-mise-action-4.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?