Skip to content

chore(deps): update jdx/mise-action action to v4.2.3 - #200

Merged
renovate[bot] merged 1 commit into
masterfrom
renovate/jdx-mise-action-4.x
Jul 28, 2026
Merged

chore(deps): update jdx/mise-action action to v4.2.3#200
renovate[bot] merged 1 commit into
masterfrom
renovate/jdx-mise-action-4.x

Conversation

@renovate

@renovate renovate Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
jdx/mise-action action patch v4.2.1v4.2.3

Release Notes

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

v4.2.3: : Restore mise PATH propagation

Compare 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 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@v4
  with:
    export_path: false # keep env vars, skip mise PATH additions

Full Changelog: jdx/mise-action@v4.2.2...v4.2.3

v4.2.2: : Zstd tar fallback for older runners

Compare Source

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 by @​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.

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).
New Contributors

Full Changelog: jdx/mise-action@v4.2.1...v4.2.2


Configuration

📅 Schedule: (in timezone Europe/Oslo)

  • Branch creation
    • "before 6am,every weekend"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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.

@renovate

renovate Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor Author

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

@renovate
renovate Bot merged commit fe147f0 into master Jul 28, 2026
4 checks passed
@renovate
renovate Bot deleted the renovate/jdx-mise-action-4.x branch July 28, 2026 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants