fix(pipx): preserve options when reinstalling tools

[risu729]

Summary

• Reuse the normal pipx backend install flow when Python upgrades trigger pipx tool reinstalls.
• Preserve install-time options such as uvx_args, pipx_args, extras, and per-tool uvx = false during those reinstalls.
• Add coverage to the existing pipx/uvx e2e so mise up --bump python must pass uvx_args during the reinstall step.

Analysis

The report is true for the Python-upgrade reinstallation path, not for ordinary pipx tool upgrades. install_version_ already passes uvx_args and pipx_args, but PIPXBackend::reinstall_all hand-built fresh uv tool install / pipx reinstall commands after a Python upgrade. That bypassed the existing option handling and could reinstall a pipx tool without its configured extras or installer args.

I also checked the recently added npm package-manager install args. The npm backend applies npm_args, pnpm_args, bun_args, and aube_args inside its normal install_version_ path, and npm does not have a separate post-Node-upgrade reinstall path equivalent to PIPXBackend::reinstall_all.

Source: #7219

Testing

• cargo fmt --all -- --check
• cargo check --all-features
• mise run test:e2e e2e/backend/test_pipx_uvx

Note: mise run format was also attempted, but it failed in the existing taplo check registry schema validation with repeated Invalid reference: https://mise.en.dev/schema/mise-registry-tool.json#/definitions/os errors. The schema formatting changes produced before that failure were not included.

This PR was generated by an AI coding assistant.

[greptile-apps]

Greptile Summary

This PR fixes a bug where PIPXBackend::reinstall_all — called after a Python upgrade — would bypass all install-time option handling and reinstall pipx tools without their configured uvx_args, pipx_args, extras, or per-tool uvx settings. The fix replaces the hand-rolled UV/pipx commands with a direct call to install_version (which already handles all those options) and adds a functional e2e assertion verifying that an --with rich extra is preserved through the upgrade cycle.

• src/backend/pipx.rs: reinstall_all now builds an InstallContext with force: true and delegates to b.install_version(ctx, tv), inheriting full option-handling from install_version_. The ToolVersion objects returned by list_installed_versions carry the configured options from .mise.toml when the installed version matches a toolset entry, so options are correctly threaded through.
• e2e/backend/test_pipx_uvx: Adds uvx_args = \"--with rich\" to the mkdocs fixture and, after mise up --bump python, directly verifies that import rich succeeds inside the reinstalled venv — a functional check independent of log-format details.

Confidence Score: 5/5

Safe to merge; the refactor correctly threads install options through the existing install_version path and the new e2e assertion directly validates the behaviour being fixed.

The change is narrow and the logic is sound: list_installed_versions returns ToolVersion objects that carry options from the toolset config when the installed version matches a configured entry, so delegating to install_version with force: true preserves all install-time options that were lost before. The force: true flag triggers the existing uninstall-then-reinstall flow, mirroring the original sequential uv tool uninstall + uv tool install pattern. The e2e test validates end-to-end that --with rich (via uvx_args) survives a Python bump reinstall.

No files require special attention.

_{Reviews (3): Last reviewed commit: "Merge branch 'main' into fix/pipx-reinst..." | Re-trigger Greptile}

[gemini-code-assist]

Code Review

This pull request adds support for uvx_args in the pipx backend and refactors the reinstall_all function to use the standard install_version interface. A review comment points out that the reinstall_all implementation hardcodes dry_run: false in the InstallContext, which could lead to unexpected system changes if a user expects a dry run to be respected.