Repository navigation
feat(mise): refresh cooled release pin - #16
Merged
Merged
Conversation
gaborbernat
force-pushed
the
fix/refresh-mise-pin
branch
from
October 24, 2026 11:14
34d9bcf to
bfef38f
Compare
gaborbernat
marked this pull request as ready for review
October 24, 2026 11:18
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.
JetBrains-fish and PyVenvManage pin both a mise version and its executable digest in their release workflows. Their weekly updates need to refresh both values after the release and its Linux executable have aged seven days.
This keyless Action selects the newest eligible stable GitHub Release. The pinned mise Action verifies mise's signed checksum file; the refresh Action also compares the installed executable with GitHub's release asset digest. It edits only the named workflow step's version and digest through a hash-locked YAML parser. The caller then uses the verified mise on
PATHto refreshmise.lockwith--minimum-release-age 7d, before its separate App writer opens one PR for both files.