Pin the CI uv release and regenerate the lock with it - #522
Merged
Merged
Conversation
The 6.0.0 Versioning job failed at release_lock.py --refresh: setup-uv installed the latest uv (0.12.14), which rewrites two dependency-edge markers in uv.lock on a cold cache, so the post-bump lock differed from the reviewed lock beyond the root version and the refresh failed closed. uv lock --check accepts both spellings, which is why PR checks passed. Pin uv 0.12.14 in every setup-uv step and regenerate uv.lock with that release, so the refresh changes only the root version. Reproduced locally: 0.11.7 keeps the markers, 0.12.14 drops them and is idempotent afterwards; the simulated bump + generate + refresh now passes with a root-only diff. Fixes #521 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
MaxGhenis
marked this pull request as ready for review
September 15, 2026 12:33
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
1 participant
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.
Fixes #521
The 6.0.0 Versioning job (run 34962073254) failed at
python scripts/release_lock.py --refreshwith "Versioning changed the reviewed dependency graph".setup-uv@v8.1.0installs the latest uv (0.12.14, released 2026-09-14). On a cold cache that release rewrites two dependency-edge markers inuv.lock(cffi -> pycparser,pexpect -> ptyprocess), so the post-bump lock differed from the reviewed lock beyond the root version and the strict refresh failed closed.uv lock --checkaccepts either spelling, which is why the PR checks on #515 passed.This pins uv 0.12.14 in every
setup-uvstep (push, PR code, PR docs workflows), regeneratesuv.lockwith that release (the only change is the two marker lines; every version, URL and hash is unchanged), and documents the pin indocs/release-bundles.md.Validation (local, uv 0.12.14 on PATH):
python scripts/release_lock.pypasses on the regenerated lock at 5.3.1.bump_version.py+scripts/bundle.py generate+release_lock.py --refreshpasses; the lock diff is the root version only (5.3.1 -> 6.0.0). Bump reverted before commit.uv lock --refreshwith 0.12.14 on the regenerated lock is a no-op (idempotent); with 0.11.7 the markers reappear, which is what the pin prevents.make lintpasses.Merging this to main triggers the push workflow, whose Versioning job consumes the pending 6.0.0 fragments from #515 and this one.
🤖 Generated with Claude Code