Update dependency jdx/mise to v2026.3.6#273
Merged
renovate[bot] merged 1 commit intomainfrom Mar 10, 2026
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:
v2026.3.5→v2026.3.6v2026.3.7Release Notes
jdx/mise (jdx/mise)
v2026.3.6: : Per-environment lockfiles, Windows fixes, and fork bomb preventionCompare Source
This release redesigns environment-specific lockfiles for better CI isolation, fixes a critical fork bomb caused by shim recursion in
go:backend tools, and addresses several Windows-specific issues including locked.exeshims andenv._.sourcesupport.Highlights
envtag system, somise.test.tomlnow generatesmise.test.lockinstead of tagging entries in a sharedmise.lock. This means CI caches are no longer invalidated by dev-only tool changes.go:backend tools are configured alongside an uninstalled Go version in shims mode..exeshim handling gracefully renames locked shim executables instead of failing with "Access is denied" during reshim.Changed
Lockfiles are now per-environment -- Environment-specific configs now get their own lockfiles (
mise.test.toml->mise.test.lock,mise.local.toml->mise.local.lock) instead of usingenv = ["test"]tags in a singlemise.lock. This improves CI cache isolation -- environments that don't setMISE_ENVonly depend onmise.lock, so dev tool version bumps won't invalidate CI caches. Old lockfiles withenvfields are silently accepted and migrated on the nextmise lock. #8523 by @jdxmise.tomlmise.lockmise.test.tomlmise.test.lockmise.local.tomlmise.local.locktouch_outputsremoved from prepare providers -- Thetouch_outputsconfiguration option has been removed from prepare providers. Freshness checking now uses blake3 content hashing exclusively, so touching output modification times is no longer necessary. #8535 by @jdxFixed
Fork bomb when using
go:backend tools in shims mode -- When ago:backend tool (e.g.,go:github.com/pulumi/upgrade-provider) was configured alongside a Go version that wasn't installed, and the version cache was cleared, mise could enter infinite shim recursion -- the Go shim would callmise exec, which would resolve thego:backend, which would callgo listvia the shim, and so on. The fix strips mise's shims directory from the PATH independency_env, ensuring dependency tools either resolve to a real installed binary or fail cleanly. This applies to all backends that use dependency environments (go,npm,gem,dotnet,spm,elixir). #8475 by @poseLocked
.exeshims on Windows during reshim --mise reshimwould fail with "Access is denied" on Windows when.exeshims were locked by running processes. The fix removes shims individually (instead of wiping the entire directory) and uses a rename-to-.oldfallback for locked files, which Windows allows even when the file is in use. The.oldfiles are cleaned up on the next reshim. #8517 by @davireisenv._.sourcenow works on Windows --env._.sourcewould fail on Windows because it searched forbashwithout the.exeextension. The Windows API executable search now correctly looks forbash.exe. #8520 by @pjebyGitHub
@latestversion resolution -- Thegithub:backend would fail with a 404 when using@latestbecause it constructed/releases/tags/latestinstead of using GitHub's/releases/latestAPI endpoint. This was a regression introduced in v2026.3.5. #8532 by @jdxFish shell shim PATH ordering on re-source -- When
config.fishis re-sourced (e.g., in VS Code integrated terminals),mise activate fish --shimsnow correctly moves shims to the front of PATH usingfish_add_path --global --move, instead of silently skipping them because they were already present. Other shells are unaffected. #8534 by @jdxTask output prefix disambiguation -- When running the same task multiple times with different arguments (e.g.,
mise run greet alice ::: greet bob), output prefixes now include the arguments to distinguish runs ([greet alice]vs[greet bob]). Arguments are only included when disambiguation is needed; single-instance tasks keep clean prefixes. Long prefixes are truncated to 40 characters. #8533, #8536 by @jdxNon-MRI Ruby on Windows -- Requesting non-MRI Ruby engines (jruby, truffleruby, etc.) on Windows now fails early with a clear error message explaining that only standard MRI Ruby is supported via RubyInstaller2, instead of producing a confusing 404 from an invalid download URL. #8539 by @jdx
Added
tigerbeetle(github:tigerbeetle/tigerbeetle) to the tool registry. #8514 by @risu729Breaking Changes
envtags withinmise.lockfor environment-specific version pinning, runningmise lockwill migrate to the new format automatically, creating separatemise.<env>.lockfiles. Make sure to commit the new lockfiles and update your.gitignoreif needed formise.<env>.local.lockfiles.touch_outputsremoved: If you were usingtouch_outputsin prepare provider configuration, that field is no longer recognized. Freshness is now determined entirely by blake3 hashing of source files.New Contributors
Full Changelog: jdx/mise@v2026.3.5...v2026.3.6
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.