489 commits

Author	SHA1	Message	Date
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
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
Harshith VH	2825ee3435	Add --no-clear to uv venv to disable removal prompts (#15795) ... <!-- 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 #15485 --------- Co-authored-by: Aditya-PS-05 <adityapratapsjnhh7654@gmail.com> Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-09-16 08:24:57 -05:00
Charlie Marsh	f59d00b479	Allow escaping spaces in --env-file handling (#15815) ... ## Summary We allow space-delimiting for `--env-file`, but Clap doesn't support any form of escaping, so as-is, there's no way to provide a `.env` file in a directory that contains a space. We now do the splitting ourselves and respect escapes. Closes https://github.com/astral-sh/uv/issues/15806.	2025-09-12 18:11:51 -04:00
Harshith VH	a0f8359012	Add conflict detection between --only-group and --extra flags (#15788) ... <!-- 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 - Added `conflicts_with = "only_group"` to `--extra` arguments in `SyncArgs`, `RunArgs`, and `ExportArgs` - Added tests to verify proper conflict detection and error messages **Before:** The `--extra` flag was silently ignored when used with `--only-group` **After:** Clear error message: `error: the argument '--only-group <ONLY_GROUP>' cannot be used with '--extra <EXTRA>'` fixes: #15676 ## Test Plan - Tests confirm proper error message format when `--only-group` and `--extra` are used together - Verified existing functionality remains unchanged when flags are used independently	2025-09-11 10:34:49 -05: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
Charlie Marsh	5012b4e831	Allow --editable to override editable = false annotations (#15712) ... ## Summary We support `--no-editable` on the CLI, but now that workspace members and path dependencies can be marked as `editable = false`, I think it makes sense for `--editable` to override that.	2025-09-07 14:37:04 -04: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	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	ac5dc9be1f	Add a plain text backend for credential storage (#15588) ... Adds a default plain text storage mechanism to `uv auth`. While we'd prefer to use the system store, the "native" keyring support is experimental still and I don't want to ship an unusable interface. @geofft also suggested that the story for secure credential storage is much weaker on Linux than macOS and Windows and felt this approach would be needed regardless. We'll switch over to using the native keyring by default in the future. On Linux, we can now fallback to a plaintext store the secret store is not configured, which is a nice property. Right now, we store credentials in a TOML file in the uv state directory. I expect to also read from the uv config directory in the future, but we don't need it immediately.	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
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
Charlie Marsh	ac84f5aedc	Move preview features into a dedicated crate (#15482) ... ## Summary This is causing some cyclic dependencies issues for me, because these can be used in virtually _any_ crate (like `uv-install-wheel`), which then means that all of `uv-configuration` becomes a dependency, etc. I think this should be a leaf crate so that we can safely depend on it anywhere.	2025-08-24 09:55:30 -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	35a8dd514e	Import PackageName from uv-normalize (#15439) ... ## Summary This might be unintentional? `PackageName` is re-exported from `uv-pep508`, so some crates import it from there.	2025-08-21 23:15:40 +00:00
Charlie Marsh	91d66e0bd8	Add file-to-CLI overrides for build isolation configuration (#15437) ... ## Summary Like #15395, but `--no-build-isolation`.	2025-08-21 23:54:39 +01: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
Charlie Marsh	330b54b173	Add file-to-CLI overrides for reinstall configuration (#15426) ... ## Summary This is like #15395, but for `--reinstall` and `--reinstall-package`.	2025-08-21 19:03:03 +00:00
Charlie Marsh	e4de538dae	Remove UpgradeSelection struct (#15422) ... ## Summary After #15395, I realized that we didn't actually need a separate struct for this since we now pass it around as an `Option`. (The key change from #15395 is that when combining, we treat the options as a single unit.)	2025-08-21 18:35:07 +00:00
Charlie Marsh	0397595e53	Treat --upgrade-package on the command-line as overriding upgrade = false in configuration (#15395) ... ## Summary Right now, if you put `upgrade = false` in a `uv.toml`, then pass `--upgrade-package numpy` on the CLI, we won't upgrade NumPy. This PR fixes that interaction by ensuring that when we "combine", we look at those arguments holistically (i.e., we bundle `upgrade` and `upgrade-package` into a single struct, which then goes through the `.combine` logic), rather than combining `upgrade` and `upgrade-package` independently. If approved, I then need to add the same thing for `no-build-isolation`, `reinstall`, `no-build`, and `no-binary`.	2025-08-21 16:20:55 +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
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
Charlie Marsh	82d5b6780a	Move --config-settings structs into uv-distribution-types (#15278) ... ## Summary This breaks up a cycle I'm running into in incorporating the build configuration into our cache keys. This is actually a type that ends up in the frontend build system, etc., so I think it makes more sense here anyway (as opposed to `uv-configuration` which tend to be our own user-facing types).	2025-08-14 15:07:47 +01: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
konsti	84d57f2ee9	Ensure symlink warning is shown (#15126) ... Fixes #15115, see also https://github.com/clap-rs/clap/discussions/6092 <img width="1079" height="1030" alt="image" src="https://github.com/user-attachments/assets/05b003a6-9ca0-4f2b-8a74-078aa155ce6d" />	2025-08-07 15:56:59 +02:00
Charlie Marsh	3c1844ca4a	Add support for per-project build-time environment variables (#15095) ... ## Summary E.g., you can now do: ```toml [tool.uv.extra-build-variables] flash-attn = { FLASH_ATTENTION_SKIP_CUDA_BUILD = "TRUE" } ```	2025-08-06 18:01:55 -05:00
konsti	52771476f4	Support UV_NO_EDITABLE where --no-editable is supported (#15107) ... Specifically, support `UV_NO_EDITABLE=1 uv export`. It's now also supported in `uv add`, though it's default there anyway and the env var exists only for completeness. Fixes #15103	2025-08-06 13:06:49 +00:00