Skip to content

chore(deps): Bump uv from 0.9.28 to 0.12.10 - #123762

Merged
oioki merged 1 commit into
masterfrom
chore/bump-uv-0.12.10
Sep 9, 2026
Merged

oioki merged 1 commit into
masterfrom
chore/bump-uv-0.12.10

Conversation

@oioki

@oioki oioki commented Sep 8, 2026

Copy link
Copy Markdown
Member

Bumps our pinned uv from 0.9.28 to 0.12.10 — the nine astral-sh/setup-uv pins across CI, plus the pip install 'uv==...' in self-hosted/Dockerfile.

Why

uv 0.11.25 changed how lockfile markers are written for projects that set tool.uv.environments (which we do): markers that are tautological within the configured environment are omitted, and conditional ones are factored. This was deliberate and is documented in that release under three entries — #19933 "Avoid writing redundant lockfile markers with tool.uv.environments", #19969 "Factor supported environments out of lockfile markers", and #19971 "Simplify dependency markers under parent reachability".

Our uv.lock on master is already in that normalized form, but CI was still pinned to 0.9.28, which writes the old form.

Nothing is broken today: uv does not rewrite a lockfile it considers current, so requirements check passes and uv sync --frozen is unaffected. The problem appears on the next real re-resolve. Against the current lock:

uv 0.9.28   --upgrade-package sentry-sdk -> 495 markers re-added, 1006 lines changed
uv 0.12.10  --upgrade-package sentry-sdk ->   0 markers re-added,    4 lines changed

So the first dependency bump on 0.9.28 reverts the normalization in a ~1000-line diff, requirements check auto-pushes that revert onto the PR, and the next Dependabot PR re-applies it. This ends the loop.

Notes for review

  • No uv.lock change is needed or included. uv lock is a no-op on the current lock under 0.9.28, 0.11.25 and 0.12.10 alike, and it stays at revision = 3 — no lock-format migration.
  • The two pins interoperate, so there's no flag-day: uv 0.9.28 reads a 0.12.10-written lock cleanly (uv export --frozen exits 0 and leaves the file byte-identical). Old checkouts and any straggling pin keep working.
  • self-hosted/Dockerfile installs uv from our internal index, which until recently only carried 0.8.2 and 0.9.28. 0.12.10 has since been published there, and both manylinux_2_28_aarch64 and manylinux_2_17_x86_64 wheels are present — the base image is python:3.13.1-slim-bookworm (glibc 2.36), so both arches install.
  • The setup-uv@884ad927… (v6) action SHA is intentionally left alone; the version is an input, resolved from GitHub releases.
  • The floor for the fix is 0.11.25; 0.12.10 was chosen as current latest, to match what Dependabot's own toolchain already produces.

The main thing worth watching in CI is whether ~15 releases' worth of uv changes affect the other jobs (uv sync --frozen --active, devenv) beyond the lock behavior, which is verified inert above.

🤖 Generated with Claude Code

uv 0.11.25 changed how lockfile markers are written for projects that set
`tool.uv.environments`: markers that are tautological within the configured
environment are now omitted, and conditional ones are factored (PRs #19933,
#19969, #19971). Our `uv.lock` is already written in that normalized form,
but CI was still pinned to 0.9.28, which writes the old form.

Nothing is broken today, because uv does not rewrite a lockfile it considers
current -- `requirements check` passes and `uv sync --frozen` is unaffected.
The problem shows up on the next real re-resolve. Against the current lock:

    uv 0.9.28  --upgrade-package sentry-sdk -> 495 markers re-added, 1006 lines changed
    uv 0.12.10 --upgrade-package sentry-sdk ->   0 markers re-added,    4 lines changed

So the first dependency bump on 0.9.28 would revert the normalization in a
~1000-line diff, which `requirements check` would then auto-push onto that
PR, and the following Dependabot PR would re-apply it. Bumping the pins ends
that loop.

No `uv.lock` change is needed: `uv lock` is a no-op on the current lock under
0.9.28, 0.11.25 and 0.12.10 alike, and the lock stays at `revision = 3`.

The self-hosted Dockerfile installs uv from our internal index, which until
now only carried 0.8.2 and 0.9.28; 0.12.10 has since been published there,
so that pin moves too.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Sep 8, 2026
@oioki
oioki marked this pull request as ready for review September 8, 2026 10:49
@oioki
oioki requested review from a team as code owners September 8, 2026 10:49
@oioki
oioki merged commit 723c3d6 into master Sep 9, 2026
67 checks passed
@oioki
oioki deleted the chore/bump-uv-0.12.10 branch September 9, 2026 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants