feat(step): add "uv python" step#1122
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
|
|
||
| debug!("Found latest version: {latest:?}"); | ||
|
|
||
| // TODO: support multiple versions. Install new patch releases for each? Optionally install new minor release? |
Check notice
Code scanning / devskim
A "TODO" or similar was left in source code, possibly indicating incomplete functionality Note
|
|
||
| impl UvPythonVersionData { | ||
| /// Returns `None` when the version is undesirable, that is when any of the following conditions is met: | ||
| /// - It's a pre-release (we don't care about pre-releases) (TODO: add an option to care about pre-releases) |
Check notice
Code scanning / devskim
A "TODO" or similar was left in source code, possibly indicating incomplete functionality Note
|
There are plans to add something similar within |
|
I realized that |
That aged badly... Astral is way quicker with this stuff than I anticipated 😂 I'll revisit this soon, to add |
From PR topgrade-rs#1122. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Fix unclosed delimiter in config.rs (missing closing brace for plasmoids_get_excluded) - Resolve PR topgrade-rs#1122 merge conflict: keep both HEAD fields (doom, cargo, rustup, pkgfile) and add uv_python - Remove duplicate serde_json entry in Cargo.toml - Remove unused get_require_sudo_string import from generic.rs Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 participant
What does this PR do
Adds a disabled-by-default "uv python" step, that checks for new available versions and installs them automatically.
Is this acceptable?
Standards checklist
CONTRIBUTING.mdFor new steps
--dry-runoption works with this step--yesoption works with this step if it is supported bythe underlying command