Repository navigation
chore(deps): Bump uv from 0.9.28 to 0.12.10 - #123762
Merged
Merged
Conversation
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>
oioki
marked this pull request as ready for review
September 8, 2026 10:49
jan-auer
approved these changes
Sep 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps our pinned
uvfrom 0.9.28 to 0.12.10 — the nineastral-sh/setup-uvpins across CI, plus thepip install 'uv==...'inself-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 withtool.uv.environments", #19969 "Factor supported environments out of lockfile markers", and #19971 "Simplify dependency markers under parent reachability".Our
uv.lockon 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 checkpasses anduv sync --frozenis unaffected. The problem appears on the next real re-resolve. Against the current lock:So the first dependency bump on 0.9.28 reverts the normalization in a ~1000-line diff,
requirements checkauto-pushes that revert onto the PR, and the next Dependabot PR re-applies it. This ends the loop.Notes for review
uv.lockchange is needed or included.uv lockis a no-op on the current lock under 0.9.28, 0.11.25 and 0.12.10 alike, and it stays atrevision = 3— no lock-format migration.uv export --frozenexits 0 and leaves the file byte-identical). Old checkouts and any straggling pin keep working.self-hosted/Dockerfileinstalls 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 bothmanylinux_2_28_aarch64andmanylinux_2_17_x86_64wheels are present — the base image ispython:3.13.1-slim-bookworm(glibc 2.36), so both arches install.setup-uv@884ad927…(v6) action SHA is intentionally left alone; the version is an input, resolved from GitHub releases.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