Skip to content

ci: let the test harness drive the Home Assistant core version #95

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
deviantintegral merged 1 commit into from
Jun 9, 2026
Merged

ci: let the test harness drive the Home Assistant core version #95

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
37 changes: 32 additions & 5 deletions script/setup/bootstrap
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,14 +131,44 @@ else
log_info "No runtime dependencies defined (this is normal for blueprints)"
fi

HA_VERSION="${HA_VERSION:-$(grep '"homeassistant"' hacs.json | head -1 | sed 's/.*"homeassistant"\s*:\s*"\([^"]*\)".*/\1/')}"
# Determine which Home Assistant core version to target for the environment.
#
# By default we let the test harness drive it. Each
# pytest-homeassistant-custom-component release (pinned in requirements_test.txt
# and installed above) is locked to one exact Home Assistant version, and its
# fixtures call core internals that must match that version. So we read the
# version the harness just pulled in rather than pinning our own.
#
# hacs.json's "homeassistant" is a *minimum* supported version, not an exact
# pin. Installing it as an exact version here previously downgraded core out
# from under a newer harness, breaking the test run.
#
# Set HA_VERSION explicitly to override (e.g. to target a specific core version
# in a matrix build); the installed harness must be compatible with it.
if [[ -n "${HA_VERSION:-}" ]]; then
PIN_HA_CORE=true
log_info "Targeting explicitly requested Home Assistant ${HA_VERSION}"
else
PIN_HA_CORE=false
HA_VERSION="$(python -c 'from homeassistant.const import __version__; print(__version__)' 2>/dev/null || true)"
if [[ -n "$HA_VERSION" ]]; then
log_info "Targeting Home Assistant ${HA_VERSION} (pulled in by the test harness)"
fi
fi

if [[ -z "$HA_VERSION" ]]; then
log_error "HA_VERSION not set and could not be determined from hacs.json"
log_error "Could not determine the Home Assistant version: no HA_VERSION override set and homeassistant is not installed"
exit 1
fi
HA_CORE_BASE_URL="https://raw.githubusercontent.com/home-assistant/core/${HA_VERSION}"

# Only install core explicitly when an override is requested. Otherwise the
# harness already installed the matching version and re-pinning would downgrade.
if [[ "$PIN_HA_CORE" == true ]]; then
log_header "Installing Home Assistant ${HA_VERSION} core"
uv pip install "homeassistant==${HA_VERSION}"
fi

log_header "Installing Home Assistant ${HA_VERSION} runtime dependencies"
mkdir -p "/tmp/homeassistant"
curl -fsSL "${HA_CORE_BASE_URL}/homeassistant/package_constraints.txt" -o "/tmp/homeassistant/package_constraints.txt" # constraints for requirements files
Expand All @@ -151,9 +181,6 @@ curl -fsSL "${HA_CORE_BASE_URL}/requirements_test_pre_commit.txt" -o "/tmp/requi
curl -fsSL "${HA_CORE_BASE_URL}/requirements_test.txt" -o "/tmp/requirements_test.txt"
uv pip install --requirement "/tmp/requirements_test.txt"

log_header "Installing Home Assistant ${HA_VERSION} core"
uv pip install "homeassistant==${HA_VERSION}"

set +e
rm -rf /tmp/requirements*.txt /tmp/homeassistant/ || log_warning "Failed to clean up temporary files"
set -e
Expand Down