Validate built wheel project identity - #203
Draft
zaniebot wants to merge 1 commit into
Draft
Conversation
astral-automations-bot
Bot
force-pushed
the
zb/bughunt200/164-validate-built-wheel-identity
branch
from
July 21, 2026 16:40
bd8fb7e to
f8cd75c
Compare
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.
uv buildcan produce a wheel whose name and version do not match the project's static metadata and still report success. Validate the built wheel before moving it intodist/, so a rejected artifact is not left behind. PreserveUV_SKIP_WHEEL_FILENAME_CHECK=1and local-version compatibility for malformed or nightly wheels (uv#16046); filename/METADATA and sdist/wheel consistency are separate checks.