mise 2026.5.9

[BrewTestBot]

Created by brew bump

---

Created with brew bump-formula-pr.

Details

release notes

A modest release: SwiftPM gains artifact bundle support, `[[watch_files]]` hooks can pick their own inline shell, and a handful of fixes land for aqua latest-tag resolution, vfox `cmd.exec`, and GitHub OAuth device-flow URLs. Plain-string Tera rendering also gets a fast path.
Added


(spm) SwiftPM installs now prefer prebuilt artifact bundles (*.artifactbundle.zip) when a release publishes one for the current Swift target triple, falling back to a source build otherwise (#9825) by @ikesyo. New controls:
[tools]
# require an artifact bundle; fail instead of source-building
"spm:giginet/swift-testing-revolutionary" = { version = "0.4.0", artifactbundle = true }

# always source-build, ignore any bundles
"spm:tuist/tuist" = { version = "latest", artifactbundle = false }

# disambiguate when multiple bundle assets are published
"spm:org/tool" = { version = "1.0.0", artifactbundle_asset = "tool.artifactbundle.zip" }

[settings]
# apply "bundles only" globally (mirrors cargo.binstall_only)
spm.artifactbundle_only = true


(config) [[watch_files]] entries with run accept an optional shell field, rendered through templates and falling back to the configured default inline shell when unset (#9810) by @risu729:
[[watch_files]]
patterns = ["*.js"]
run = "eslint --fix ."
shell = "bash -c"
shell only applies to run hooks; combining it with task produces a warning and the value is ignored.


Fixed

(aqua) When GitHub's latest release pointed at a tag that aqua's registry rejected via version_filter or version_constraint, mise would return it anyway. The latest fast path now applies both checks before accepting a tag (#9834) by @risu729.
(vfox) Lua cmd.exec calls inside vfox plugins now build commands from mise's configured unix_default_inline_shell_args / windows_default_inline_shell_args instead of hardcoding sh -c or cmd /C, aligning plugin behavior with tasks, Tera command rendering, and other inline shell users (#9837) by @risu729.
GitHub OAuth device-flow paths were slightly off compared to the documented endpoints. The default oauth_auth_url is now the GitHub login base, with mise appending /device/code and /oauth/access_token per GitHub's device-flow docs (#9791) by @jasisk.
(patrons) mise patrons now points the "become a patron" link to the en.dev homepage instead of /sponsor (#9868) by @jdx.

Changed

(registry) npm is now resolved through aqua:npm/cli (with npm:npm retained as a fallback), and buck2 switches to aqua:facebook/buck2 with prerelease = true so its always-prerelease releases are visible (#9762, #9805) by @risu729.
(registry) Added SonarQube CLI as aqua:SonarSource/sonarqube-cli (#9824) by @3PeatVR.

Performance

(config) Strings with no Tera block markers ({{, {%, {#, including whitespace-trimmed forms) now bypass the Tera renderer at config evaluation sites, skipping context construction, async context fetches, and get_tera setup. Tera 1.20.1's grammar guarantees these are the only block openers, so output is unchanged for both well-formed and malformed templates (#9833) by @risu729.

Documentation

Updated the Walkthrough guide (#9853) by @thernstig.

New Contributors

@3PeatVR made their first contribution in #9824
@ikesyo made their first contribution in #9825
@thernstig made their first contribution in #9853

Full Changelog: jdx/mise@v2026.5.8...v2026.5.9
💚 Sponsor mise
mise is built by @jdx under en.dev — an independent studio making developer tooling (mise, aube, and more). Development is funded by sponsors.
If mise saves you or your team time, please consider sponsoring at en.dev. Individual and company sponsorships keep mise fast, free, and independent.

View the full release notes at https://github.com/jdx/mise/releases/tag/v2026.5.9.

---

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Caution

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.