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.2.1 #24

Merged
mxmehl merged 1 commits from renovate/https-github.com-jdx-mise-action-4.x into main 2026-07-21 10:11:55 +02:00
Conversation 0 Commits 1 Files Changed 1
+1 -1
renovate-bot commented 2026-07-20 03:17:03 +02:00
Collaborator
Copy Link
Copy Source

This PR contains the following updates:

Package Type Update Change
https://github.com/jdx/mise-action action patch v4.2.0 → v4.2.1

Release Notes

jdx/mise-action (https://github.com/jdx/mise-action)

v4.2.1: : Signed checksums and PATH export fix

Compare Source

A small patch release with two user-facing fixes: mise downloads are now verified against minisign-signed release checksums by default, and the env input no longer leaks the runner's PATH into subsequent steps.

Fixed

Verify mise downloads with signed checksums (#​548) by @​jdx

The action now embeds mise's minisign public key and verifies SHASUMS256.txt.minisig before trusting any release checksums, then checks the downloaded mise binary's SHA256 against the verified list. This applies to both GitHub release archives (verified before extraction) and the default mise.jdx.dev CDN path (verified against the signed checksum for the matching release asset). If a CDN download fails verification, the action warns and falls back to the signed GitHub release asset instead of installing an unverified binary.

  • The existing sha256 input still works as an explicit override.
  • Pinned mise versions older than 2024.12.24 (which predate minisign checksums) get a warning and skip signed verification rather than failing.
  • Because tar installs now extract from a verified file on disk, the previous streaming download | tar fast path is replaced with a download-then-verify-then-extract flow.

Thanks to @​potiuk for the detailed threat-model writeup in #​547.

Exclude PATH from environment export (#​556) by @​jdx

The env input has always documented that "PATH modifications are not part of this", but since the switch to mise env --json in #​252 (needed for redaction support), the action was exporting every string value returned by mise — including the computed PATH — into GITHUB_ENV. That effectively snapshotted the runner's entire PATH into subsequent steps and let [env] _.path entries in mise.toml leak past the action's own PATH management.

exportMiseEnv now skips PATH (case-insensitive) when exporting JSON env vars, restoring the documented behavior. Normal mise env vars are still exported, and PATH continues to be managed by the action's own setup (e.g. add_shims_to_path). Fixes #​555.

Full Changelog: https://github.com/jdx/mise-action/compare/v4.2.0...v4.2.1

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 | patch | `v4.2.0` → `v4.2.1` | --- ### Release Notes <details> <summary>jdx/mise-action (https://github.com/jdx/mise-action)</summary> ### [`v4.2.1`](https://github.com/jdx/mise-action/releases/tag/v4.2.1): : Signed checksums and PATH export fix [Compare Source](https://github.com/jdx/mise-action/compare/v4.2.0...v4.2.1) A small patch release with two user-facing fixes: mise downloads are now verified against minisign-signed release checksums by default, and the `env` input no longer leaks the runner's `PATH` into subsequent steps. #### Fixed ##### Verify mise downloads with signed checksums ([#&#8203;548](https://github.com/jdx/mise-action/pull/548)) by [@&#8203;jdx](https://github.com/jdx) The action now embeds mise's minisign public key and verifies `SHASUMS256.txt.minisig` before trusting any release checksums, then checks the downloaded mise binary's SHA256 against the verified list. This applies to both GitHub release archives (verified before extraction) and the default `mise.jdx.dev` CDN path (verified against the signed checksum for the matching release asset). If a CDN download fails verification, the action warns and falls back to the signed GitHub release asset instead of installing an unverified binary. - The existing `sha256` input still works as an explicit override. - Pinned mise versions older than `2024.12.24` (which predate minisign checksums) get a warning and skip signed verification rather than failing. - Because tar installs now extract from a verified file on disk, the previous streaming `download | tar` fast path is replaced with a download-then-verify-then-extract flow. Thanks to [@&#8203;potiuk](https://github.com/potiuk) for the detailed threat-model writeup in [#&#8203;547](https://github.com/jdx/mise-action/issues/547). ##### Exclude `PATH` from environment export ([#&#8203;556](https://github.com/jdx/mise-action/pull/556)) by [@&#8203;jdx](https://github.com/jdx) The `env` input has always documented that "PATH modifications are not part of this", but since the switch to `mise env --json` in [#&#8203;252](https://github.com/jdx/mise-action/pull/252) (needed for redaction support), the action was exporting every string value returned by mise — including the computed `PATH` — into `GITHUB_ENV`. That effectively snapshotted the runner's entire `PATH` into subsequent steps and let `[env] _.path` entries in `mise.toml` leak past the action's own PATH management. `exportMiseEnv` now skips `PATH` (case-insensitive) when exporting JSON env vars, restoring the documented behavior. Normal mise env vars are still exported, and PATH continues to be managed by the action's own setup (e.g. `add_shims_to_path`). Fixes [#&#8203;555](https://github.com/jdx/mise-action/issues/555). **Full Changelog**: <https://github.com/jdx/mise-action/compare/v4.2.0...v4.2.1> </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:eyJjcmVhdGVkSW5WZXIiOiI0My4yNzAuMSIsInVwZGF0ZWRJblZlciI6IjQzLjI3MC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
renovate-bot added 1 commit 2026-07-20 03:17:04 +02:00
chore(deps): update https://github.com/jdx/mise-action action to v4.2.1
renovate/stability-days Updates have met minimum release age requirement
Details
Website build and deploy / build (pull_request) Successful in 1m37s
Details
4374fccdde
mxmehl merged commit 74c86c31bf into main 2026-07-21 10:11:55 +02:00
mxmehl deleted branch renovate/https-github.com-jdx-mise-action-4.x 2026-07-21 10:11:55 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
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#24