mise v2026.9.7 broke pretty much all pipx tools for me

[sergei-ivanov]

1. Multiple copies of the tool are created.

For example I have now:

$ mise ls pipx:detect-secrets
Tool                 Version  Source                      Requested 
pipx:detect-secrets  1.5.0   
pipx:detect-secrets  1.5.0   
pipx:detect-secrets  1.5.0    ~/.config/mise/config.toml  latest

Uninstallng all versions shows that they have hashes, so effectively 3 separate uv installs for the same version:

$ mise uninstall pipx:detect-secrets --all
✓ removed 3 tools in 20ms: pipx:detect-secrets@1.5.0~uv~14d6fe6f2e3d9d87, pipx:detect-secrets@1.5.0~uv~30f8cd35ad45ced1, pipx:detect-secrets@1.5.0~uv~91fb78da7895d93f
mise WARN  missing: pipx:detect-secrets@latest

Every time I run mise install, it creates yet another installation of pipx:detect-secrets in the mise cache.

2. Some tools plainly refuse to install. They worked perfectly fine up to now.

For example:

$ mise install awscli-local
mise 2026.9.7 by @jdx  ░░░░░░░░░░░░░░░░░░░░░░░░  0/1
mise 2026.9.7 by @jdx  ░░░░░░░░░░░░░░░░░░░░░░░░  0/1
 awscli-local@0.22.2                                                                                                                                                                         ◜
  × No solution found when resolving dependencies:
  ╰─▶ Because all versions of localstack-client have no usable wheels and
      awscli-local>=0.22.2 depends on localstack-client, we can conclude that
      awscli-local>=0.22.2 cannot be used.
      And because your project depends on awscli-local[ver1]==0.22.2, we can
      conclude that your project's requirements are unsatisfiable.
✗ awscli-local@0.22.2  215ms · failed: ~/.local/share/mise/installs/uv/latest/.mise-bins/uv exited with non-zero status: exit code 1
✗ installed 0 tools · 1 failed in 216ms
mise ERROR Failed to install pypi:awscli-local@latest: ~/.local/share/mise/installs/uv/latest/.mise-bins/uv exited with non-zero status: exit code 1
mise ERROR Version: 2026.9.7 linux-x64 (2026-09-13)
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

I can still install awslocal using plain uvx:

$ uvx awscli-local
      Built localstack-client==2.12                                                                                                                                                           Installed 9 packages in 25ms
An executable named `awscli-local` is not provided by package `awscli-local`.
The following executables are available:
- awslocal
- awslocal.bat

Use `uvx --from awscli-local <EXECUTABLE-NAME>` instead.

$ uvx --from awscli-local awslocal --version
aws-cli/2.36.28 Python/3.14.6 Linux/6.17.0-1032-oem exe/x86_64.ubuntu.24

$ uvx --version
uvx 0.12.13 (x86_64-unknown-linux-gnu)

3. Tools installed with uvx_args fail installation without any suggested remediation:

mise.toml:

"pipx:gitlint-core" = { version = "latest", uvx_args = "--with gitlint" }

$ mise install pipx:gitlint-core
✗ pipx:gitlint-core@0.19.1  63ms · failed: pipx:gitlint-core dependency locking does not support uvx_args or pipx_args
✗ installed 0 tools · 1 failed in 64ms
mise ERROR Failed to install pipx:gitlint-core@latest: pipx:gitlint-core dependency locking does not support uvx_args or pipx_args
mise ERROR Version: 2026.9.7 linux-x64 (2026-09-13)
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

[jdx]

Thanks for the detailed report. I confirmed that the source-only dependency failure and the uvx_args/pipx_args failure are compatibility regressions from the new dependency-graph locking behavior.

I opened PR #13170 to restore the previous ordinary-install behavior: when mise cannot create a portable wheel-only graph, or arbitrary installer arguments make graph locking unsafe, mise install warns and falls back to uv's version-only installation path. Subsequent ordinary installs reuse that installation. Explicit mise lock and mise install --locked remain strict so they cannot silently claim reproducibility without a valid graph.

The ~uv~<hash> directories themselves are intentional: the hash identifies the dependency graph, selected Python, and install options, allowing distinct environments for the same top-level version. I could not reproduce a new hash from consecutive installs with identical inputs—the graph identity stayed stable—so this PR does not remove existing hashed directories. Once the PR is available in a build, please retest detect-secrets; if it still creates a fresh hash on every unchanged install, that is a separate identity-stability bug and the before/after MISE_DEBUG=1 mise install pipx:detect-secrets output would help isolate which input is changing.

AI-assisted — Tool: Codex; model: unavailable/unavailable; version: unavailable.

[sergei-ivanov]

Thank you. It looks like the functionality has been restored in 2026.9.12.