CI: run unit + extension integration suite on Linux, macOS, and Windows

Matrix both jobs across ubuntu/macos/windows. The integration job picks the
matching haybarn_unittest asset per platform; on Windows the bash steps run
under Git Bash and the worker LOCATION is the native path to the
.venv/Scripts/vgi-easter.exe launcher.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: rustyconover

.github/workflows/ci.yml

@@ -2,7 +2,8 @@
 #
 # Unit tests + the sqllogictest extension suite (test/sql/*.test) run against
 # the easter worker through the real signed `vgi` DuckDB community extension via
-# a prebuilt standalone `haybarn-unittest`. See ci/README.md for the design.
+# a prebuilt standalone `haybarn-unittest`. Both jobs run on Linux, macOS, and
+# Windows. See ci/README.md for the design.
 #
 # Reusable (workflow_call) so publish.yml can gate releases on a green run.
 name: CI
@@ -27,15 +28,30 @@ env:
 
 jobs:
   unit:
-    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest, windows-latest]
+    runs-on: ${{ matrix.os }}
     steps:
       - uses: actions/checkout@v4
       - uses: astral-sh/setup-uv@v6
       - name: Run unit tests
         run: uv run --python 3.13 pytest tests/ -q
 
   integration:
-    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - { os: ubuntu-latest,  asset: haybarn_unittest-linux-amd64.zip }
+          - { os: macos-latest,   asset: haybarn_unittest-osx-arm64.zip }
+          - { os: windows-latest, asset: haybarn_unittest-windows-amd64.zip }
+    runs-on: ${{ matrix.os }}
+    defaults:
+      run:
+        # Git Bash on Windows; the integration runner is a bash script.
+        shell: bash
     steps:
       - uses: actions/checkout@v4
       - uses: astral-sh/setup-uv@v6
@@ -49,17 +65,27 @@ jobs:
         run: |
           gh release download "$HAYBARN_RELEASE" \
             --repo Query-farm-haybarn/haybarn \
-            --pattern 'haybarn_unittest-linux-amd64.zip' \
-            --output /tmp/haybarn-unittest.zip --clobber
-          unzip -o -q /tmp/haybarn-unittest.zip -d /tmp/haybarn-unittest
-          UNITTEST=$(find /tmp/haybarn-unittest -name 'haybarn-unittest' -type f | head -1)
-          chmod +x "$UNITTEST"
-          echo "HAYBARN_UNITTEST=$UNITTEST" >> "$GITHUB_ENV"
+            --pattern '${{ matrix.asset }}' \
+            --output haybarn-unittest.zip --clobber
+          mkdir -p hb && unzip -o -q haybarn-unittest.zip -d hb
         env:
           GH_TOKEN: ${{ github.token }}
 
+      - name: Resolve runner + worker paths
+        run: |
+          # The worker LOCATION is consumed by the (native) extension process,
+          # so on Windows it must be a native path to the .exe launcher; the
+          # unittest binary itself is exec'd by bash, so a POSIX path is fine.
+          if [ "$RUNNER_OS" = "Windows" ]; then
+            UNITTEST=$(find hb -name 'haybarn-unittest.exe' -type f | head -1)
+            WORKER=$(cygpath -w "$PWD/.venv/Scripts/vgi-easter.exe")
+          else
+            UNITTEST=$(find hb -name 'haybarn-unittest' -type f | head -1)
+            chmod +x "$UNITTEST"
+            WORKER="$PWD/.venv/bin/vgi-easter"
+          fi
+          echo "HAYBARN_UNITTEST=$UNITTEST" >> "$GITHUB_ENV"
+          echo "VGI_EASTER_WORKER=$WORKER" >> "$GITHUB_ENV"
+
       - name: Run extension integration suite
         run: ci/run-integration.sh
-        env:
-          HAYBARN_UNITTEST: ${{ env.HAYBARN_UNITTEST }}
-          VGI_EASTER_WORKER: ${{ github.workspace }}/.venv/bin/vgi-easter

ci/README.md

@@ -2,9 +2,15 @@
 
 [`.github/workflows/ci.yml`](../.github/workflows/ci.yml) runs the unit tests
 and this repo's sqllogictest suite (`test/sql/*.test`) against the easter VGI
-worker through the **real DuckDB `vgi` extension** on every push / PR — and is
-reused by [`publish.yml`](../.github/workflows/publish.yml) so nothing reaches
-PyPI without a green extension run.
+worker through the **real DuckDB `vgi` extension** on every push / PR — across
+**Linux, macOS, and Windows** — and is reused by
+[`publish.yml`](../.github/workflows/publish.yml) so nothing reaches PyPI
+without a green extension run on all three.
+
+Both jobs run as an OS matrix. The integration job selects the matching
+`haybarn_unittest-*` asset per platform (`linux-amd64`, `osx-arm64`,
+`windows-amd64`); on Windows the bash steps run under Git Bash and the worker
+LOCATION is the native path to the `.venv/Scripts/vgi-easter.exe` launcher.
 
 ## How it works (no C++ build)