From a41e124bb23d1c2fb6d5f244adf2c64b90c6a17d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Erik=20Bj=C3=A4reholt?= Date: Wed, 24 Jun 2026 12:53:11 +0200 Subject: [PATCH] fix(ci): use 'poetry run' in test target + run typecheck The test target called the bare 'aw-watcher-window' console script, which only resolves when the venv's bin/ is on PATH. Under the unified release workflow (activates venv, then 'make test') this is flaky: the same job that passes on one run fails with 'aw-watcher-window: No such file or directory' on another, and the retry wrapper just re-runs the identical failure. Switch to 'poetry run aw-watcher-window --help' to match aw-watcher-afk and aw-watcher-input, which resolves the entrypoint regardless of PATH. Also run 'make typecheck' here like the sibling watchers (window was skipping mypy entirely). --- Makefile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 4c50b28d..6806465a 100644 --- a/Makefile +++ b/Makefile @@ -13,7 +13,8 @@ aw_watcher_window/aw-watcher-window-macos: aw_watcher_window/macos.swift swiftc $^ -o $@ test: - aw-watcher-window --help + poetry run aw-watcher-window --help # Ensures that it at least starts + make typecheck typecheck: poetry run mypy aw_watcher_window/ --ignore-missing-imports