Repository navigation
chore(deps): update jdx/mise-action action to v5.2.10 - #78
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/jdx-mise-action-5.x
branch
from
October 17, 2026 13:13
a331af6 to
be3e7ff
Compare
renovate
Bot
force-pushed
the
renovate/jdx-mise-action-5.x
branch
from
October 20, 2026 16:00
be3e7ff to
61c7956
Compare
renovate
Bot
force-pushed
the
renovate/jdx-mise-action-5.x
branch
from
October 22, 2026 19:57
61c7956 to
64280e5
Compare
renovate
Bot
force-pushed
the
renovate/jdx-mise-action-5.x
branch
from
October 25, 2026 13:13
64280e5 to
b7b4c11
Compare
renovate
Bot
force-pushed
the
renovate/jdx-mise-action-5.x
branch
from
October 30, 2026 20:17
b7b4c11 to
e52f1e2
Compare
renovate
Bot
force-pushed
the
renovate/jdx-mise-action-5.x
branch
from
November 1, 2026 13:03
e52f1e2 to
a00e1fa
Compare
renovate
Bot
force-pushed
the
renovate/jdx-mise-action-5.x
branch
from
November 3, 2026 23:30
a00e1fa to
236544f
Compare
renovate
Bot
force-pushed
the
renovate/jdx-mise-action-5.x
branch
from
November 7, 2026 21:44
236544f to
66591a1
Compare
renovate
Bot
force-pushed
the
renovate/jdx-mise-action-5.x
branch
from
November 13, 2026 20:30
66591a1 to
56b8763
Compare
renovate
Bot
force-pushed
the
renovate/jdx-mise-action-5.x
branch
from
November 17, 2026 02:27
56b8763 to
7f84d27
Compare
renovate
Bot
force-pushed
the
renovate/jdx-mise-action-5.x
branch
from
November 19, 2026 19:52
7f84d27 to
daaa1b6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v5.1.1→v5.2.10Release Notes
jdx/mise-action
v5.2.10: : Fix mise download on Windows when MSYS curl is first on PATHCompare Source
On Windows, the action can now download mise when an MSYS
curl.exe(for example the Rtools one added byr-lib/actions/setup-r) comes first onPATH. Before this fix, the download failed every time while fetching the packslip bundle.Fixed
mise downloads no longer fail on Windows with MSYS curl.
r-lib/actions/setup-rputs the Rtoolscurl.exefirst onPATH. When mise-action ran after it, the mise zip downloaded, but every attempt to fetchpackslip.sigstore.jsonfailed withError: Could not download …/packslip.sigstore.json:. The job stopped after five retries.The cause was a literal newline in curl's
--write-outargument. MSYS curl splits that newline, so the action couldn't read the HTTP status from the response. curl now always writes the response body to a file, and--write-outcontains no newline. wget downloads are unchanged. If you ran mise-action beforesetup-rto work around this, you can now run them in either order. (#744 by @jdx, fixes #743 reported by @eitsupi)Full Changelog: jdx/mise-action@v5.2.9...v5.2.10
v5.2.9: : Maintenance releaseCompare Source
This release has no user-facing changes. It updates dependencies and the project's CI.
Full Changelog: jdx/mise-action@v5.2.8...v5.2.9
v5.2.8: : Fix mise install on Windows when MISE_DATA_DIR is on another driveCompare Source
On Windows, the action can now install mise when
MISE_DATA_DIRis on a different drive from the temporary directory. Before this fix, the install failed withEXDEV: cross-device link not permitted.Fixed
Installing mise on Windows no longer fails when
MISE_DATA_DIRis on another drive. On hostedwindows-2025runners, the workspace andRUNNER_TEMPare onD:, but the action downloaded mise toos.tmpdir()onC:. IfMISE_DATA_DIRpointed into the workspace, movingmise.exeinto place failed:The action now downloads to
RUNNER_TEMPwhen that variable is set and the directory exists. Otherwise it falls back to the system temp directory. If movingmise.exe,mise-shim.exeor a raw mise binary still crosses drives, the action copies the file and then deletes the original. This also covers self-hosted runners whereRUNNER_TEMPis on a different drive from the data directory. Setups that use the default data directory were not affected. If you setTEMPandTMPto${{ runner.temp }}to work around this, you can remove those settings. (#732 by @jdx and @HengYangDS, fixes #730)New Contributors
Full Changelog: jdx/mise-action@v5.2.7...v5.2.8
v5.2.7: : Retry failed mise downloads with backoff and show the HTTP statusCompare Source
When the action can't download mise, the log now shows the HTTP status and host for each failed attempt. Retries wait longer between attempts, so a short GitHub outage is less likely to fail the job.
Fixed
Download failures now show what went wrong, and brief outages are retried for longer. Before this release, a failed mise download logged only
The process '/usr/bin/curl' failed with exit code 22and retried five times with a fixed 2-second wait. From that message you couldn't tell a rate limit from a missing asset or a server error. Each failed attempt now logs the HTTP status and the host that answered:The wait between attempts doubles from about 2s up to a 30s cap, with random jitter, so the five retries cover roughly a minute. Only transient failures are retried: connection errors and timeouts, and HTTP 408, 429 and 5xx responses. A 404, any other 4xx, or a local file-write error fails at once. The log shows only the host and file name of each URL, never signed query strings or curl/wget stderr. Partial files are deleted before the next attempt. wget now runs with
--tries=1, so its own 20-retry default no longer stacks on top of the action's retries. This applies to every download the action makes: the release archive, checksums and the packslip bundle. Checksum and signature verification are unchanged, and there are no new inputs. (#722 by @jdx, fixes #721)Changed
Full Changelog: jdx/mise-action@v5.2.6...v5.2.7
v5.2.6: : Fix step hanging after a failed cache restoreCompare Source
The action now exits as soon as its work is done. Before this release, a cache restore that failed during the download could leave the step running for up to ten minutes after setup had finished.
Fixed
getaddrinfo EAI_AGAIN, the action logged a warning, installed the tools and saved the cache, then stopped producing output. The step stayed in progress until the job was cancelled or a timer inside@actions/cachefired after 10 minutes. That timer is left running when a download fails (actions/toolkit#2470), and it kept the Node process alive. The action now exits explicitly after both the main step and the post step finish. It waits up to 5 seconds for log output to flush, then exits. The exit code set by any earlier failure is kept. Errors that aren'tErrorobjects now mark the step as failed with their message. Before, they caused an unhandled rejection. (#718 by @jdx and @kjanat, fixes #717)Full Changelog: jdx/mise-action@v5.2.5...v5.2.6
v5.2.5: : Bundled packslip verifier updated to 1.11.0; README examples use v5Compare Source
This release updates the packslip library that the action uses to verify downloaded mise releases, and updates the README examples to use the current major versions.
Changed
packslip.sigstore.jsonthat ships with mise releases from 2026.9.3 onward. The new version runs extra checks on the signed statement: the identity it declares must match the certificate that signed it, and the certificate must belong to thegithub.com/jdx/miserepository. GitHub and GitLab repository names now match regardless of letter case. The action still asks for the same identity, issuer and tag as before, and there are no new inputs. (#715)jdx/mise-action@v5andactions/checkout@v7. (#710 by @deining)Full Changelog: jdx/mise-action@v5.2.4...v5.2.5
v5.2.4: : Reuse cached signed checksums when restoring miseCompare Source
Jobs that restore mise from the cache no longer have to download its signed checksums from GitHub on every run, so a network failure at that step no longer fails a job that otherwise restored correctly.
Fixed
SHASUMS256.txtand its.minisig. Before this release it downloaded both files from GitHub on every run, even when the cache restored correctly. When that download failed, for example after repeated curl errors, the job failed. Now, once the signature checks out, the action saves both files asSHASUMS256-<version>.txtand.minisigin<mise_dir>/bin, which is part of the mise cache. On later runs it reads them from the restored cache and checks the minisign signature again before using them. If the files are missing, corrupt or tampered with, the action downloads them as it did before. There are no new inputs. (#708 by @jdx)Full Changelog: jdx/mise-action@v5.2.3...v5.2.4
v5.2.3: : Faster cache key computation in large workspacesCompare Source
The cache key no longer comes from searching the whole workspace for mise config files. In repos that already contain
node_modulesorvendor/bundle, this removes a delay of several minutes in "Restoring mise cache".Fixed
**/…glob patterns. That meant it walked every subdirectory of the workspace, includingnode_modulesandvendor/bundle, before checking the cache at all. When the action ran after a step likepnpm installorruby/setup-rubywithbundler-cache: true, this could take 3–7 minutes. The action now looks for mise config files the same way mise does: only in the working directory and each parent directory up to the workspace root. It checks formise.toml,.mise.toml,.config/mise/…,conf.dfragments,.tool-versions, and their local, env-specific and.lockvariants. The step also logsHashed mise config files in N.Ns. (#703 by @jdx and @corsicanec82)cache_keythat doesn't use{{file_hash}}or{{default}}, the action no longer hashes config files at all.--monorepo.New Contributors
Full Changelog: jdx/mise-action@v5.2.2...v5.2.3
v5.2.2: : Include conf.d config fragments in the cache keyCompare Source
The cache key now includes mise
conf.d/*.tomlconfig fragments, so changing one of them invalidates the cache.Fixed
conf.dfragment now invalidates the cache. mise can load config from single-file fragments inconf.d/directories, but the action didn't hash those files when it built the cache key. As a result, adding or changing tools in a fragment could restore an outdated cache. The cache key now also hashesconf.d/*.tomlfiles under.config/mise/,.mise/andmise/. If your repo already uses these fragments, the cache will miss once after you upgrade. (#698 by @rileymichael)New Contributors
Full Changelog: jdx/mise-action@v5.2.1...v5.2.2
v5.2.1: : Require the signed packslip for mise 2026.9.3 and laterCompare Source
The action now refuses to install mise 2026.9.3 or later if the release's signed packslip is missing. This closes a gap where verification could be downgraded to the weaker checksum check.
Fixed
packslip.sigstore.json. If that file wasn't found, though, the action quietly fell back to the minisign-signedSHASUMS256checksums. Anyone who could hide the file could force the weaker check. Every mise release from 2026.9.3 on includes a packslip, so for those versions a missing bundle now stops the install with an error like this:sha256input, it still takes precedence over both checks. A packslip that fails verification still never falls back to the checksums. (#695 by @jdx)Full Changelog: jdx/mise-action@v5.2.0...v5.2.1
v5.2.0: : Periodic cache rebuilds, signed packslip verification, and monorepo installsCompare Source
The default cache key now rolls over every 30 days, so long-lived caches pick up newer mise releases. The action also checks the downloaded mise binary against the release's signed packslip, and it runs
mise install --monorepoautomatically in monorepos. Existing caches miss once after you upgrade, because the default cache key format has changed.Added
-p<N>), so the cache is rebuilt from scratch at least once per period. All repos roll over on the same calendar boundary. Use the newcache_max_age_daysinput to change the period, or set it to0to keep the old key that never expires. Customcache_keytemplates can use the new{{cache_period}}variable, which{{default}}already includes. A custom key that doesn't use it behaves as before. On self-hosted runners that keep mise data between runs, you may also needauto_update: trueto pick up a newer mise. (#689 by @jdx, fixes #688)cache_restore_retry_budgetandcache_save_retry_budgetinputs set how long the action may wait. Each retry waits for theRetry-Aftervalue plus some random jitter. Once the budget runs out, the action falls back to the old behavior. Retries apply to the main cache, the post-step save and the binary cache. Real cache misses and reservation conflicts are never retried. Both budgets default to0s(no retries).@actions/cachedoesn't report 429 errors directly, so the action detects throttling from its warning messages. If those messages change in a future@actions/cacherelease, throttling won't be detected and nothing will be retried. (#692 by @jdx, fixes #691)fetch_from_githubsetting decides which source it tries first. Pinned versions andminimum_release_ageinstalls are only downloaded from GitHub. The binary is still checked against the signed checksums for the resolved version, whichever source it came from. (#692 by @jdx)packslip.sigstore.json, the action checks the downloaded binary against it. The bundle must be signed by mise's release workflow for that exact tag. After a successful check, the log showsVerified <asset> against the signed packslip. If the check fails, the install stops instead of falling back to a weaker check. Releases without a packslip use the existing minisign andSHASUMS256check. An explicitsha256input still takes precedence. (#693 by @jdx)[monorepo].config_roots, the action now adds--monorepotomise install, so tools configured anywhere in the monorepo get installed. Repos without that setting aren't affected. To opt out, setmonorepo: false. (#679 by @zeitlinger)Fixed
PATHare now exported. The action used to find mise'sPATHchanges by comparing mise'sPATHwith the runner's. If a tool's bin directory was already on the runner'sPATH, such as~/.cargo/bin, mise only moved it to the front, so the action didn't export it. Later steps then found the mise shim first. For example,rustupresolved to the shim instead of~/.cargo/bin/rustup. The action now asks mise for its entries withmise env --pathsand exports them in the order mise reports. This fix needs a mise version that supports--paths. With older versions, the action uses the old comparison. (#685 by @jdx)Documentation
cache: falseor GitHub'scache-mode: none. (#682 by @jdx)mise.lock, instead of installed tools. It includes a Windows example that setsMISE_CACHE_DIRfrom${{ runner.temp }}, becauseactions/cachedoesn't expand%TEMP%. (#686, #690 by @zeitlinger)Breaking Changes
cache_max_age_days: 0. Workflows that set a customcache_keywithout{{default}}or{{cache_period}}aren't affected.Full Changelog: jdx/mise-action@v5.1.2...v5.2.0
v5.1.2: : mise_dir now sets MISE_DATA_DIR; auto_update handles a locked mise binaryCompare Source
The
mise_dirinput now also sets where mise installs tools, so those tools end up in the cache. Withauto_update: true, the action no longer crashes on Windows when the mise binary is still in use.Fixed
mise_dirnow exportsMISE_DATA_DIR. Before this release,mise_dirmoved the mise binary and the cache path, but mise kept installing tools to~/.local/share/mise. The saved cache didn't include the tools. On runners where~/.localisn't writable, the step failed withEACCES: permission denied. Whenmise_diris set, the action now exportsMISE_DATA_DIR=<mise_dir>, so tools are installed into the directory that gets cached. If your workflow sets a differentMISE_DATA_DIR, themise_dirinput overrides it. Ifmise_dirisn't set, nothing changes. mise's state directory (~/.local/state/mise) stays where it is. If that path also can't be written, setMISE_STATE_DIRyourself. (#672 by @jdx, fixes #668)auto_updateno longer crashes when it can't replacemise.exe. On Windows, the step used to fail with a bareEPERM: operation not permitted, unlink '…\mise.exe'if another process was still using the binary. Now, ifversionisn't pinned and the existing binary passes verification against its recorded version, the action prints a warning and continues with that version. In any other case, the step fails with a message that says the file is in use and how to fix it. A pinnedversionnever quietly keeps an older binary. (#665 by @jdx, fixes #664)Documentation
MISE_ENABLE_TOOLSsetting as a job-level allowlist. Unlikeinstall_args, the allowlist applies to the action's install and to latermisecommands. If jobs use different allowlists, add the value to a customcache_key. (#667 by @zeitlinger)mise installrepairs a restored toolchain instead of leavingrustfmtmissing. Swatinem/rust-cache now works alongside mise-managed Rust. (#670 by @jdx)Full Changelog: jdx/mise-action@v5.1.1...v5.1.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 was generated by Mend Renovate. View the repository job log.