Initial commit

.github/workflows/canary.yml

@@ -0,0 +1,45 @@
+name: Command-class catalogue canary
+
+# Monthly canary, like the Matter and ESPHome integrations'.
+#
+# PURPOSE: catch zwave-js / zwave-js-server / zwave-js-server-python changes this integration does not support yet.
+# Each run installs their LATEST releases (not the locked ones) and runs the whole suite, whose catalogue
+# (tests/test_catalogue.py) hosts one mock device per command class. It goes RED when upstream ships something
+# unsupported: a new command class, value metadata type or unit (the fast checks), or a new or changed value of a
+# hosted command class (the sweep). That is the signal to add support, or to explain why not.
+
+on:
+  schedule:
+    - cron: "0 4 1 * *" # monthly
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  canary:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: "22"
+
+      - name: Install the project
+        run: (command -v poetry || pipx install poetry) && poetry install
+
+      - name: Upgrade to the latest zwave-js, zwave-js-server and zwave-js-server-python
+        run: |
+          npm ci --prefix tests/mock --no-audit --no-fund
+          npm install --prefix tests/mock --no-save --no-audit --no-fund zwave-js@latest @zwave-js/server@latest
+          poetry run pip install --upgrade zwave-js-server-python
+          npm ls --prefix tests/mock zwave-js @zwave-js/server
+          poetry run pip show zwave-js-server-python | head -2
+
+      - name: Whole suite, catalogue included
+        run: poetry run pytest -v

.github/workflows/release.yml

@@ -0,0 +1,38 @@
+name: Release
+
+on:
+  workflow_dispatch:
+
+permissions:
+  contents: write
+  id-token: write
+
+jobs:
+  release:
+    uses: ParkerIndustries/workflows/.github/workflows/release.yml@v1
+    with:
+      pypi-package-name: majordom-zwave
+      python-version: "3.12"
+      stable-branch: master
+      # the QA run needs the mock Z-Wave network: see test.yml
+      setup-script: npm ci --prefix tests/mock --no-audit --no-fund
+
+  # PyPI publish runs HERE, in the caller — Trusted Publishing can't match a reusable workflow.
+  publish-pypi:
+    name: Publish to PyPI
+    needs: release
+    runs-on: ubuntu-latest
+    environment:
+      name: release
+      url: https://pypi.org/p/majordom-zwave
+    permissions:
+      id-token: write
+    steps:
+      - name: Download distributions
+        uses: actions/download-artifact@v8
+        with:
+          pattern: dist-*
+          merge-multiple: true
+          path: dist/
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

.github/workflows/test.yml

@@ -2,55 +2,16 @@ name: QA & Tests
 
 on:
   push:
-    # Long-lived branches — keep whichever your repo uses (main or master) and develop.
     branches:
-      - main
       - master
       - develop
   pull_request:
   workflow_dispatch:
 
 jobs:
-  # Real integrations created from this template (any repo other than the template itself)
-  # run the full shared QA suite, including tests/test_controller.py — which stays red until
-  # the controller is implemented.
   test:
-    if: github.repository != 'MajorDom-Systems/integration-template'
     uses: ParkerIndustries/workflows/.github/workflows/test.yml@v1
-    # Defaults to the team matrix ["3.12", "3.13"]. Uncomment to customize:
-    # with:
-    #   python-versions: '["3.12", "3.13", "3.14"]'
-    #   # Runs after `poetry install`, before checks (system deps, Cython build_ext, ...):
-    #   setup-script: |
-    #     sudo apt-get update && sudo apt-get install -y espeak-ng
-    #   # Teardown, always runs after checks:
-    #   post-run-script: docker compose down
-
-  # ─────────────────────────────────────────────────────────────────────────────
-  # TEMPLATE-ONLY — delete this whole job AND the `if:` line on `test` above when you
-  # scaffold a real integration.
-  #
-  # tests/test_controller.py is prefilled to FAIL until the controller is implemented (no
-  # skip markers in the code or pytest config — deliberate, so a real integration's CI is
-  # red until it works). On the template repo itself we run everything *except* that file so
-  # the template stays green. This exclusion lives only here, only for the template's repo.
-  template-selfcheck:
-    if: github.repository == 'MajorDom-Systems/integration-template'
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v7
-      - name: Install poetry
-        run: pipx install poetry
-      - uses: actions/setup-python@v7
-        with:
-          python-version: "3.12"
-          # No `cache: poetry` — the template gitignores poetry.lock, so there's nothing to key on.
-      - name: Install dependencies
-        run: poetry install
-      - name: Lint & type-check (full tree, including the skeleton tests)
-        run: |
-          poetry run ruff check .
-          poetry run ruff format --check .
-          poetry run ty check
-      - name: Tests (excluding the prefilled, expected-to-fail controller suite)
-        run: poetry run pytest --ignore=tests/test_controller.py
+    with:
+      # The end-to-end tests run against a mock Z-Wave network (zwave-js's mock controller behind a real
+      # zwave-js-server, tests/mock): install it. Node.js comes with the runner.
+      setup-script: npm ci --prefix tests/mock --no-audit --no-fund

.gitignore

@@ -51,3 +51,4 @@ venv/
 # OS
 .DS_Store
 Thumbs.db
+node_modules/