mirror of
https://github.com/astral-sh/uv
synced 2026-01-10 08:03:23 -05:00
Remove --upgrade, --no-upgrade, and --upgrade-package from uv tool upgrade (#9318)
## Summary `--upgrade` isn't useful, since it's the default. So it's now hidden, but continues to warn if you enable it. `--no-upgrade` isn't useful, since it panics. So it's now removed entirely. This isn't breaking, since it already didn't work. `--upgrade-package` actually _is_ useful, because it turns out it allows things like: `uv tool upgrade babel --upgrade-package "babel<0.2.14"` to constrain the upgrade. I left this in place but hid it... I think we should provide a better workflow for this, like `uv tool upgrade "babel<0.2.14"`? It's strange to specify the package twice, and that `uv tool upgrade` has an `--upgrade-package` flag. Closes https://github.com/astral-sh/uv/issues/9317.
This commit is contained in:
@@ -3741,10 +3741,6 @@ uv tool upgrade [OPTIONS] <NAME>...
|
||||
|
||||
<li><code>lowest-direct</code>: Resolve the lowest compatible version of any direct dependencies, and the highest compatible version of any transitive dependencies</li>
|
||||
</ul>
|
||||
</dd><dt><code>--upgrade</code>, <code>-U</code></dt><dd><p>Allow package upgrades, ignoring pinned versions in any existing output file. Implies <code>--refresh</code></p>
|
||||
|
||||
</dd><dt><code>--upgrade-package</code>, <code>-P</code> <i>upgrade-package</i></dt><dd><p>Allow upgrades for a specific package, ignoring pinned versions in any existing output file. Implies <code>--refresh-package</code></p>
|
||||
|
||||
</dd><dt><code>--verbose</code>, <code>-v</code></dt><dd><p>Use verbose output.</p>
|
||||
|
||||
<p>You can configure fine-grained logging using the <code>RUST_LOG</code> environment variable. (<https://docs.rs/tracing-subscriber/latest/tracing_subscriber/filter/struct.EnvFilter.html#directives>)</p>
|
||||
|
||||
Reference in New Issue
Block a user