feat: add support for Python metadata version 2.5 - #83
Merged
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
glin
approved these changes
Aug 12, 2026
glin
left a comment
Member
There was a problem hiding this comment.
👍, once this gets into PPM do you think we need a NEWS item? I remember last time we bumped to 2.4, it was because of some python builder bug.
Contributor
Author
|
@glin When we updated PPM to v0.7.0, there was a metadata version change and a breaking change - the |
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.
Summary
internal/distributions/Fixes CI failure in https://github.com/rstudio/python-distribution-parser/actions/runs/31545855913/job/93958054499?pr=81 where hatch wheels with metadata version 2.5 failed to parse.
Test plan
go build ./...passesgo test ./internal/distributions/passes with new unit tests