Fix default handling in PEP 792 status markers#17671
Merged
Conversation
Signed-off-by: William Woodruff <william@astral.sh>
Member
Author
|
TestPyPI seems to be a little flakey at the moment. |
zsol
approved these changes
Jan 23, 2026
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.
Summary
"project-status": {}is a perfectly valid PEP 792 status response, which just means "default status" (active) and "no reason given." We previously didn't handle that correctly because we didn't tell serde it could use the default impls to fill in missing fields. Now we do.See #17631.
Part of #15254.
Test Plan
Added two testcases for this.