Skip to content

[stubsabot] Mark binaryornot as obsolete since 0.5.0#15494

Merged
srittau merged 1 commit intomainfrom
stubsabot/binaryornot
Mar 8, 2026
Merged

[stubsabot] Mark binaryornot as obsolete since 0.5.0#15494
srittau merged 1 commit intomainfrom
stubsabot/binaryornot

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Mar 8, 2026

@github-actions github-actions bot added the bot: stubsabot 🤖 Third-party stub updates by stubsabot 🤖 label Mar 8, 2026
@AlexWaygood AlexWaygood closed this Mar 8, 2026
@AlexWaygood AlexWaygood reopened this Mar 8, 2026
@srittau srittau merged commit 4905a32 into main Mar 8, 2026
34 checks passed
@srittau srittau deleted the stubsabot/binaryornot branch March 8, 2026 07:41
@brianschubert
Copy link
Collaborator

Funnily enough, the v0.5.0 release doesn't actually contain any type hints. It seems that they added a py.typed file as part of a "cookiecutter" template migration (binaryornot/binaryornot@07055b5), but that migration didn't actually add any type hints.

They did however add type hints in a later commit (binaryornot/binaryornot@26badac), which made it into the v0.6.0 release earlier today. So I don't think there's any action needed on our part.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bot: stubsabot 🤖 Third-party stub updates by stubsabot 🤖

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants