uv

a502464f - Retain the cache lock and temporary caches during `uv run` and `uvx` (#15990)

Retain the cache lock and temporary caches during `uv run` and `uvx` (#15990) We're seeing reports of a regression from https://github.com/astral-sh/uv/pull/15888 where `--no-cache` causes `uv run` and `uvx` to fail to spawn a command. The intent of this code was to allow destructive cache operations _after_ we'd finished setting up the environment. However, it's unclear to me that it's safe to run `uv cache clean` during a `uv run` operation (e.g., `uv run --script` uses an environment in the cache) and, more importantly, we cannot drop non-persistent caches (e.g., from `--no-cache`) as they include the environment we're spawning the command in. Alternative to #15977 which retains release of the lock — we may want to consider that approach still but this regression needs to be resolved quickly. Closes https://github.com/astral-sh/uv/issues/15989 Closes https://github.com/astral-sh/uv/issues/15987 Closes https://github.com/astral-sh/uv/issues/15967