Preparing release 1.3.0 #435
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
nicoddemus
approved these changes
Aug 26, 2023
Member
Author
|
Pluggy 1.3.0 is released, thanks for the reviews as always @nicoddemus. |
Member
|
Awesome, thanks for taking care of the release! 👍 |
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.
Notes:
pytest: Fixes for typed pluggy pytest#11353
tox: has a few new "useless type ignore" warnings, expected
devpi: has a new mypy error due to using
warn_on_impl="a string"instead ofwarn_on_impl=Warning("a warning"). I'm not really sure if the string one even works, but in any case I think it's better to let devpi change toWarninghere instead of adding support for str.The rest seem good.