ci: let the test harness drive the Home Assistant core version#95
Merged
Conversation
The bootstrap script derived the Home Assistant core version from hacs.json's "homeassistant" field and installed it as an exact pin (homeassistant==<version>). That field is a *minimum* supported version, not an exact pin. pytest-homeassistant-custom-component locks each release to one exact Home Assistant version and its fixtures call core internals that must match it. When Renovate bumped phacc, it pulled in the matching newer core, but bootstrap then downgraded core back to the hacs.json minimum, leaving the newer harness running against an older core (e.g. device_registry.async_setup, added in 2026.4.0, missing on 2026.3.0). The test run failed in fixture setup before any of our code ran. Read the version the harness already installed instead of re-pinning, and only install core explicitly when HA_VERSION is set as an override (e.g. for matrix builds). This keeps the harness and core in sync and removes this whole class of Renovate test failure. https://claude.ai/code/session_01XsZWJtA1Q1wW2C84VTsoQg
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
2 participants
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.
The bootstrap script derived the Home Assistant core version from
hacs.json's "homeassistant" field and installed it as an exact pin
(homeassistant==). That field is a minimum supported version,
not an exact pin.
pytest-homeassistant-custom-component locks each release to one exact
Home Assistant version and its fixtures call core internals that must
match it. When Renovate bumped phacc, it pulled in the matching newer
core, but bootstrap then downgraded core back to the hacs.json minimum,
leaving the newer harness running against an older core
(e.g. device_registry.async_setup, added in 2026.4.0, missing on
2026.3.0). The test run failed in fixture setup before any of our code
ran.
Read the version the harness already installed instead of re-pinning,
and only install core explicitly when HA_VERSION is set as an override
(e.g. for matrix builds). This keeps the harness and core in sync and
removes this whole class of Renovate test failure.
https://claude.ai/code/session_01XsZWJtA1Q1wW2C84VTsoQg