22 commits

Author	SHA1	Message	Date
konsti	0cee76417f	Bump version to 0.9.18 (#17141) ... It's been a week. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-12-16 13:32:35 +00:00
Zanie Blue	2b5d65e61d	Bump version to 0.9.17 (#17058)	2025-12-09 16:36:00 -06:00
Zanie Blue	a63e5b62e3	Bump version to 0.9.16 (#17008)	2025-12-06 07:52:06 -06:00
Zanie Blue	e7af5838bb	Bump version to 0.9.15 (#16942)	2025-12-02 17:48:28 -06:00
Zsolt Dollenstein	05814f9cd5	Bump version to 0.9.14 (#16909)	2025-12-01 11:52:15 -05:00
Zanie Blue	735b87004c	Bump version to 0.9.13 (#16862)	2025-11-26 15:12:54 +00:00
Zanie Blue	0fb1233363	Bump version to 0.9.12 (#16840)	2025-11-24 23:22:12 +00:00
William Woodruff	7b3199f07c	Collect and upload PEP 740 attestations during uv publish (#16731) ... Co-authored-by: konsti <konstin@mailbox.org>	2025-11-24 16:47:15 -05:00
Zanie Blue	1a6238c835	Disable test_simultaneous_multiple_create_delete_single_thread on Windows (#16834) ... Closes https://github.com/astral-sh/uv/issues/16096	2025-11-24 15:10:34 +00:00
Zanie Blue	1de0cbea94	Use the word "internal" in crate descriptions (#16810) ... ref https://github.com/astral-sh/uv/pull/16809#pullrequestreview-3494007588	2025-11-21 13:22:47 -06:00
Zanie Blue	563438f13d	Fix documentation links for crates (#16801) ... Part of https://github.com/astral-sh/uv/issues/4392 We shouldn't link to PyPI, and dropping the workspace-level documentation link should mean that we get the auto-generated `docs.rs` links.	2025-11-21 10:44:58 -06:00
Zanie Blue	dfe89047bb	Publish to crates.io (#16770)	2025-11-20 21:26:44 +00:00
Ruben Arts	2e180f5c66	Add missing fields to the Cargo package manifests (#16179) ... <!-- 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? --> Hey devs, great tool as always, you're doing amazing work. ## Summary <!-- What's the purpose of the change? What does it do, and why? --> Adds the following fields to the `[package]` table of `Cargo.toml` files where they were missing: ```toml rust-version = { workspace = true } homepage = { workspace = true } documentation = { workspace = true } repository = { workspace = true } authors = { workspace = true } license = { workspace = true } ``` Most crates already had these fields, this just aligns the rest for consistency. This also resolves the warnings from `cargo-deny` when using `uv` crates as dependencies in Pixi. ## Test Plan No tests needed, this only updates metadata.	2025-10-08 12:01:52 +02:00
konsti	cd49e1d11f	Use the windows crate facade consistently (#15737) ... The initial motivation for this change was that we were using both the `windows`, the `window_sys` and the `windows_core` crate in various places. These crates have slightly unconventional versioning scheme where there is a large workspace with the same version in general, but only some crates get breaking releases when a new breaking release happens, the others stay on the previous breaking version. The `windows` crate is a shim for all three of them, with a single version. This simplifies handling the versions. Using `windows` over `windows_sys` has the advantage of a higher level error interface, we now get a `Result` for all windows API calls instead of C-style int-returns and get-last-error calls. This makes the uv-keyring crate more resilient. We keep using the `windows_registry` crate, which provides a higher level interface to windows registry access.	2025-09-09 15:07:14 +00:00
konsti	d9b63dc547	Use workspace dependencies in uv-keyring (#15738) ... It seems that this was during the vendoring of the keyring crate.	2025-09-09 09:05:43 +02: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	2fd2e19ce3	Use thiserror for keyring error type (#15561)	2025-08-28 08:09:11 -05:00
Zanie Blue	17a86d83ca	Ensure we get the last error from Windows on the same thread (#15564) ... Reverts #15552 Closes https://github.com/astral-sh/uv/pull/15562 Closes https://github.com/astral-sh/uv/issues/15558 The `GetLastError` calls must be on the same thread, or we can pull the wrong last error!	2025-08-27 21:42:37 +00:00
konsti	0bde9e4b8f	Read index credentials from env for uv publish (#15545) ... We were previously missing the `index_locations.cache_index_credentials()` call in `uv publish` to load index credentials from the env. See https://github.com/astral-sh/uv/issues/11836#issuecomment-3022735011 Fixes #11836	2025-08-27 11:19:10 -05:00
Zanie Blue	bce30be3a5	Treat a 203 error on credential removal as a missing entry on Windows (#15552) ... Attempting to address the failure at 4900907073	2025-08-27 10:48:12 -05:00
konsti	439395dadf	Fix unused code warning around entry_from_constructor (#15525)	2025-08-26 13:30:46 +02:00
John Mumm	880eb286e8	Add new uv-keyring crate that vendors the keyring-rs crate (#14725) ... This PR is a first step toward support for storing credentials in the system keyring. The `keyring-rs` crate is the best option for system keyring integration, but the latest version (v4) requires either that Linux users have `libdbus` installed or that it is built with `libdbus` vendored in. This is because v4 depends on [dbus-secret-service](https://github.com/open-source-cooperative/dbus-secret-service), which was created as an alternative to [secret-service](https://github.com/open-source-cooperative/secret-service-rs) so that users are not required to use an async runtime. Since uv does use an async runtime, this is not a good tradeoff for uv. This PR: * Vendors `keyring-rs` crate into a new `uv-keyring` workspace crate * Moves to the async `secret-service` crate that does not require clients on Linux to have `libdbus` on their machines. This includes updating `CredentialsAPI` trait (and implementations) to use async methods. * Adds `uv-keyring` tests to `cargo test` jobs. For `cargo test | ubuntu`, this meant setting up secret service and priming gnome-keyring as an earlier step. * Removes iOS code paths * Patches in @oconnor663 's changes from his [`keyring-rs` PR](https://github.com/open-source-cooperative/keyring-rs/pull/261) * Applies many clippy-driven updates	2025-08-15 15:57:56 +02:00