Repository navigation
ci: nightly compatibility matrix (aiohttp latest vs locked) - #57
Merged
Merged
Conversation
Cross-checks the full test suite every day at 05:17 UTC against the cartesian of Python 3.13/3.14 × aiohttp "latest" (as pip resolves it today) × "locked" (as pinned in uv.lock). Reason: the SDK hit aioresponses-vs-aiohttp divergence twice already (the v1.0.3 stream_writer shim). Nightly surfaces the next divergence before users file issues. Everything runs against aioresponses-mocked HTTP; no live API traffic, no credentials. The report-failure job opens or updates a single `nightly-failure`-labelled issue on a scheduled-run failure so we don't get a daily inbox spam. Co-Authored-By: Claude Opus 4.7 <[email protected]> Claude-Session: https://claude.ai/code/session_01RgkYaQACLxezeceA1hrXQs
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
Vierte Welle der HA-Adoptions: Nightly-Compatibility-Matrix für die kritische `aiohttp`/`aioresponses`-Grenzfläche.
Was läuft
Täglich um 05:17 UTC:
Jede Zelle läuft `uv run pytest -ra` auf dem vollen Test-Suite (inkl. Snapshots, Property-Tests, Failure-Paths).
Nach dem matrix-Job: Falls mindestens eine Zelle versagt und der Run per `schedule` ausgelöst wurde, erzeugt der `report-failure`-Job entweder ein neues `nightly-failure`-Issue oder appendet an das bestehende offene. So landet in GitHub keine Issue-Flut, aber die Degradation ist sofort sichtbar.
Wofür das gut ist
SDK ist zweimal auf die `aioresponses`/`aiohttp`-Divergenz gelaufen (v1.0.3-Shim um den `stream_writer`-Fehler). Beide Male erst durch User-Reports entdeckt. Nightly surfaced die nächste Divergenz, bevor jemand ein Issue öffnet.
Keine Secrets, keine Credentials
Alles läuft gegen `aioresponses`-gemockte HTTP. Keine Live-API-Traffic, keine `ONEKOMMAFIVE_*`-Secrets im Workflow. Entspricht der 2026-10-16-Policy.
Test plan
🤖 Generated with Claude Code
https://claude.ai/code/session_01RgkYaQACLxezeceA1hrXQs