Test against HA 2026.2.3 as well as 2025.12.0 in CI

Add requirements-test-latest.txt pinning the newest published
pytest-homeassistant-custom-component (0.13.316, HA 2026.2.3, Python
3.13) and run the workflow as a matrix over both requirement files. No
DNS-library pin is needed for the newer release. Both environments pass
scripts/check.sh locally, with no HA deprecation warnings logged for
this integration. Remote runner execution is still unverified.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.gitea/workflows/tests.yml

@@ -6,6 +6,11 @@ on:
 jobs:
   tests:
     runs-on: bs-node
+    strategy:
+      fail-fast: false
+      matrix:
+        # Minimum supported HA (hacs.json) and the newest published test fixtures.
+        requirements: [requirements-test.txt, requirements-test-latest.txt]
     steps:
       - uses: https://github.com/actions/checkout@v4
       # uv supplies standalone Python builds for the Debian job container.
@@ -17,7 +22,7 @@ jobs:
       - name: Create Python environment
         run: uv venv --python 3.13 --seed .venv
       - name: Install test dependencies
-        run: uv pip install --python .venv/bin/python -r requirements-test.txt
+        run: uv pip install --python .venv/bin/python -r ${{ matrix.requirements }}
       - name: Run checks
         run: |
           . .venv/bin/activate

requirements-test-latest.txt

@@ -0,0 +1,3 @@
+# Newest published fixtures: Home Assistant 2026.2.3; requires Python 3.13.
+# Update together with the README's tested-versions note.
+pytest-homeassistant-custom-component==0.13.316