astral-sh/uv - CodSpeed

uv

Blog Docs Changelog

Performance History

Latest Results

Handle project conflicts and legacy development groups in lock validation

konsti/regenerate-locked-dependencies

1 hour ago

Preserve empty legacy development groups in frozen locks

konsti/metadata-free-lock-selections

2 hours ago

Ignore Codex runtime files when creating bug tests (#20674) Bug reproduction for astral-sh/uv#20672 created a regression test but could not publish it because `codex-action` modified its tracked configuration and generated runtime state in `agents/codex`. Ignore generated Codex state and restore `agents/codex/config.toml` before checking for unrelated repository changes, preserving the integration-test-only publication guard. Co-authored-by: Zanie Blue <contact@zanie.dev>

main

2 hours ago

Avoid duplicate security review comments (#20673) The security review can repeat a finding after a pull request is rebased because previous inline comments are not included in its context. Collect existing review comments, including comments attached to earlier commits, and instruct the reviewer not to report issues that have already been identified. Enable `pipefail` so a failed comment request cannot silently produce incomplete review context.

main

3 hours ago

Simplify direct lock parsing validation

zsol/direct-lock-parsing

3 hours ago

Support combined upgrade and reinstall in Python install (#20659) ## Summary > Note: Not sure if this is bug or enhancement. Someone help. While perusing the code I noticed this confusing TODO about `uv python install --reinstall`. In #11072 we changed `uv python install --reinstall` to reinstall all existing Python installations except when a specific minor version was passed, in which case we would instead install the latest available patch. This was justified due to having no `--upgrade` at the time. Then in #16676 we introduced `uv python install --upgrade` but we didn't change the `--reinstall` behaviour. So we now had two ways to do this one thing, but no way to re-install only specific versions. This PR completes the deferred change to `--reinstall`. That's the first commit. The second commit restores the behaviour of `--reinstall --upgrade`, which install or reinstalls the latest patch only, not sure if this is a desirable combo, but it _did_ work in the past and I didn't know if it should break too. Without the special case `--reinstall` takes precedence and `--upgrade` is ignored. This change seems breaking. It's currently just dropped right in (maybe 0.12.0?) but I'm also open to putting it behind a preview flag and adding some warnings. ## Test Plan Test adjustments, to match/test the new behaviours.

release/0.12.0

3 hours ago

Fix metadata-free lock validation and frozen selections

konsti/regenerate-locked-dependencies

3 hours ago

Make lock parsing tests independent of snapshot format

zsol/direct-lock-parsing

3 hours ago

Latest Branches

0%

Regenerate locked dependencies#20640

2 hours ago

f4f2dcd

konsti/regenerate-locked-dependencies

0%

Support frozen installs from metadata-free lockfiles#20671

2 hours ago

64e9a5e

konsti/metadata-free-lock-selections

+8%

Parse uv lockfiles directly#20648

3 hours ago

99b5885

zsol/direct-lock-parsing

© 2026 CodSpeed Technology

Home Terms Privacy Docs