Fix Python setup in CI
Tests / tests (push) Successful in 1m10s

This commit is contained in:
buzera committed 2026-10-26 20:13:15 +02:00
1 parent 9ed62885b7
commit 43f30dab2b
3 files changed
+28 -6

No files matched your search

+11
View File
@@ -124,3 +124,14 @@ Remote runner execution, a modern-HA version matrix, dedicated lint/type checks,
full process restart, partial platform failure and real disk-failure testing remain
open. The test harness needed a pycares 4.11.0 pin for compatibility with HA's DNS
dependency. Integration runtime dependencies and behavior are unchanged.
## CI provisioning correction
Remote CI reached checkout on the dedicated `bs-node` runner but failed at
setup-python: no Python 3.13 x64 build matched the Debian Bookworm job OS. No tests
ran in that job. The workflow now uses setup-uv v6 with uv 0.9.6 to create a seeded
Python 3.13 virtual environment, then runs the same dependency and test checks.
GitHub cache services are disabled and no Gitea token is supplied to setup-uv.
The runner label and integration runtime are unchanged. Remote execution of the
corrected workflow remains to be verified.