Repository navigation
ci: Check uv lockfile - #4052
Merged
Merged
Conversation
Run uv lock --check in lint CI so pyproject.toml dependency changes fail unless uv.lock is updated in the same PR. This mirrors the existing generated-file checks by catching stale generated state in CI.
Run uv lock in lint CI and fail if it changes uv.lock. Printing the diff makes stale lockfile failures more actionable while still requiring contributors to commit the generated lockfile update themselves.
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.
I tried with just
uv lock --checkfirst but thought it would be more useful to see what would be updated in the lock file in case the local version is out of sync with the remote in an unexpected way