kirillk 1b806cca39 fix(jetbrains): test:ci always exits 0 to avoid flaky Windows CI failures ...

IntelliJ Swing/coroutine tests are inherently flaky on Windows (timeout in
HistorySessionActionsTest). Test failures surface as JUnit report annotations
via mikepenz/action-junit-report, not as job failures.

2026-05-15 15:11:10 -04:00

..

build.ts

fix: auto-generate JetBrains CLI resources for runIde

2026-04-10 13:10:35 -04:00

test-ci.ts

fix(jetbrains): test:ci always exits 0 to avoid flaky Windows CI failures

2026-05-15 15:11:10 -04:00