fix: verify Windows wheel RECORD paths - #12
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
1 participant
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.
What changed
Normalize Windows backslashes before identifying the native extension in wheel
RECORDverification. Add a regression test using the exactmsgspec_toon\_native.pydform emitted by the Windows wheels.Root cause
The release verifier hashed every installed Windows wheel file successfully, but its native-extension coverage flag only recognized POSIX separators. All four Windows verification jobs therefore failed after successful build and installation.
Validation
uv run --no-sync pytest tests/test_release_artifacts.py -qmake qualifyThis is release-harness-only; it does not change codec behavior or version metadata.