Skip to content

chore(deps): update github-actions - #148

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github-actions
Open

chore(deps): update github-actions#148
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github-actions

Conversation

@renovate

@renovate renovate Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Type Update
actions/checkout v7.0.0 -> v7.0.1 action patch
actions/checkout 9c091bb -> 3d3c42e action digest
jdx/mise-action v4.2.0 -> v4.2.3 action patch

Release Notes

actions/checkout (actions/checkout)

v7.0.1

Compare Source

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

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: jdx/mise-action@v4.2.0...v4.2.1


Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
    • "after 4pm on thursday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 requested a review from scottames as a code owner July 24, 2026 02:55
@renovate
renovate Bot enabled auto-merge (squash) July 24, 2026 02:55
@renovate
renovate Bot force-pushed the renovate/github-actions branch 2 times, most recently from 0d55086 to 085ce17 Compare July 28, 2026 16:44
@renovate
renovate Bot force-pushed the renovate/github-actions branch from 085ce17 to e73f3fd Compare July 28, 2026 22:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants