Repository navigation
chore(deps): update jdx/mise-action action to v5.3.0 - #525
Merged
Merged
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:
v5.2.10→v5.3.0Release Notes
jdx/mise-action
v5.3.0: : New mise_env input exports MISE_ENV to later stepsCompare Source
A new
mise_envinput sets the mise environment for the action and exportsMISE_ENVto every later step in the job.mise runandmise xin later steps now load the samemise.<env>.tomlconfigs that the action installed and cached.Added
mise_envinput. Before this change, settingMISE_ENVin the action step'senv:only applied inside the action. Later steps never saw it and quietly fell back to the base config. Job-levelenv:worked, but composite actions that pick the environment from their own inputs had to writeMISE_ENVtoGITHUB_ENVthemselves, and security linters such as zizmor flag that. The new input handles the export for you:In a composite action:
The input accepts one or more environments, such as
ciorci,linux. The action exports it before computing the cache key, so{{mise_env}}in a customcache_key,mise install, and later steps all use the same value. IfMISE_ENVis already set, the input takes priority, the same waymise_dirtakes priority overMISE_DATA_DIR. If you leave the input unset, nothing changes, and a step-levelMISE_ENVstill isn't exported. (#745 by @jdx with @veimox and @cprecioso, closes #447)Full Changelog: jdx/mise-action@v5.2.10...v5.3.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.