Pin hatchling to 1.29.0#533
Merged
Merged
Conversation
About an hour ago, a new version of our build system, Hatchling (1.30.0), was released. This sets the metadata-version to 2.5. But that version is not supported by Twine, our PyPI upload system. I haven't researched if there's a better option, but this should deal with the immediate problem. At the least, we should update Hatchling once Twine is able to handle 2.5.
Contributor
Author
|
I forgot to mention in my commit notes: the new version of Hatchling caused our PyTest to start issuing failures in test_setup.py: it would ask Twine to ensure that the built artifacts are as expected. |
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.
About an hour ago, a new version of our build system, Hatchling (1.30.0), was released. This sets the metadata-version to 2.5. But that version is not supported by Twine, our PyPI upload system.
I haven't researched if there's a better option, but this should deal with the immediate problem. At the least, we should update Hatchling once Twine is able to handle 2.5.