AIOSAIand@devpulse b25fc5c2fd feat(system): fix(windows-ci): activate venv in Verify step so drone binary is on PATH ...

PR #330 fixed the pip bootstrap (ensurepip error-swallowing in setup.sh). With that fix working, the Verify step in windows-test.yml now fails at 'drone: command not found' (exit 127). Root cause: each CI step spawns a fresh shell, so the venv activation from setup.sh doesn't carry to Verify. drone lives at .venv/Scripts/drone.exe which isn't on the default PATH.

Fix: prepend 'source .venv/Scripts/activate' to the Verify step so drone is findable.

Stacked on PR #330 conceptually — both fixes needed for windows-test.yml to actually pass.

Co-Authored-By: @devpulse <devpulse@aipass>

2026-04-16 11:17:04 -07:00

..

ci.yml

ci(deps): bump codecov/codecov-action from 4 to 6 (#136)

2026-03-28 10:58:51 -07:00

publish.yml

ci(deps): bump actions/upload-artifact from 4 to 7 (#40)

2026-03-14 23:06:57 -07:00

security.yml

chore: add hooks, CI/CD infrastructure, ignore runtime JSON

2026-03-06 20:33:40 -08:00

stale.yml

ci(deps): bump actions/stale from 9 to 10 (#39)

2026-03-14 23:06:55 -07:00

windows-test.yml

feat(system): fix(windows-ci): activate venv in Verify step so drone binary is on PATH

2026-04-16 11:17:04 -07:00