Repository navigation
Extract file hashing into RegistryClient - #21752
Merged
Merged
Conversation
charliermarsh
temporarily deployed
to
automations
September 16, 2026 15:25 — with 
GitHub Actions
Inactive
RegistryClient
This branch was previously deployed
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.
Move the file-hashing helper from pylock export into
RegistryClient, so we can compute SHA-256 hashes for local files and remote URLs without extracting them. Reuse it for the existing pylock export path and remove the dependencies that are no longer needed byuv-lock.Prefactor for #21651. This does not include the libc-specific caller.