Bump test/CI dependency to Home Assistant 2026.7.4 - #12
Merged
Conversation
Was pinned to 2024.1.0 (2.5+ years stale), which is why the recent hass.components.persistent_notification crash wasn't caught by CI: that deprecated accessor still worked on the old pinned version. - requirements-dev.txt: homeassistant 2024.1.0 -> 2026.7.4, mypy 1.8.0 -> 1.15.0 (old mypy can't parse HA's newer syntax) - CI Tests job now runs on Python 3.14 (required by HA >=2026.3) - mypy: skip following into homeassistant.* imports instead of type-checking HA's own source tree against our target Python version (was timing out / erroring on syntax mismatches) - DataUpdateCoordinator now passes config_entry explicitly instead of relying on the deprecated ContextVar lookup; HA 2026.8 turns this into a hard failure for all integrations, so this was about to break regardless of the version bump - manifest.json minimum_version raised to 2024.11.0, the first HA release that accepts config_entry as a DataUpdateCoordinator kwarg Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Our dev/test dependency was pinned to
homeassistant==2024.1.0, over 2.5 years stale. This is why the recenthass.components.persistent_notificationcrash (fixed in #10) wasn't caught by CI — that deprecated accessor still worked fine on the old pinned version, so tests passed locally while it crashed on any HA version real users actually run.requirements-dev.txt:homeassistant2024.1.0 → 2026.7.4 (latest),mypy1.8.0 → 1.15.0 (old mypy can't parse HA's newer source syntax)Testsjob now runs on Python 3.14 (HA 2026.3+ requires it)mypy: addedfollow_imports = "skip"forhomeassistant.*— previously mypy tried to fully parse HA's own source tree, which times out / errors on syntax mismatches as HA's syntax requirements move forward. We don't need HA's types checked, just our own code.DataUpdateCoordinator.__init__now expectsconfig_entrypassed explicitly rather than relying on a deprecated ContextVar lookup. HA 2026.8 turns this into a hard failure for all integrations (not just core ones), so this was going to break regardless — the version bump just surfaced it now instead of after the fact. Fixed by threadingconfig_entrythroughPecronDataUpdateCoordinator.__init__.manifest.jsonminimum_versionraised to2024.11.0, the first HA release that acceptsconfig_entryas aDataUpdateCoordinatorkwarg.Test plan
pytest— all 64 tests pass on HA 2026.7.4 / Python 3.14ruff check/ruff format --checkclean on changed filesmypyruns without timing out or syntax errors (pre-existing, unrelated type errors in files not touched here are unaffected — CI's mypy job is non-blocking anyway)🤖 Generated with Claude Code