455 commits

Author	SHA1	Message	Date
samypr100	bf99f0a195	Add support for SSL_CERT_DIR (#16473) ... ## Summary Closes https://github.com/astral-sh/uv/issues/16414 Adds support for the standard [SSL_CERT_DIR](https://docs.openssl.org/3.6/man3/SSL_CTX_load_verify_locations) which has gained recent proper support from [rustls-native-certs](https://github.com/rustls/rustls-native-certs/pull/187) in v0.8.2. In addition, this PR clarifies documentation around `SSL_CERT_FILE` and `SSL_CERT_DIR` when used in combination with `UV_NATIVE_TLS` as mentioned in https://github.com/astral-sh/uv/issues/16412#issuecomment-3434927201 ## Test Plan Manually tested with custom cert chains in multiple directories and loading them via SSL_CERT_DIR. We didn't have tests for `SSL_CERT_FILE` or `SSL_CERT_DIR` environment variables so I added a basic one using our own test-only certificate generation and dummy https server. I also moved some things around for better reuse.	2025-11-16 11:48:31 -06:00
Meitar Reihan	b9826778b9	Support http/https URLs in uv python --python-downloads-json-url (#16542) ... continuation PR based on #14687 --------- Co-authored-by: Geoffrey Thomas <geofft@ldpreload.com> Co-authored-by: Aria Desires <aria.desires@gmail.com>	2025-11-14 17:51:24 -05:00
Meitar Reihan	7f4d8c67a8	Account for python_downloads_json_url on Pre-release Python version warnings (#16737) ... Solves #16711	2025-11-14 15:12:35 -06:00
Zanie Blue	f5ce5b47c8	Add support for --upgrade in uv python install (#16676) ... This allows us to suggest `uv python install --upgrade 3.14` as the canonical way to get the latest patch version of a given Python regardless of whether it is installed already. Currently, you can do `uv python upgrade 3.14` and it will install it, but I'd like to remove that behavior as I find it very surprising.	2025-11-13 09:55:48 -06:00
Mikayla Thompson	88811553e4	pip install --target (and sync) install python if necessary (#16694) ... ## Summary As described in https://github.com/astral-sh/uv/issues/12229, `pip install` with `--target` or `--prefix` seem like they should install the necessary python version if it doesn't exist, but they currently don't. Most minimal reproduction is something like: ``` > uv python uninstall 3.13 ... > uv pip install anyio --target target-dir --python 3.13 error: No interpreter found for Python 3.13 in virtual environments, managed installations, or search path ``` This also fails without `--target`, but a venv is expected in that case, so the with `--target`/`--prefix` is the only version that needs to be fixed. The same mechanism occurs for `uv pip sync` as well. ## Test Plan Added tests for install and sync that failed before fix and now pass. --------- Signed-off-by: Mikayla Thompson <mrt@mikayla.codes>	2025-11-12 15:42:52 -07:00
Zanie Blue	4fac4cb7ed	Bump version to 0.9.9 (#16708)	2025-11-12 18:14:44 +00:00
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
konsti	2428a1664e	Document metadata consistency expectation (#15683) ... An opinionated write-up on why Python packaging needs metadata consistency, and that we need to extend metadata to accommodate ML and scientific users. I didn't add a paragraph related to CUDA or accelerators in general and wheel variants, as this is currently support neither by wheel tags nor by PEP 508 markers, so it's not a strict metadata consistency concern, plus this would get outdated quickly as wheel variants progress.	2025-10-19 14:29:47 +02: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
konsti	d45acaebc8	Fix typo in resolver internal docs (#16232)	2025-10-10 15:46:47 +00:00
samypr100	d5dd43aa18	Missing added_in on new env vars (#16217) ... ## Summary Adds the version for environment variables added in https://github.com/astral-sh/uv/pull/16040 and https://github.com/astral-sh/uv/pull/16125. as these were in-flight before documentation versioning was added. Adds ability to emit a compiler error when added in is missing for improved reporting to the developer. e.g. example for the ones fixed in this PR ```shell error: missing #[attr_added_in("x.y.z")] on `UV_UPLOAD_HTTP_TIMEOUT` note: env vars for an upcoming release should be annotated with `#[attr_added_in("next release")]` --> crates\uv-static\src\env_vars.rs:593:15 | 593 | pub const UV_UPLOAD_HTTP_TIMEOUT: &'static str = "UV_UPLOAD_HTTP_TIMEOUT"; | ^^^^^^^^^^^^^^^^^^^^^^ error: missing #[attr_added_in("x.y.z")] on `UV_WORKING_DIRECTORY` note: env vars for an upcoming release should be annotated with `#[attr_added_in("next release")]` --> crates\uv-static\src\env_vars.rs:1087:15 | 1087 | pub const UV_WORKING_DIRECTORY: &'static str = "UV_WORKING_DIRECTORY"; | ^^^^^^^^^^^^^^^^^^^^ error: could not compile `uv-static` (lib) due to 2 previous errors ```	2025-10-10 08:55:09 -05:00
Andrei Berenda	a58d031157	Add UV_UPLOAD_HTTP_TIMEOUT and respect UV_HTTP_TIMEOUT in uploads (#16040) ... ## Summary - Move parsing `UV_HTTP_TIMEOUT`, `UV_REQUEST_TIMEOUT` and `HTTP_TIMEOUT` to `EnvironmentOptions` - Add new env varialbe `UV_UPLOAD_HTTP_TIMEOUT` Relates https://github.com/astral-sh/uv/issues/14720 ## Test Plan Tests with existing tests	2025-10-09 12:28:30 -05:00
konsti	787d035d5e	Document why uv discards upper bounds on requires-python (#15927) ... We're regularly get questions about this. The DPO thread is the best ressource, but it's also a long read, so I summarized some points for uv's decision. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-10-09 17:15:03 +02:00
samypr100	f81c6b9a62	document uv version for environment variables (#15196) ... ## Summary As new environment variables get introduced (e.g. `UV_EDITABLE`) I thought it would useful to start tracking which release they were introduced. I think its a common workflow to navigate to the [env var documentation](https://docs.astral.sh/uv/reference/environment) to know what the env var for something is but then end up in a situation where one is using an environment variable with the wrong version of uv and not notice immediately that its not compatible and therefore ignored. ## Test Plan Existing tests. The versions in `since` have all been manually reviewed to the best of my ability for correctness.	2025-10-08 12:31:12 -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
Aria Desires	b06f02f13d	Fix typo in _CONDA_ROOT docs (#16114) ... All other references are correct, just slipped through in the actual docs.	2025-10-03 10:38:00 -05:00
Charlie Marsh	7d9ea797b0	Add UV_SKIP_WHEEL_FILENAME_CHECK to allow installing invalid wheels (#16046) ... ## Summary This PR adds a user setting to allow (in rare cases) accepting wheels with mismatched filenames and internal metadata. Closes https://github.com/astral-sh/uv/issues/8082. Closes https://github.com/astral-sh/uv/issues/15647.	2025-09-29 19:54:25 -04:00
konsti	fd908aa439	Windows arm64 and Linux RISC-V64 are Tier 2 supported (#16027) ... Windows arm64 and Linux RISC-V64 are supported. Windows arm64 is special because you can also use the x86_64 stack, which may even be a better experience.	2025-09-29 17:54:04 +02: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
konsti	537d1333bd	Document why we ban URLs from index dependencies (#15929) ... Document why we ban URLs from index dependencies, and also what the lookahead resolver does.	2025-09-25 12:18:10 +02:00
Charlie Marsh	7f7fac812c	Add S3 request signing (#15925) ... ## Summary This PR enables users to mark a URL as an S3 endpoint, at which point uv will sign requests to that URL by detecting credentials from the standard AWS environment variables, configuration files, etc. Signing is handled by the [reqsign](https://docs.rs/reqsign/latest/reqsign/) crate, which we can also use in the future to sign requests for other providers.	2025-09-22 23:59:52 +00: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
Zanie Blue	d805d4a370	Use _CONDA_ROOT to detect conda base environments (#15680) ... While investigating https://github.com/astral-sh/uv/pull/15679, I noticed this variable was available in the environment and seems like a nice additional heuristic.	2025-09-17 11:17:06 +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
Charlie Marsh	b770639c91	Rename provides_extras to provides_extra (#15825) ... ## Summary This is now consistent with `requires_dist` (singular).	2025-09-14 13:27:45 +00:00
Charlie Marsh	bd8a9348bd	Document NO_PROXY support (#15816) ... Closes https://github.com/astral-sh/uv/issues/15785.	2025-09-12 13:11:05 -04: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