Repository navigation
chore(deps): update jdx/mise-action action to v5.2.7 - #157
Merged
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/github-actions
branch
from
October 27, 2026 11:05
c5f6930 to
39fe4be
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
2 times, most recently
from
November 3, 2026 01:11
b3b1ede to
14a1426
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
from
November 6, 2026 20:33
14a1426 to
d7e2b1a
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.2.2→v5.2.7Release Notes
jdx/mise-action
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
Configuration
📅 Schedule: (in timezone Etc/UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.