A patch release that restores mise's PATH propagation to subsequent workflow steps — without reintroducing the full-PATH snapshot behavior that v4.2.1 fixed.
Fixed
Export mise PATH entries to subsequent steps (#575) by @jdx
v4.2.1 stopped exporting the complete PATH returned by mise env --json into GITHUB_ENV, which correctly prevented snapshotting the runner's environment into subsequent steps. However, that also dropped mise-produced PATH entries — tool shims, [env] _.path directories, and similar — that workflows relied on after the setup step. See #565.
The action now computes only the prefix that mise prepended to the existing PATH and forwards those directories individually through GITHUB_PATH. This preserves mise's configured ordering, composes cleanly with PATH changes from other actions, and never persists the runner's full PATH through GITHUB_ENV. The dotenv fallback path (used with older mise versions) also strips PATH= lines and re-derives additions from mise env --json.
A new export_path input (default true) lets workflows keep regular env exports while opting out of PATH changes:
- uses:jdx/mise-action@v4with:export_path:false# keep env vars, skip mise PATH additions
The action previously chose the .tar.zst mise archive whenever zstd --version succeeded, then extracted it with tar --zstd. On RHEL 8-compatible runners that ship zstd 1.4.4 alongside GNU tar 1.30, the --zstd option isn't recognized and installation failed.
Detection now runs both checks:
zstd --version
tar --zstd --version
If either fails, the action falls back to the .tar.gz archive. No configuration change is required — existing workflows on affected runners just start working again. Fixes #568.
Documentation
Update the cache_key_prefix example in the README to reflect the current default of mise-v1 (previously documented as mise-v0) (#570 by @muzimuzhi).
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [https://github.com/jdx/mise-action](https://github.com/jdx/mise-action) | action | patch | `v4.2.1` → `v4.2.3` |
---
### Release Notes
<details>
<summary>jdx/mise-action (https://github.com/jdx/mise-action)</summary>
### [`v4.2.3`](https://github.com/jdx/mise-action/releases/tag/v4.2.3): : Restore mise PATH propagation
[Compare Source](https://github.com/jdx/mise-action/compare/v4.2.2...v4.2.3)
A patch release that restores mise's PATH propagation to subsequent workflow steps — without reintroducing the full-PATH snapshot behavior that v4.2.1 fixed.
#### Fixed
##### Export mise PATH entries to subsequent steps ([#​575](https://github.com/jdx/mise-action/pull/575)) by [@​jdx](https://github.com/jdx)
v4.2.1 stopped exporting the complete `PATH` returned by `mise env --json` into `GITHUB_ENV`, which correctly prevented snapshotting the runner's environment into subsequent steps. However, that also dropped mise-produced PATH entries — tool shims, `[env] _.path` directories, and similar — that workflows relied on after the setup step. See [#​565](https://github.com/jdx/mise-action/issues/565).
The action now computes only the **prefix** that mise prepended to the existing `PATH` and forwards those directories individually through `GITHUB_PATH`. This preserves mise's configured ordering, composes cleanly with PATH changes from other actions, and never persists the runner's full `PATH` through `GITHUB_ENV`. The dotenv fallback path (used with older mise versions) also strips `PATH=` lines and re-derives additions from `mise env --json`.
A new `export_path` input (default `true`) lets workflows keep regular `env` exports while opting out of PATH changes:
```yaml
- uses: jdx/mise-action@v4
with:
export_path: false # keep env vars, skip mise PATH additions
```
**Full Changelog**: <https://github.com/jdx/mise-action/compare/v4.2.2...v4.2.3>
### [`v4.2.2`](https://github.com/jdx/mise-action/releases/tag/v4.2.2): : Zstd tar fallback for older runners
[Compare Source](https://github.com/jdx/mise-action/compare/v4.2.1...v4.2.2)
A small patch release that fixes archive selection on runners with an older `tar` and corrects a stale default in the README.
#### Fixed
##### Verify `tar` supports Zstd before picking `.tar.zst` ([#​569](https://github.com/jdx/mise-action/pull/569) by [@​JackMyers001](https://github.com/JackMyers001)
The action previously chose the `.tar.zst` mise archive whenever `zstd --version` succeeded, then extracted it with `tar --zstd`. On RHEL 8-compatible runners that ship `zstd` 1.4.4 alongside GNU `tar` 1.30, the `--zstd` option isn't recognized and installation failed.
Detection now runs both checks:
```
zstd --version
tar --zstd --version
```
If either fails, the action falls back to the `.tar.gz` archive. No configuration change is required — existing workflows on affected runners just start working again. Fixes [#​568](https://github.com/jdx/mise-action/issues/568).
#### Documentation
- Update the `cache_key_prefix` example in the README to reflect the current default of `mise-v1` (previously documented as `mise-v0`) ([#​570](https://github.com/jdx/mise-action/pull/570) by [@​muzimuzhi](https://github.com/muzimuzhi)).
#### New Contributors
- [@​JackMyers001](https://github.com/JackMyers001) made their first contribution in [#​569](https://github.com/jdx/mise-action/pull/569)
- [@​muzimuzhi](https://github.com/muzimuzhi) made their first contribution in [#​570](https://github.com/jdx/mise-action/pull/570)
**Full Changelog**: <https://github.com/jdx/mise-action/compare/v4.2.1...v4.2.2>
</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:eyJjcmVhdGVkSW5WZXIiOiI0My4yODEuMSIsInVwZGF0ZWRJblZlciI6IjQzLjI4MS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR contains the following updates:
v4.2.1→v4.2.3Release Notes
jdx/mise-action (https://github.com/jdx/mise-action)
v4.2.3: : Restore mise PATH propagationCompare Source
A patch release that restores mise's PATH propagation to subsequent workflow steps — without reintroducing the full-PATH snapshot behavior that v4.2.1 fixed.
Fixed
Export mise PATH entries to subsequent steps (#575) by @jdx
v4.2.1 stopped exporting the complete
PATHreturned bymise env --jsonintoGITHUB_ENV, which correctly prevented snapshotting the runner's environment into subsequent steps. However, that also dropped mise-produced PATH entries — tool shims,[env] _.pathdirectories, and similar — that workflows relied on after the setup step. See #565.The action now computes only the prefix that mise prepended to the existing
PATHand forwards those directories individually throughGITHUB_PATH. This preserves mise's configured ordering, composes cleanly with PATH changes from other actions, and never persists the runner's fullPATHthroughGITHUB_ENV. The dotenv fallback path (used with older mise versions) also stripsPATH=lines and re-derives additions frommise env --json.A new
export_pathinput (defaulttrue) lets workflows keep regularenvexports while opting out of PATH changes:Full Changelog: https://github.com/jdx/mise-action/compare/v4.2.2...v4.2.3
v4.2.2: : Zstd tar fallback for older runnersCompare Source
A small patch release that fixes archive selection on runners with an older
tarand corrects a stale default in the README.Fixed
Verify
tarsupports Zstd before picking.tar.zst(#569 by @JackMyers001The action previously chose the
.tar.zstmise archive wheneverzstd --versionsucceeded, then extracted it withtar --zstd. On RHEL 8-compatible runners that shipzstd1.4.4 alongside GNUtar1.30, the--zstdoption isn't recognized and installation failed.Detection now runs both checks:
If either fails, the action falls back to the
.tar.gzarchive. No configuration change is required — existing workflows on affected runners just start working again. Fixes #568.Documentation
cache_key_prefixexample in the README to reflect the current default ofmise-v1(previously documented asmise-v0) (#570 by @muzimuzhi).New Contributors
Full Changelog: https://github.com/jdx/mise-action/compare/v4.2.1...v4.2.2
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR has been generated by Mend Renovate.
LGTM