github jdx/mise v2026.11.10
v2026.11.10: Check lockfiles in CI with `mise lock --check`, plus an `enable_backends` allowlist

2 hours ago

mise lock gains an offline --check mode for CI, and --dry-run now shows what would actually change. New options let you limit mise to an allowlist of backends, choose musl or glibc builds for a single tool, pin PyPI packages to private uv indexes, and exclude git-ignored files from task sources. This release also fixes problems with lockfiles, Java build ordering, mise exec PATH order, Homebrew formulas, and shims.

Added

Lockfiles

  • mise lock --check. Checks that mise.lock matches mise.toml without writing anything or using the network. It fails with a list of everything mise install --locked would reject: a version that isn't locked (for example, when an update bot bumps mise.toml but not the lockfile), a platform entry with no URL, or a checksum that is missing or malformed. It also reports missing GitHub additional artifacts and missing or edited npm/PyPI dependency graphs. Platforms are chosen the same way mise lock chooses them. --json prints one object per platform entry. It can't be combined with --bump, --upgrade, --dry-run, --minimum-release-age, --sidecars or a tool@version argument. #15768 (@jdx, @jmoreno11)

    $ mise lock --check
    mise ERROR ~/src/app/mise.lock would fail a locked install:
      - jq@1.6 is not in the lockfile
      - No lockfile checksum found for yq@4.44.1 on platform linux-x64 (...) (--locked mode)
    hint: run `mise lock` to update the lockfile
  • Provenance in --check output. Each platform entry now shows what it was verified with when it was locked: minisign, cosign, slsa, github-attestations, checksum only, or none. --json adds a matching provenance field. This information is for display only and doesn't change whether the check passes. #15769 (@jdx, @jmoreno11)

Backends

  • enable_backends allowlist. Only the backends you list can resolve or install tools. Registry shorthands fall back to their next allowed backend, and an identifier that uses a backend you didn't list fails with an error that names the setting. disable_backends still applies on top of the allowlist. An empty list, the default, allows every backend. The setting checks each tool's configured backend, not tools that a backend runs itself (such as the node used by npm:). mise install-into now respects both settings. #15766 (@jdx, @jmoreno11)

    [settings]
    enable_backends = ["core", "aqua", "github"]
  • Per-tool libc for packslip and github tools. On Linux, libc = "musl" or libc = "glibc" (also gnu) selects the build for one tool without changing the global libc setting. Once you set it, mise never falls back to the other libc. It errors if no matching build exists. The option is recorded in the lockfile, and you need mise install --force to replace an existing install after changing it. It also works with the gitlab and forgejo backends. #15765 (@jdx, @jmoreno11)

    [tools]
    fnox = { version = "latest", libc = "musl" }
  • filter_bins for http: tools. Only the named executables are put on PATH, instead of the whole bin_path directory. The cursor-agent registry entry now uses this, so its bundled node and rg no longer override your own. #15835 (@jdx)

  • Private uv indexes for pypi: packages. The new indexes and sources tool options take individual packages (the tool or its with/expose requirements) from a named index, while everything else stays on the default index. They mirror uv's tool.uv.index and tool.uv.sources, require uv and a dependency graph, and are recorded in mise.lock. Index URLs can't contain credentials. Use UV_INDEX_<NAME>_USERNAME and UV_INDEX_<NAME>_PASSWORD instead. #15840 (@jdx, @sisp)

    [tools."pypi:zensical"]
    version = "0.1.1"
    with = ["my-zensical-theme==1.2.3"]
    indexes = [{ name = "private", url = "<your private index URL>", explicit = true }]
    sources = { my-zensical-theme = { index = "private" } }

Tasks

  • !@gitignore in sources. This entry removes git-ignored, untracked files from what the earlier entries matched, so build output or node_modules no longer makes a task stale. Like a ! pattern, it is evaluated in order, so a later entry can add an ignored path back. Tracked files always count as sources. Only the repository's own .gitignore files and .git/info/exclude are used, not your global excludes file. #15796 (@jdx, @brodienguyen)

    [tasks.build]
    sources = ["pkg/**", "!@gitignore", "pkg/dist/**"]
  • Task completion offers one spelling per task. In a monorepo, mise run <TAB> now suggests only the shortest name for each task. Typing : shows names qualified for the current config root, and // shows absolute paths. Every spelling still runs. #15832 (@jdx)

  • Set one lock pool at a time. mise settings set task.lock_pools.cpu 8 and mise settings unset task.lock_pools.cpu change a single entry without replacing the whole map. This works for any map setting, such as url_replacements. Pool sizes can also come from MISE_TASK_LOCK_POOLS, as cpu=8,gpu=1 or a JSON object. #15794 (@jdx)

