Repository navigation
Allow uv's exact dist marker in release verification - #38
Merged
Merged
Conversation
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.
The v0.0.13 Actions recovery confirmed the third dist entry is
dist/.gitignore, a one-byte file created by the build. Local uv output shows the marker byte is*. This change allows only that exact marker (rejecting symlinks or any other contents) while preserving strict validation of exactly one wheel, one sdist, and no other files. Focused tests cover the accepted marker and rejection of unexpected contents.\n\nValidation:.venv/bin/pytest tests/unit/test_distribution_identity.py -q(6 passed), Ruff check/format,git diff --check. This does not change the immutable v0.0.13 tag or its package source.