Files
Mike DegatanoandClaude Opus 5.5 ae1fa5cd89 Check recorded API responses against aiohasupervisor in CI (#7378)
* Check recorded API responses against aiohasupervisor in CI

Record API responses in the pytest job and check them with the
aiohasupervisor compat checker for the client versions pinned by Home
Assistant Core stable, beta and dev, plus the latest client release and
client main. Each version is checked once, by the first target using it.
Client main is informational and does not fail the workflow.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

* Resolve aiohasupervisor versions once for all compat targets

Each matrix job resolved its own versions, so a pin or tag changing between
jobs could make a target skip a version another target never checked.
Resolve and de-duplicate all targets in one job and pass the result to the
matrix, keeping resolution errors per target.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

* Check all aiohasupervisor releases of the past year

Replace the Core version resolution with every stable aiohasupervisor
release published in the past year. A gate job with a fixed name
aggregates the per-release jobs so it can be required without updating
branch protection on each release. Client main is checked separately
and does not block.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

* Blocklist aiohasupervisor 0.7.0 and always check the newest release

Block 0.7.0, its known incompatibilities are fixed in 0.8.0. Each
blocked release carries its reason, which is shown in the skip notice.
Always include the newest release since client releases can be more
than a year apart. Restrict GITHUB_TOKEN to read access for the whole
workflow.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

---------

Co-authored-by: Claude Opus 5.5 <[email protected]>
2026-10-21 09:45:30 +02:00
..
…