CI Perf Lint

prefer-uv-0-12

Why it matters

uv ships performance work continuously, and the 0.11 and 0.12 lines carried large batches that directly affect CI:

Pinning uv below 0.12 keeps CI on the slower resolver and installer, so dependency resolution and installs take longer than necessary. uv has little compatibility risk between these releases, so there is usually no reason to keep an older pin.

What it flags

The rule reports jobs and repository configuration that resolve to a uv below 0.12:

Version constraints are read as a floor. A lower bound at or above 0.12 is accepted, and an upper bound that cannot reach 0.12 (for example <0.12) is flagged. latest and unpinned uv installs are not flagged because they already resolve to a current release.

Suggested action

Verification

Compare Python dependency resolution and install wall-clock time before and after moving uv to 0.12.x or newer, and confirm the resolved dependency set is unchanged.

Sources