ci: pin uv, enforce lockfile, sync it with pyproject#6
Merged
Conversation
The committed uv.lock was out of sync with pyproject.toml: #2 moved the dev dependencies into [dependency-groups], but the lock still recorded them as an optional-dependency extra. Regenerating brings the lock back in line — no dependency versions change. - Regenerate uv.lock so the [dependency-groups] dev set is represented correctly (9 insertions / 6 deletions, no version churn) - Add --locked to `uv sync` so CI fails on future lockfile drift instead of silently re-resolving - Pin uv to 0.11.16 in setup-uv for reproducible resolution Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
What
Three CI-hygiene changes, surfaced while reviewing #2:
uv.lock. It was out of sync withpyproject.toml— feat: restructure as proper Python package with tooling #2 moved the dev dependencies into[dependency-groups], but the lock still recorded them as an optional-dependency extra. Regenerating corrects the representation only; no dependency versions change (9 insertions / 6 deletions).--lockedtouv syncin CI, so future lockfile/pyproject.tomldrift fails the build instead of being silently re-resolved away.0.11.16insetup-uv, so dependency resolution is reproducible across runs.Why
CI runs
uv syncwithout--locked, so the stale lock went unnoticed — uv just re-resolved on the fly. Enforcing the lock makes drift visible; pinning uv keeps resolution deterministic.Verification
Full CI sequence run locally with the pinned uv (0.11.16):
uv sync --locked --only-group dev— passes (lock now consistent)ruff check/ruff format --check/mypystrict — all green🤖 Generated with Claude Code