Skip to content

fix(pipx): upgrade shared pip environment when using version constraints #10138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jdx merged 1 commit into from
May 31, 2026
+1 −0
Merged

fix(pipx): upgrade shared pip environment when using version constraints #10138

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/dev-tools/backends/pipx.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,7 @@ If you have `uv` installed, mise will use `uv tool install` under the hood and y
When [`minimum_release_age`](/configuration/settings.html#minimum_release_age) is set, mise forwards the cutoff
to transitive Python dependency resolution during install. The uv install path uses uv's
`--exclude-newer` flag, and the `pipx` fallback passes pip's `--uploaded-prior-to` flag.
When using `minimum_release_age` with the `pipx` install path, `pip >= 26.0` is required for pip's `--uploaded-prior-to` support, and you are responsible for ensuring that compatible Python/pip environment is installed.

In case you need `pipx` for other reasons, you can install it with or without mise.
Here is how to install `pipx` with mise:
Expand Down
Loading