chore: emit and upload coverage.xml from CI (#576)

The test job ran `make test` (no coverage) even though a `test-coverage`
target and pytest-cov were already in place. Point CI at that target and
upload the report so the weekly coverage report can read the number from
the newest successful run on main instead of it being collected by hand.

Coverage measures 94.3% (3305/3505 lines), which matches the figure the
weekly report has been carrying — this repo's hand-collected number was
already accurate, so publishing the artifact just removes the manual step.

`if-no-files-found: error` so a silently-missing report fails the step
rather than publishing an empty artifact.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: runpod-Henrik

.github/workflows/ci.yml

@@ -40,10 +40,21 @@ jobs:
           UV_PYTHON: ${{ matrix.python-version }}
 
       - name: Run tests
-        run: make test
+        run: make test-coverage
         env:
           UV_PYTHON: ${{ matrix.python-version }}
 
+      # Consumed by the weekly coverage report, which reads the artifact from
+      # the newest successful run on main. Name is per-matrix-version because
+      # upload-artifact@v4 requires unique names within a run.
+      - name: Upload coverage report
+        uses: actions/upload-artifact@v4
+        if: always()
+        with:
+          name: coverage-${{ matrix.python-version }}
+          path: coverage.xml
+          if-no-files-found: error
+
   e2e:
     if: github.event_name != 'schedule' && github.repository == 'runpod/runpod-python'
     runs-on: ubuntu-latest

Makefile

@@ -9,7 +9,7 @@ test:
 	uv run pytest
 
 test-coverage:
-	uv run pytest --cov=runpod --cov-report=term-missing
+	uv run pytest --cov=runpod --cov-report=term-missing --cov-report=xml
 
 # --- Build ---
 build: