Repository navigation
Bump pydantic, azure-servicebus and aiolimiter - #445
Conversation
|
Heads-up: even with HA 2026.11 (core already on 7.15.0),
So I'd suggest Why it only started failing now: the check was added in home-assistant/core#181913 (merged 2026-09-14), and the |
|
Interesting. I've updated all manifest.json deps to be a range. aiolimiter does not appear in HA requirements_all.txt (yet), but staying consistent seems reasonable, and it might get added in the future. I don't think requiring HA 2026.11+ makes sense:
|
- Brings in custom-components#440 (ruff 0.16.9) and custom-components#445 (dependency bumps) - requirements*.txt aligned with custom-components#414's merge: pydantic >=2.11.7,<2.15, pytest-homeassistant-custom-component 0.13.373 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Current core dev-branch includes a bump of pydantic, so we need to include this in 0.8.8 @sveinse. @rhammen mentions testing azure-servicebus==7.15.0 in #442 (comment), so that should be ok as well. Aiolimiter appears to barely be updating anything, other than dropping python 3.9.
Hassfest test fails due to "Requirement azure-servicebus==7.15.0 is incompatible with azure-servicebus==7.10.0, which Home Assistant depends on." HA core dev-branch has already updated to 7.15 in home-assistant/core@c44cc4e, so that should stop failing once we hit HA 2026.11.0. Not sure why this test hasn't failed before, since we have been on 7.14 as long as I can remember, and the 7.10-requirement was added in May 🤷