ci.yml

name: CI

on:
  push:
    # main is included because releases are tagged from it, and release.yml
    # builds the shipped ZIP from that tag. Without main here, the commit that
    # reaches users would be one no job ever ran against.
    branches: ["main", "dev", "feature/**", "fix/**", "hotfix/**"]
    tags-ignore: ["**"]
  pull_request:
    branches: [dev, main]
  # pytest-homeassistant-custom-component is deliberately unpinned, so the
  # suite tracks whatever Home Assistant is current. That means a Home
  # Assistant release can break this integration without anyone touching the
  # repository — the weekly run surfaces it instead of the next contributor.
  schedule:
    - cron: "0 6 * * 1"
  workflow_dispatch:

concurrency:
  group: ci-${{ github.ref }}
  cancel-in-progress: true

permissions:
  contents: read

jobs:
  lint:
    name: Lint & pre-commit
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7

      - uses: actions/setup-python@v7
        with:
          python-version: "3.14"
          cache: pip

      - name: Install dependencies
        run: pip install pre-commit mypy -r requirements.txt

      - name: Cache pre-commit hooks
        uses: actions/cache@v6
        with:
          path: ~/.cache/pre-commit
          key: pre-commit-${{ hashFiles('.pre-commit-config.yaml') }}

      - name: Run pre-commit
        run: pre-commit run --all-files

      - name: Run mypy
        run: mypy custom_components/battery_controller/

  test:
    # Home Assistant's supported Python floor decides which Home Assistant
    # version pip can install. On 3.13 the newest resolvable release is
    # 2026.2.3, because Home Assistant 2026.3 onwards requires Python 3.14.2.
    # Testing only on 3.13 therefore validates against a Home Assistant that
    # is months behind what users run, without saying so anywhere.
    #
    # 3.14 is the version that matters; 3.13 is kept so the older supported
    # Home Assistant line does not silently break.
    name: Test (Python ${{ matrix.python-version }})
    runs-on: ubuntu-latest
    strategy:
      fail-fast: false
      matrix:
        python-version: ["3.14", "3.13"]
    steps:
      - uses: actions/checkout@v7

      - uses: actions/setup-python@v7
        with:
          python-version: ${{ matrix.python-version }}
          cache: pip

      - name: Install dependencies
        run: pip install -r requirements.txt

      # Which Home Assistant a green run actually proves compatibility with is
      # otherwise invisible, since the dependency is unpinned by design.
      - name: Report the resolved Home Assistant version
        run: |
          HA_VERSION=$(pip show homeassistant | awk '/^Version:/ {print $2}')
          echo "Python ${{ matrix.python-version }} resolved Home Assistant $HA_VERSION"
          {
            echo "### Environment"
            echo ""
            echo "Python \`${{ matrix.python-version }}\` → Home Assistant \`$HA_VERSION\`"
          } >> "$GITHUB_STEP_SUMMARY"

      - name: Run pytest
        run: pytest --cov=custom_components --cov-report=xml -q

      # setup.cfg gates the build at 90%, but the number itself appeared
      # nowhere on the pull request — so a run could sit just above the floor,
      # or drift down towards it, with nothing to notice. always() matters
      # here: the figure is most interesting on the run that just failed the
      # gate.
      - name: Summarise coverage
        if: always()
        run: |
          python - <<'PY' >> "$GITHUB_STEP_SUMMARY"
          import xml.etree.ElementTree as ET
          from pathlib import Path

          print("### Coverage\n")

          report = Path("coverage.xml")
          if not report.is_file():
              print("No `coverage.xml` was produced — pytest did not get that far.")
              raise SystemExit

          root = ET.parse(report).getroot()
          total = float(root.get("line-rate", 0)) * 100
          floor = 90.0
          mark = "✅" if total >= floor else "❌"
          print(f"{mark} **{total:.1f}%** overall (floor {floor:.0f}%)\n")

          files = sorted(
              (
                  (float(c.get("line-rate", 0)) * 100, c.get("filename", "?"))
                  for c in root.iter("class")
              ),
          )
          weakest = [f for f in files if f[0] < 95.0][:5]
          if weakest:
              print("Least covered files:\n")
              print("| File | Coverage |")
              print("| --- | ---: |")
              for rate, name in weakest:
                  print(f"| `{name}` | {rate:.1f}% |")
          PY

      - name: Upload coverage
        uses: codecov/codecov-action@v7
        with:
          files: ./coverage.xml
          fail_ci_if_error: false

  hacs:
    name: HACS validation
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7

      - uses: hacs/action@main
        with:
          category: integration

  js-test:
    name: Test (JS analyzer)
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7

      - uses: actions/setup-node@v7
        with:
          # Node 20 left maintenance in April 2026, so the analyzer tests were
          # running on an unsupported runtime. 22 is the current LTS.
          node-version: "22"
          cache: npm

      - name: Install dependencies
        run: npm ci

      - name: Run Jest
        run: npm test

      # Separate from the Jest run on purpose: jest's vm context costs ~16x on
      # this hot numeric loop, so a benchmark inside it would measure jest
      # rather than the DP.
      - name: Check DP runtime
        run: |
          # pipefail so the guard's exit code survives the tee; bash -e alone
          # would report the exit status of tee instead.
          set -o pipefail
          npm run test:perf | tee perf-output.txt

      # The benchmark prints its median on every run, but inside a job log that
      # only gets read when something already failed. Surfacing it here makes a
      # drift towards the ceiling visible while the check is still passing.
      - name: Summarise DP runtime
        if: always()
        run: |
          {
            echo "### Analyzer DP runtime"
            echo ""
            if grep -q '^DP runtime:' perf-output.txt 2>/dev/null; then
              sed -n 's/^DP runtime: //p' perf-output.txt
            else
              echo "The benchmark produced no timing — it failed before measuring."
            fi
          } >> "$GITHUB_STEP_SUMMARY"

  hassfest:
    name: Home Assistant hassfest
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7

      - uses: home-assistant/actions/hassfest@master