30e3342049
## Summary The `exclude-newer-package` setting accepts `false` to exempt a specific package from the global `exclude-newer` constraint (via `PackageExcludeNewer::Disabled`), but this isn't documented. This PR adds: - A sentence in both doc comments for `exclude_newer_package` explaining the `false` opt-out - An example showing `false` alongside a date value ## Motivation This came up while adding a 3-day `exclude-newer` quarantine to a project that also uses a private registry without PEP 700 upload-time metadata. The `false` opt-out is exactly the right mechanism, but it took reading the source to discover it. The `false` value is handled by the `PackageExcludeNewer::Disabled` variant and its custom deserializer: https://github.com/astral-sh/uv/blob/main/crates/uv-resolver/src/exclude_newer.rs ## Test plan - Documentation-only change (doc comments in `settings.rs`) - Verified the generated docs render correctly by checking the existing doc generation pipeline uses these comments ## Disclaimer Mismatch found by @alexandrukis, patch created by Claude, reviewed by me. --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>
uv-settings
This crate is an internal component of uv. The Rust API exposed here is unstable and will have frequent breaking changes.
This version (0.0.35) is a component of uv 0.11.2. The source can be found here.
See uv's crate versioning policy for details on versioning.