Charlie Marsh 40844048af 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.		2024-11-21 09:35:57 -05:00
..
src	Remove --upgrade, --no-upgrade, and --upgrade-package from uv tool upgrade (#9318)	2024-11-21 09:35:57 -05:00
build.rs	chore(uv): more env var mappings (#8193)	2024-10-15 07:59:03 -04:00
Cargo.toml	chore(uv): more env var mappings (#8193)	2024-10-15 07:59:03 -04:00