mise-en-place
The front-end to your dev env Pronounced "MEEZ ahn plahs"
- site: https://mise.jdx.dev/
New mise audit and mise upgrade --vulnerable commands check your tools against OSV.dev advisories and upgrade the affected ones. This release also adds mise prune --system, a per-tool bump = false option, and more flexible dotfile groups. It fixes lockfile handling for platforms a tool has no build for, PATH setup for locked task tools, and Temurin hotfix versions from .sdkmanrc.
Added
Vulnerability auditing
-
mise auditchecks each tool version your config uses against the OSV.dev database and lists the advisories that affect it. It exits 1 when it finds any, so you can use it to gate CI.mise audit node pythonchecks only the tools you name, and--jsonprints{"vulnerabilities": [...], "unchecked": [...]}. #15942 (@jdx, @johnstegeman)$ mise audit Tool Version ID Severity Fixed Summary npm:lodash 4.17.15 GHSA-35jh-r3h4-6jhm high 4.17.21 Command Injection in lodash ... mise not checked, no known advisory source: zig@0.13.0- These tools are covered:
- registry packages (
npm:,pipx:,cargo:,gem:,go:,dotnet:) - tools released from GitHub or GitLab (
github:,aqua:,packslip:,gitlab:), matched by repository and release tag - the core tools go (as the Go standard library), node, python, deno, bun and erlang
- registry packages (
- Anything else, including tools from private registries or self-hosted
api_urls, is listed as not checked and is never reported as clean. - The audit fails if a configured version doesn't resolve. It needs network access to
api.osv.dev, so it fails in offline mode. Only tool names and versions are sent.
- These tools are covered:
-
mise upgrade --vulnerablelimitsmise upgradeto installed tools with a known vulnerability. Upgrades stay within the configured range unless you add--bump.--dry-run,--excludeand--inactivework as usual. mise warns when an affected tool has no fix in range, when the target version is still affected, and when a tool could not be checked. #15942 (@jdx, @johnstegeman)
Upgrades and pruning
-
Per-tool
bumpoption.bump = falsekeeps a tool out ofmise upgrade --bumpandmise outdated --bump. Those commands still upgrade it within its version request but don't rewrite its entry inmise.toml. This helps when tools like topgrade runmise upgradefor you and can't pass-x. If you name the tool (mise upgrade node --bump), it is still bumped. This option isn't available in.tool-versions. #15947 (@jdx, @gitfool)[tools] node = { version = "lts", bump = false } -
mise prune --systemremoves unused versions from the system installs directory, usingsudowhen that directory is owned by root. A version is kept if a config file your user has loaded (including/etc/mise/config.toml) still selects it, or if a running process you can inspect uses it. mise can't see other users' configs, so it warns about that. Plainmise prunestill leaves system installs alone. #15949 (@jdx, @ioweb-gr)mise prune --system --dry-run mise prune --systemmise upgradenow also cleans up system installs it replaces, after theupgrade.prune_aftergrace period. Before, old versions piled up indefinitely. This background cleanup never asks for a sudo password. If removing a version would needsudo, mise keeps it and tells you to runmise prune --systemor upgrade with--prune.mise uninstallof a system version in a root-owned directory now usessudoinstead of failing.mise reshim --systemno longer drops the shim for a system version that you also have in your own installs directory.
Dotfiles
-
rootin a[dotfile_groups.<name>]table now defaults to the group name. A table that only sets options such asexcludenow deploys instead of failing withroot: is required. Invalid groups no longer print a second, misleading "no table declares it" warning. #15953 (@jdx, @lhs-12) -
A dotfile group entry can now deploy outside the group's
target, so a package whose files go to more than one place can be a single group. These entries need an explicitsource, unless their mode takes none (such asabsent). They are applied, unapplied and pruned with the rest of the group. The docs now also show how to deploy only a group's entries withexclude = ["/*"]. #15954 (@jdx, @lhs-12)[dotfile_groups.vscode] root = "vscode/.config" target = "~/AppData/Roaming" [dotfile_groups.vscode.entries] "~/.crossnote" = { source = "crossnote", mode = "symlink" }
Daemons
- A daemon project reference now exports
<NAME>_PORTand<NAME>_URLunder its local name. For example,[daemons.search]withproject = "../search"providesSEARCH_PORTandSEARCH_URL. With pitchfork 2.36.0 or later,{{ daemons.search.url }}also resolves in templates. Older pitchfork versions still get plain dependency IDs. Local daemons win when names collide. #15956 (@jdx, @jholzinger-hadrian)
Fixed
- Lockfiles and platforms with no build.
mise locknow records platforms a tool has no build for in a newunsupported_platformslist inmise.lock.mise lock --checkthen passes for those platforms unless you name one with--platform. Before,--checkfailed on a lockfile thatmise lockhad just written.mise install --lockedon a listed platform now reports that there is no build, instead of "No lockfile URL found". Auto-lock no longer resolves listed platforms again on every install. Node (withnode.compileoff) and PyPy now report missing builds this way too. The lockfile format version is unchanged. Older mise versions ignore the field but drop it if they rewrite the file. #15952, #15941 (@jdx, @NVolcz)- In the default generate mode,
mise locknow refuses a version upgrade that would drop a platform the old version supported. Before, it silently pruned the old version and wrote a lockfile without that platform. #15939 (@jdx, @NVolcz)
- Locked task tools. A tool pinned in a task's
toolsand locked withmise lockis now on the task'sPATHon a fresh machine. Before, it was installed but missing fromPATH, so the task failed or ran another copy of the command. #15958 (@jdx, @hajikelu) - Secrets in tasks. Tasks can now list keys from your own fnox config, and tasks in your global or system mise config can list secrets. Both used to be refused, so you had to pass
mise run --secrets KEYon every run.--secrets-allstill leaves your own keys out unless the task names them. Remote tasks still can't list secrets. As a result,mise secrets ls --jsonandmise tasks validateno longer report the problem kindspersonalornot_project_config. #15937 (@jdx) - Java.
.sdkmanrcentries for Temurin hotfix releases, such asjava=25.0.5.1+2-tem, install again. They now resolve to the canonical catalog version (temurin-25.0.5.1+2). #15928 (@jdx) mise deps. Theaubeprovider now watchesaube-workspace.yaml(andpnpm-workspace.yamlwhen aube falls back to it) as well as each workspace member'spackage.json. Edits to catalogs, overrides or member dependencies are no longer reported as "fresh". #15940 (@jdx)
Documentation
- The
mise watchhelp now explains that tasks separated by:::share one watcher, so a change to any task's sources reruns all of them. To restart tasks independently, use a separatemise watchper task. #15938 (@jdx)
Breaking Changes
- Temurin hotfix versions. The Java catalog now lists Temurin hotfixes under their canonical version. If you pinned an old encoded hotfix string such as
temurin-25.0.4+101, change it totemurin-25.0.4.1+1. #15928
Full Changelog: https://github.com/jdx/mise/compare/v2026.11.11...v2026.11.12
💚 Sponsor mise
mise is built and maintained by @jdx, an open source developer at entire.io, the title sponsor of his open source work.
If mise saves you or your team time, please consider becoming an individual or company sponsor. Your support funds ongoing development and helps keep mise fast, free, and independent.