chore(deps): update jdx/mise-action action to v5 - #71
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
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:
v4.3.0→v5.0.0Release Notes
jdx/mise-action (jdx/mise-action)
v5.0.0: : Default minimum release age of 24 hours for miseCompare Source
If you don't pin a
version, mise-action now installs the newest stable mise release that is at least 24 hours old. Upgrading mise on a runner that already has it is also less likely to hit GitHub API rate limits.Breaking Changes
minimum_release_agenow defaults to24h(#632 by @jdx)Before this release,
minimum_release_agewas an opt-in setting. It now defaults to24h. If you don't setversion, the action picks the highest-numbered stable mise release published at least 24 hours ago. A mise release that just shipped won't be installed until it's a day old.To get the latest stable release right away, as in v4, set the delay to
0s. You can also choose a longer delay:versioninput still takes precedence and skips the delay.releases.tsvon mise.jdx.dev) instead of paging through the GitHub Releases API. Picking a release doesn't use GitHub API quota, even when an installed binary is reused. If the index is missing or malformed, the action fails instead of skipping the release-age check.mise self-update, which may call the GitHub API to fetch that exact release.Fixed
mise self-updatenow runs withMISE_GITHUB_TOKEN. When a runner already had a different mise version installed, the action runsmise self-updateto switch versions. That GitHub API call used to go out without authentication, so busy shared or self-hosted runners could hit the rate limit and fail withHTTP 403 RateLimitedError. If you already set a token in your environment, the action leaves it unchanged. (#619 by @hegde5)New Contributors
Full Changelog: jdx/mise-action@v4.3.0...v5.0.0
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.