Skip to content

stubsabot obsoletion PRs: erroneous assumptions that the latest release is the one that added a py.typed #8754

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
AlexWaygood opened this issue Sep 16, 2022 · 0 comments · Fixed by #8775
Closed

stubsabot obsoletion PRs: erroneous assumptions that the latest release is the one that added a py.typed #8754

AlexWaygood opened this issue Sep 16, 2022 · 0 comments · Fixed by #8775
Labels
project: infrastructure typeshed build, test, documentation, or distribution related

Comments

@AlexWaygood
Copy link
Member

See #8746 (comment).

termcolor releases have been coming thick and fast recently, since maintenance of the package has just been taken over by a new team. There have been two releases in the last week, and stubsabot erroneously assumed that it was the most recent release that added a py.typed when making a PR to mark types-termcolor as obsolete. (In reality, it was the one before that which added the py.typed file).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
project: infrastructure typeshed build, test, documentation, or distribution related
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Link earliest version with py.typed in stubsabot obsoletion PRs AlexWaygood/typeshed
1 participant
@AlexWaygood