Respect resolved Git SHAs in uv lock
#3956
Merged
Conversation
This file contains 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
charliermarsh
added
enhancement
charliermarsh
force-pushed
the
charlie/git-lock
branch
from
732e212
to
feec984
Compare
charliermarsh
force-pushed
the
charlie/git-lock
branch
from
feec984
to
bf529c1
Compare
CodSpeed Performance ReportMerging #3956 will improve performances by 6.27%Comparing Summary
Benchmarks breakdown
|
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.
Summary
This PR ensures that if a lockfile already contains a resolved reference (e.g., you locked with
mainpreviously, and it locked to a specific commit), and you runuv lock, we use the same SHA, even if it's not the latest SHA for that tag. This avoids upgrading Git dependencies without--upgrade.Closes #3920.