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
..
blocking.rs	Add new uv-keyring crate that vendors the keyring-rs crate (#14725)	2025-08-15 15:57:56 +02:00
credential.rs	Add new uv-keyring crate that vendors the keyring-rs crate (#14725)	2025-08-15 15:57:56 +02:00
error.rs	Use thiserror for keyring error type (#15561)	2025-08-28 08:09:11 -05:00
lib.rs	Remove the native system store from the keyring providers (#15612)	2025-09-02 13:16:52 -05:00
macos.rs	Remove the native system store from the keyring providers (#15612)	2025-09-02 13:16:52 -05:00
mock.rs	Add new uv-keyring crate that vendors the keyring-rs crate (#14725)	2025-08-15 15:57:56 +02:00
secret_service.rs	Remove the native system store from the keyring providers (#15612)	2025-09-02 13:16:52 -05:00
windows.rs	Remove the native system store from the keyring providers (#15612)	2025-09-02 13:16:52 -05:00