337 commits

Author	SHA1	Message	Date
Charlie Marsh	2c0d166260	Add only-emit-workspace and similar variants to uv export (#16681) ... ## Summary This is useful for scenarios in which you want to emit the workspace dependencies, but nothing else.	2025-11-12 16:51:45 +00:00
liam	63ab247765	Allow explicit values with uv version --bump (#16555) ... Resolves https://github.com/astral-sh/uv/issues/16427 This PR updates `uv version --bump` so you can pin the exact number you’re targeting, i.e. `--bump patch=10` or `--bump dev=42`. The command-line interface now parses those `component=value` flags, and the bump logic actually sets the version to the number you asked for.	2025-11-11 12:27:32 -05:00
Mathieu Kniewallner	9a21897f3d	feat(cli): expose UV_NO_DEFAULT_GROUPS environment variable (#16645) ... <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary Similarly to #16529 that adds `UV_NO_GROUP`, this adds `UV_NO_DEFAULT_GROUPS` that does the same as `--no-default-groups`. This can be useful on the CI, to disable default groups on a job without having to set the argument in all commands that could trigger a sync (for instance [here](8757b318e9/.github/workflows/main.yml (L105-L116))). ## Test Plan Snapshot tests. --------- Co-authored-by: samypr100 <3933065+samypr100@users.noreply.github.com>	2025-11-10 14:43:48 -06:00
Haaris Rahman	e5c10cd45d	Fix typo in uv tool list doc (#16625) ... <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary Fixed a typo in the docs. Regenerated the docs, with the fix. <!-- What's the purpose of the change? What does it do, and why? -->	2025-11-06 22:06:17 -06:00
Charlie Marsh	5fe8af114b	Accept multiple packages in uv export (#16603) ... ## Summary Closes https://github.com/astral-sh/uv/issues/16503.	2025-11-05 22:52:22 +00:00
Charlie Marsh	9a6eafc043	Accept multiple packages in uv sync (#16543) ... ## Summary Closes https://github.com/astral-sh/uv/issues/12130. --------- Co-authored-by: Zanie Blue <contact@zanie.dev> Co-authored-by: konsti <konstin@mailbox.org>	2025-11-04 14:17:58 +00:00
chisato	8b479efd2f	Add a uv cache size command (#16032) ... ## Summary <!-- What's the purpose of the change? What does it do, and why? --> Implement `uv cache size` to output the cache directory size in raw bytes by default, with a `--human` option for human-readable output. close #15821 <!-- How was it tested? --> --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-11-02 20:44:28 +00:00
Blair Allan	4b61e65d6c	Add UV_NO_SOURCES as an environment variable (#15883) ... ## Summary This is an enhancement that makes the cli flag `--no-sources` an environment variable - "UV_NO_SOURCES" Why is this a relevant change? When working across different environments, in our case remote vs local, we often have our packages hosted in a artifact registry but when developing locally we build our packages from github. This results in us using the uv.tool.sources table quite a bit however this then also forces us to use `--no-sources` for all our remote work. This change enables us to set an environment variable once and to never have to type --no-sources after every uv run command again. ## Test Plan Expanded on the current --no-sources tests, to test when UV_NO_SOURCES=true/false the behaviour is the same as the flag. Additionally ensured that the cli overrides the env variable. --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-11-02 20:25:19 +00:00
Charlie Marsh	5c71b5c124	Enable first-class dependency exclusions (#16528) ... ## Summary This PR adds an `exclude-dependencies` setting that allows users to omit a dependency during resolution. It's effectively a formalized version of the `flask ; python_version < '0'` hack that we've suggested to users in various issues. Closes #12616.	2025-10-31 10:14:12 -04:00
Charlie Marsh	7cf1646a44	Expose UV_NO_GROUP as an environment variable (#16529) ... ## Summary Closes https://github.com/astral-sh/uv/issues/11619.	2025-10-30 22:34:14 -05:00
Alexander Vandenbulcke	c156b1d50d	Don't use UV_LOCKED to enable --check flag (#16521) ... Env var UV_LOCKED should only be used to enable `--locked` for the `uv lock` command. Previously `--check` was also enabled by specifying UV_LOCKED.	2025-10-30 15:37:27 -04:00
konsti	cfa1de311e	Add --no-create-gitignore to uv build (#16369) ... Fixes #16332	2025-10-28 07:25:31 -05:00
konsti	804f1ff808	Add --clear to uv build to remove old build artifacts (#16371) ... Add `uv build --clear` that behaves like `rm -r ./dist && uv build` to clear artifacts from previous builds. This avoids accidentally publishing the wrong artifacts and removes accumulated old builds. See https://github.com/astral-sh/uv/issues/10293#issuecomment-3405904013 Fixes #10293	2025-10-27 18:15:17 +00:00
Charles-Meldhine Madi Mnemoi	225bffbb6c	Running uv lock --check with outdated lockfile will print that --check was passed, instead of --locked (#16322) ... Hello, # Summary This PR fixes the confusing error message when running `uv lock --check` with an outdated lockfile. Previously, the error message incorrectly stated that `--locked` was provided, even when the user used `--check`. Now, the error message correctly indicates which flag was used: either `--check` or `--locked`. This closes #14105. # Test plan - I updated the existing integration test (`check_outdated_lock` in `lock.rs`) to verify the new error message includes the correct flag. - I ran existing tests to ensure I have no introduced regressions for other commands.	2025-10-21 12:46:10 -05:00
Charlie Marsh	bf81a5bf0c	Add CUDA 13.0 support (#16321) ... ## Summary Closes https://github.com/astral-sh/uv/issues/16319.	2025-10-15 15:10:08 -04:00
Harshith VH	b4168e665e	Add uv tool list --show-python (#15814) ... <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> Closes #15312 Closes https://github.com/astral-sh/uv/issues/16237 --------- Co-authored-by: pythonweb2 <32141163+pythonweb2@users.noreply.github.com> Co-authored-by: Wade Roberts <wade.roberts@centralsquare.com>	2025-10-10 12:33:26 -05:00
Shunsuke Tsuchiya	39e2e3e74b	Support UV_WORKING_DIRECTORY for setting --directory (#16125) ... <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary <!-- What's the purpose of the change? What does it do, and why? --> This pull request enables the `--directory` option to accept environment variable: `UV_DIRECTORY` ### Motivation Currently, the `--project` option already supports environment variables, but --directory does not. The motivation for this change is the same as for the --project option. When using this option, it’s likely that the project root and the directory containing the uv project differ. In such cases, allowing environment variables makes it easier to avoid repeatedly specifying the directory in commands or task runners. ### Other PRs - PR for create `--project` option: https://github.com/astral-sh/uv/pull/12327 ## Test Plan <!-- How was it tested? --> ### no auto testing As with the --project option, no auto tests are included for this change. This is because the implementation relies on Clap’s built-in attribute functionality, and testing such behavior would effectively mean testing a third-party crate, which would be redundant. As long as the compiler accepts it, things should work as expected. ### testing manually i tested manually like [previous pull request](https://github.com/astral-sh/uv/pull/12327) ```shell $ cargo build --locked ./target/debug/uv init uv_directory $ mkdir uv_directory $ UV_DIRECTORY=uv_directory ./target/debug/uv sync Using CPython 3.14.0rc3 Creating virtual environment at: .venv Resolved 1 package in 15ms Audited in 0.04ms $ UV_DIRECTORY=uv_directory ./target/debug/uv run main.py Hello from uv-directory! $ ./target/debug/uv run main.py error: Failed to spawn: `main.py` Caused by: No such file or directory (os error 2) ``` --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-10-08 08:46:11 -05:00
Zanie Blue	7e4edf0fb4	Add --force flag for uv cache prune (#16137) ... Matching #15992 See https://github.com/astral-sh/setup-uv/issues/588	2025-10-06 11:36:58 -05:00
Andrei Berenda	372283c0cf	Add install_mirrors to EnvironmentOptions (#15937) ... ## Summary Add install_mirrors to EnvironmentOptions Relates #14720 ## Test Plan Tests with existing tests	2025-09-25 10:35:09 -05:00
Zanie Blue	107d4e0ac7	Add --force flag for uv cache clean (#15992) ... Follows https://github.com/astral-sh/uv/pull/15990 to address concerns there.	2025-09-22 22:15:14 +00:00
Zanie Blue	0edc5677ad	Document support for free-threaded and debug Python versions (#15961) ... Closes #12707 --------- Co-authored-by: Geoffrey Thomas <geofft@ldpreload.com>	2025-09-22 13:59:40 +00:00
Charlie Marsh	422863ffde	Infer check URL from publish URL when known (#15886) ... ## Summary If we know the publish URL-to-check URL mapping, we can just infer it.	2025-09-16 14:03:03 +00:00
Harsh Pratap Singh	5f2871e695	Support Gitlab CI/CD as a trusted publisher (#15583) ... Co-authored-by: William Woodruff <william@astral.sh>	2025-09-11 10:35:04 -04:00
Yiğit Ö. Ünver	19ea0f4932	support --no-project in uv format (#15572) ... When a user passes `--no-project` argument to `uv format` command, instead of running the formatter in the context of the current project, run it in the context of the current directory. This is useful when the current directory is not a project. Closes https://github.com/astral-sh/uv/issues/15462	2025-09-08 16:16:40 -05:00
Zanie Blue	5f8c7181b9	Improve the CLI help for options that accept requirements files (#15706)	2025-09-08 08:23:52 -05:00
Ahmed Ilyas	6eefde28e7	Support --with-requirements script.py and -r script.py to include inline dependency metadata from another script (#12763) ... ## Summary Closes #6542 ## Test Plan `cargo test`	2025-09-05 11:45:46 -05:00
timrid	330e56e778	Support iOS platform tags (#15640) ... ## Summary This implements the iOS part of https://github.com/astral-sh/uv/issues/8029 FYI: @freakboy3742 <!-- What's the purpose of the change? What does it do, and why? --> ## Test Plan Create a venv with uv and run `cargo run pip install --python-platform arm64-apple-ios pillow`. Then the iOS binary of pillow should be installed inside the venv.	2025-09-03 18:24:48 -04:00
timrid	d178e45368	Support Android platform tags (#15646) ... ## Summary This implements the Android part of https://github.com/astral-sh/uv/issues/8029 FYI: @freakboy3742 @mhsmith <!-- What's the purpose of the change? What does it do, and why? --> ## Test Plan Create a venv with uv and run `cargo run pip install --python-platform aarch64-linux-android pybase64`. Then the Android binary of pybase64 should be installed inside the venv.	2025-09-03 10:24:33 -04:00
konsti	a94f7d0847	Clarify that uv auth commands take a URL (#15664) ... From the previous description I tried `uv auth token pyx`, which didn't work. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-09-03 14:16:16 +00:00
Charlie Marsh	ad35d120d6	Make uv auth dir service-aware (#15649) ... ## Summary This got lost when https://github.com/astral-sh/uv/pull/15637 was merged into not-`main`.	2025-09-02 22:58:59 -04:00
Charlie Marsh	7606f1ad3c	Add uv publish --dry-run (#15638) ... ## Summary `uv publish --dry-run` will perform the `--check-url` validation, and hit the `/validate` endpoint if the registry is known to support fast-path validation (like pyx). The `/validate` endpoint lets us validate an upload without uploading the file _contents_, which lets you skip the expensive step for common mistakes. In the future, my hope is that the `/validate` step will deprecated in favor of Upload API 2.0.	2025-09-02 21:24:31 -04:00
Zanie Blue	f9e98d1fb6	Allow providing the uv auth login password or token via stdin (#15642)	2025-09-02 16:59:58 -05:00
Zanie Blue	709e0ba238	Remove the native system store from the keyring providers (#15612) ... We're not sure what the best way to expose the native store to users is yet and it's a bit weird that you can use this in the `uv auth` commands but can't use any of the other keyring provider options. The simplest path forward is to just not expose it to users as a keyring provider, and instead frame it as a preview alternative to the plaintext uv credentials store. We can revisit the best way to expose configuration before stabilization. Note this pull request retains the _internal_ keyring provider implementation — we can refactor it out later but I wanted to avoid a bunch of churn here.	2025-09-02 13:16:52 -05:00
Zanie Blue	7d627b50ef	Add uv auth dir (#15600)	2025-09-02 13:16:52 -05:00
Charlie Marsh	7d9446450b	Misc. tweaks	2025-09-02 13:16:52 -05:00
Zanie Blue	460ea6e9eb	Add uv auth commands (login, logout, and token) (#15539) ... Picks up the work from - #14559 - https://github.com/astral-sh/uv/pull/14896 There are some high-level changes from those pull requests 1. We do not stash seen credentials in the keyring automatically 2. We use `auth login` and `auth logout` (for future consistency) 3. We add a `token` command for showing the credential that will be used As well as many smaller changes to API, messaging, testing, etc. --------- Co-authored-by: John Mumm <jtfmumm@gmail.com>	2025-09-02 13:16:52 -05:00
Jo Shields	f76e0fe5e6	Add --python-platform riscv64-unknown-linux to various commands (#15630) ... ## Summary We (and I'm sure many others) are currently doing a lot of RISC-V work in QEMU. It is possible to significantly improve the speed of Python-related builds by taking care of the environment setup using an AMD64 `uv` binary (bypassing binfmt/qemu-system emulation). Some approx numbers from local testing in riscv64 Ubuntu in QEMU: | Resolver arch | Command | Time | | --- | --- | --- | | riscv64 | `pip install --upgrade --break-system-packages --index-url=https://gitlab.com/api/v4/projects/riseproject%2Fpython%2Fwheel_builder/packages/pypi/simple openai-harmony` | 15s | | riscv64 | `uv pip install --upgrade --system --break-system-packages --index-url=https://gitlab.com/api/v4/projects/riseproject%2Fpython%2Fwheel_builder/packages/pypi/simple openai-harmony` | 5s | | amd64 | `uv pip install --python-platform=riscv64-unknown-linux --upgrade --system --break-system-packages --index-url=https://gitlab.com/api/v4/projects/riseproject%2Fpython%2Fwheel_builder/packages/pypi/simple openai-harmony` | 4s | The numbers from some larger internal packages with deeper dependency trees are much more pronounced - 3m6 vs 43s vs 8s, in one example. Manylinux 2.39 is specified, as it's the first (only?) RISC-V manylinux ## Test Plan Locally, in QEMU. `$ docker run --platform linux/riscv64 -it ubuntu:latest`, get amd64 libc into LD_LIBRARY_PATH, tests as above	2025-09-02 13:17:30 -04:00
Harsh Pratap Singh	d877899920	Add uv tree --show-sizes to show package sizes (#15531) ... <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary Adds the enhancement proposed in #15470. Each package in the dependency tree now shows its compressed wheel file size, reading the wheel sizes directly from the lockfile (uv.lock). Doesn't break existing tree formatting or options. If no wheel size is available, nothing is added. Now, developers can identify large packages in their dependency tree. The tree still shows extras exactly as before, and then appends a size for the package. ## Test Plan Manually tested : ``` harsh@fcr-node:~/uv/test-uv-tree-sizes$ ../target/debug/uv tree Using CPython 3.13.7 warning: No `requires-python` value found in the workspace. Defaulting to `>=3.13`. Resolved 4 packages in 6ms pure-python v0.1.0 ├── click v8.2.1 └── six v1.17.0 harsh@fcr-node:~/uv/test-uv-tree-sizes$ ../target/debug/uv tree --show-sizes Using CPython 3.13.7 warning: No `requires-python` value found in the workspace. Defaulting to `>=3.13`. Resolved 4 packages in 6ms pure-python v0.1.0 ├── click v8.2.1 (99.8KiB) └── six v1.17.0 (10.8KiB) ```	2025-08-29 08:31:46 -05:00
Charlie Marsh	4168d9b320	Add --python-platform to uv run and uv tool (#15515) ... ## Summary Closes https://github.com/astral-sh/uv/issues/11120.	2025-08-29 00:51:39 +00:00
Charlie Marsh	d19d0e26aa	Add --python-platform to uv pip check (#15486) ... ## Summary I want this to facilitate some testing for https://github.com/astral-sh/uv/issues/15035.	2025-08-24 14:14:42 -04:00
Xavi Simpson	6e2fbbc30f	Add --no-install-local option to uv sync, uv add and uv export (#15328) ... <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary <!-- What's the purpose of the change? What does it do, and why? --> Closes #14866. Adds a `no-install-local` flag to the sync and export commands that excludes locally defined packages from being installed. This helps with if you're caching your virtual environment. You can exclude local packages since they're more likely to change between builds. ## Test Plan snapshot test: `sync::no_install_local` CI ## Notes I made an `InstallOptions` struct to avoid a crate isolation issue I was running into while implementing. Thanks for maintaining this project!	2025-08-22 11:31:52 -05:00
Charlie Marsh	d1e0c26678	Add an environment variable for UV_ISOLATED (#15428) ... Closes https://github.com/astral-sh/uv/issues/15427.	2025-08-21 23:39:04 +01:00
Zanie Blue	f210db0907	Fix format doc mistake (#15433)	2025-08-21 21:12:06 +00:00
youkaichao	b950453891	Add CUDA 12.9 backend (#15416) ... ## Summary Add torch cuda 12.9 backend <!-- What's the purpose of the change? What does it do, and why? --> ## Test Plan <!-- How was it tested? --> --------- Signed-off-by: youkaichao <youkaichao@gmail.com> Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-08-21 16:01:02 +01:00
Zanie Blue	e31f000da7	Add an experimental uv format command (#15017) ... As a frontend to Ruff's formatter. There are some interesting choices here, some of which may just be temporary: 1. We pin a default version of Ruff, so `uv format` is stable for a given uv version 2. We install Ruff from GitHub instead of PyPI, which means we don't need a Python interpreter or environment 3. We do not read the Ruff version from the dependency tree See https://github.com/astral-sh/ruff/pull/19665 for a prototype of the LSP integration.	2025-08-21 06:33:18 -05:00
Charlie Marsh	68f33e8fef	Add --no-install-* arguments to uv add (#15375) ... ## Summary Closes https://github.com/astral-sh/uv/issues/15369.	2025-08-19 15:32:56 +01:00
Zanie Blue	242214c546	Add an aarch64-pc-windows-msvc target (#15347) ... I needed this and was surprised it didn't exist! --------- Co-authored-by: konsti <konstin@mailbox.org>	2025-08-18 17:57:27 +00:00
NewDestinyDan	191c9175fe	Update cli.md to use proper uv cache subcommand "clean" (#15313) ... Correct typo. "uv cache clear" is not a command. <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary <!-- What's the purpose of the change? What does it do, and why? --> ## Test Plan <!-- How was it tested? -->	2025-08-15 21:06:37 +00:00
John Mumm	23245c63e9	Add --reinstall flag to uv python upgrade (#15194) ... As described in #15179, there are cases where it can be useful to reinstall the latest patch on upgrade if it is already installed. Using this flag, you don't need to know ahead of time if you have the latest patch already. Closes #15179.	2025-08-11 15:20:04 -05:00
Charlie Marsh	f6a9b55eb7	Add UV_DEV and UV_NO_DEV environment variables (#15010) ... ## Summary Closes https://github.com/astral-sh/uv/issues/15009. Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-08-08 14:33:44 +00:00