Skip to content

Bump homeassistant to 2026.2.0 for pycares 5 compatibility #504

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

Merged
GuyKh merged 1 commit into from
Aug 10, 2026
Merged

Bump homeassistant to 2026.2.0 for pycares 5 compatibility #504

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,11 @@
colorlog>=6.12.0
homeassistant==2025.10.2
# pycares 5.0 removed the ares_query_* result classes that aiodns 3.5.0 (pinned
# by homeassistant 2025.10.2) still references at import time. Pin <5.0 to keep
# the aiodns import chain working.
pycares>=4.9.0,<5.0.0
homeassistant==2026.2.0
# homeassistant 2026.2.0 is the first release that pins aiodns >= 4.0.0 (via
# aiodns==4.0.0). aiodns < 4.0 references the ares_query_* result classes that
# pycares 5.0 removed at import time, crashing `import aiohttp` (homeassistant's
# DNS resolver only catches ImportError). aiodns 4.x drops that annotation, so
# pycares 5.x works once HA is >= 2026.2.0.
pycares>=5.0.1,<5.1.0
iec-api==0.5.15
mypy==2.3.0
pip>=26.2
Expand Down
Loading