Bootstrap

  • Enable services without starting them. In [bootstrap.services], state = "unchanged" only manages whether a unit starts at boot or login. mise never starts, stops, reloads or restarts it. This is useful for units such as a login manager. It works for system units and existing user units. It is rejected with masked = true and for user services that mise defines with command or builtin. #15759 (@jdx, @Vantesh)

    [bootstrap.services.greetd]
    state = "unchanged"
    enabled = true
  • [bootstrap.files] and [bootstrap.directories] now accept permissions as another name for mode, the same key [dotfiles] uses. Setting both is an error. #15849 (@jdx, @syhol)

Registry

Changed

  • mise lock --dry-run reports real changes. It now resolves every tool and platform the same way mise lock does and compares the result with the lockfile on disk. Each entry is listed as a new entry, a version change, a new platform, changed fields (such as checksum filled), a removal, or unchanged. Because of this, a dry run now makes network requests, may download artifacts to compute checksums, and fails wherever mise lock would fail. --json output is unchanged. #15767 (@jdx, @jmoreno11)
  • tool_config.locked lockfiles are left alone after installs. When every config that writes a lockfile sets [tool_config] locked = true, mise install, mise exec, mise use and other install paths no longer add platforms, refresh entries or prune stale tools in that lockfile. Only mise lock (and mise upgrade for newer versions) changes it. As a result, entries for removed tools now stay until you run mise lock. #15761 (@jdx, @jmoreno11)
  • The packages a plugin needs from the system (its systemDependencies) are now installed with the Linux distribution's package manager (apk, apt, dnf, pacman, zypper) when it has a hint for them, instead of mise's built-in Homebrew. Libraries installed through Homebrew could not be found by the system pkg-config or compiler. #15839 (@jdx)

Fixed

  • Java: with several builds of the same version installed (such as Temurin +7 and +101), mise ls, the runtime symlinks (latest, temurin-25, ...), lockfile selection and mise outdated now treat the higher build number as newest. #15756 (@jdx)
  • When several mise install processes ran at once, an npm: tool could fail because its node@lts dependency was "not installed", even after another process had just installed it. #15757 (@jdx)
  • mise install <tool> and mise x <tool> now fail with a clear message when the tool's os option excludes the current platform. Previously the error was about a missing release asset. #15826 (@jdx)
  • With tool_config.locked, a tool limited to another OS no longer prints a "not in the lockfile" warning on every command. #15848 (@jdx)
  • When mise lock refuses an aqua SLSA provenance downgrade, the error now suggests setting slsa_signer_identity and slsa_signer_issuer in the tool options. #15827 (@jdx)
  • mise x -- <cmd> runs the pinned tool's binary again, for example the pinned npm instead of Node's bundled npm, even when the inherited PATH already contains that tool's bin directory. #15838 (@jdx)
  • Inactive shims that fall back to a system binary no longer run rustup checks when rust is configured. These checks could interfere with mise up. #15795 (@jdx)
  • npm: installs with provenance verification work again on images without system CA certificates (such as node:24-slim). The sigstore TUF fetch now uses mise's HTTP client, which falls back to the bundled roots. #15829 (@jdx)
  • Homebrew formulas: source builds from third-party taps that use HOMEBREW_PREFIX and related constants now work. Files that a formula installs into bin or sbin are now executable. #15834, #15836 (@jdx)
  • Ruby previews such as ruby = "4.1.0-preview1" now install from precompiled builds that are published as GitHub pre-releases, instead of failing or compiling from source. #15830 (@jdx)
  • Installing rust@beta or rust@nightly with a minimum_release_age cutoff now stops after fetch_remote_versions_timeout with a clear error, instead of searching a slow dist server for minutes. #15847 (@jdx)
  • mise prune no longer marks the commit that latest currently points to as prunable for an npm: git source that tracks the default branch. If mise can't reach the remote, it keeps every install. #15837 (@jdx)
  • mise ls --all-sources no longer hides a tool when a different tool is pinned to the same version. #15833 (@jdx)
  • mise bootstrap --from <url> --update now pulls the source repository before loading its config. A source whose current commit has a broken config can now pick up its own fix. #15841 (@jdx, @Guria)

Documentation

  • The task docs now say that a dependency requested with different arguments runs once for each set of arguments. #15855 (@jdx)

Full Changelog: v2026.11.9...v2026.11.10

💚 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.

Don't miss a new mise release

NewReleases is sending notifications on new releases.