Exclude skipped tar-wheel entries from RECORD healing - #228
Closed
zaniebot wants to merge 1 commit into
Closed
Conversation
Collaborator
|
This title needs to be more specific |
zanieb
marked this pull request as ready for review
July 15, 2026 15:28
zaniebot
changed the title
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
2 participants
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.
A
.whl.tar.zstmember is recorded before traversal containment is enforced, so a skipped../member can surviveRECORDhealing and cause uninstall to remove an unrelated environment executable. Collect only members that were successfully unpacked.This overlaps the tar-wheel extraction work in #19979.
Promoted upstream: astral-sh/uv#20429.