…#17660)

Stabilize `uv add --bounds` and the `add-bounds` configuration option.

There's not many usages of the features, but there also aren't any
problem reports, and I don't expect its functionality to change unless
there were bigger `uv add` and/or argument/configuration handling
changes.

* https://github.com/search?q=path%3A**%2F*.toml%20add-bounds&type=code
* https://grep.app/search?regexp=true&q=uv+add.*--bounds
* https://github.com/search?q=%22uv+add%22+%22--bounds%22&type=code&p=1

Not breaking, but queuing up for 0.10 since it fits nicely with that
release.

This is a copy of #16520 on #17661

Co-authored-by: samypr100 <[email protected]>

…of `python` (#17756)

Copy of #14201 for
#17661

Co-authored-by: Frazer McLean <[email protected]>

…cy_group` (#17761)

Closes #17368

Co-authored-by: Claude <[email protected]>

Same as #17756 for pyodide

Since you cannot reference these indexes, I don't think we need a
warning and deprecation period.

Co-authored-by: Claude <[email protected]>

This has been in warnings since 0.8

…all` (#14112)

Closes #12921

For `uv tool run`, we'll just use the global Python version for all
invocations without an explicit alternative request (i.e., via the
`--python` flag).

For `uv tool install`, it's a bit more complicated:

- If the tool is not installed, we'll use the global Python version
- If the tool is already installed, we won't change the Python version
unless `--reinstall` or `--python` is used
- If the tool was installed with `--python`, we won't use the global
Python version, unless the tool is uninstalled first

The behavior can be demonstrated as follows

```
$ uv python pin --global 3.12
$ uv tool install flask  # uses 3.12
$ uv tool install flask  # no-op
$ uv python pin --global 3.13
$ uv tool install flask  # no-op
$ uv tool install flask --reinstall  # uses 3.13
$ uv tool install flask -p 3.12 # uses 3.12
$ uv tool install flask  # no-op
$ uv tool install flask --reinstall # uses 3.12
```

This is a little more complicated than always reinstalling when the
global Python version pin changes, but I think it's probably more
intuitive when actually using the tool. We briefly touched on this when
adding global version pins at
#12115 (comment)

Minor note: I need to do a self-review of this implementation, as it's a
little awkward to encode this behavior in the existing logic.

…n arbitrary one (#16983)

This PR makes `TextCredentialStore.get_credentials` fail on ambiguous
matches, instead of returning the first "best" match while iterating
over all credentials.

Added a unit test, plus tested via:

```
❯ jq -n '{uri: "https://foo"}' | cargo -q run auth helper --protocol=bazel get
error: Multiple credentials found for URL 'https://foo/', specify which username to use
```
(the above needed two username/password combos registered for
`https://foo` using `uv auth login https://foo`)

#17721)

I think if you switch to a different exclude newer time we should only
change package versions if they're no longer within the range.
Otherwise, changing your exclude-newer settings can cause a bunch of
package upgrades without recourse.

I'll roll this into 0.10 even though it isn't breaking for "users".

---------

Co-authored-by: Claude <[email protected]>

Includes a few things...

- Drops preview warnings for use of `uv python upgrade` and `uv python
install --upgrade`
- Adds `--resolve-links` to `uv python find`, which I needed in test
cases to retain existing snapshots
- Fixes issues in our "Using environment ..." messages on Windows which
were incorrect
- Refactors `from_executable` for the `PythonMinorVersionLink` type
(28b2ed2)
to use the type system to prevent incorrect construction (for above)
- Removes special casing where we only upgrade links if they already
exist, which existed so preview wasn't needed on every invocation
- Fixes a bug with `PythonMinorVersionLink::exists` which returned
`true` even if the link pointed to the wrong Python installation leading
to discovery failures