From 3cc6d4c8a9d2a5e0ec6977700ff5579d70fa3821 Mon Sep 17 00:00:00 2001
From: Max Isbey <224885523+maxisbey@users.noreply.github.com>
Date: Thu, 15 Jan 2026 17:22:29 +0100
Subject: [PATCH] fix(ci): use bash shell for pytest step to ensure consistent
 error handling

On Windows, PowerShell doesn't stop on first error by default. When pytest
fails, PowerShell continues to run coverage combine/report, and if those
succeed, the step exits with code 0 (appearing to pass).

Using 'shell: bash' ensures consistent behavior across platforms - bash's
set -e stops execution on the first failed command.

Claude-Generated-By: Claude Code (cli/claude-opus-4-5=100%)
Claude-Steers: 4
Claude-Permission-Prompts: 4
Claude-Escapes: 0
---
 .github/workflows/shared.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.github/workflows/shared.yml b/.github/workflows/shared.yml
index 684c27ed79..7466664378 100644
--- a/.github/workflows/shared.yml
+++ b/.github/workflows/shared.yml
@@ -56,6 +56,7 @@ jobs:
         run: uv sync ${{ matrix.dep-resolution.install-flags }} --all-extras --python ${{ matrix.python-version }}
 
       - name: Run pytest with coverage
+        shell: bash
         run: |
           uv run --frozen --no-sync coverage run -m pytest
           uv run --frozen --no-sync coverage combine