tests/e2e/login.spec.mjs: assert the render process is alive with the `crash`
event instead of counting pageerrors; the failed-login test now accepts the
rate-limited message as well as the wrong-password one; the failure hook
attaches the console before the app guard so a launch failure still produces an
artifact, wraps `screenshot()` because it throws on a crashed page, and reaches
`fs.rmSync` on launch failure; dropped the duplicate login-form assertion.
playwright.config.mjs: pin `trace: 'off'` explicitly rather than relying on the
version default, since a trace captures the login POST body.
.gitea/workflows/tests.yml: dropped `--prefer-offline`; corrected the xvfb
comment (the guard is live for the host runner, which already has xvfb); dropped
an unresolvable CI run-number citation.
Checks: `node --check` on both JS files, `npm run test:unit` — 2 passed. E2E
cannot be run locally (no `E2E_PASSWORD` in this session); CI is the check.
act_runner mounts /var/run/docker.sock into every container job, so the fork guard
has to cover the unit job too. The e2e comment now states the blast radius of the
host DOCKER-USER exception instead of the removed container.options. Playwright deps
are narrowed to chromium, which is what Electron uses, and the homeserver reachability
curl gates with -f so a non-2xx fails the job.
The login test claimed "without crashing the app" but asserted only that the body had
text, which is true for an error page. It now asserts no uncaught renderer pageerror,
and toHaveValue after the homeserver commit proves fill() actually stuck.
Run 928 logged "--network and --net in the options will be ignored", so
NetworkMode stayed the per-job bridge. The fix is a DOCKER-USER exception on
the runner host (pizzabox), which accepts RELATED/ESTABLISHED traffic from
br-f192811a98b7; verified 200 from a bridge container after adding it.
The homeserver ruv.wtf (192.168.10.4) is a macvlan interface on the caddy-caddy-1 container on the runner host pizzabox. Replies to a bridge-networked job arrive on br-f192811a98b7 and DOCKER-ISOLATION-STAGE-2 drops them, so the login E2E times out. Host networking keeps request and reply on one path.
The login form only renders after the auth-flows request succeeds. On the runner the form never appeared within the expect timeout, so the login request to ruv.wtf (192.168.10.4) is not reachable from the runner network. The check turns a 30s locator timeout into a clear message.
Playwright's webServer replaces the custom globalSetup. The e2e job is gated to same-repo PRs because a fork PR controls both the test files and the workflow steps while the E2E_PASSWORD secret is in the environment. The dev server is pinned to loopback, the login screen is asserted before filling, the authenticated state is proven by a token-authenticated request, the token value is never printed, the failed-login test no longer asserts a tautological exitCode, and the DevTools window is no longer mistaken for the app window.
- Cache ~/.npm (setup-node) and ~/.cache/electron{,-builder} between runs
- Merge increment-version + prepare-release into one job; build jobs check out
the bumped commit directly instead of pulling
- Install wine64 only (drop i386 arch + wine32)
- Shallow checkouts in build jobs; drop no-op clean step
- Fix GITHUB_TOKEN/GITEA_TOKEN mixup in finalize-release tag cleanup
- NSIS compression: store (faster, larger exe)
- Bump cinny submodule: sourcemap skipped in CI
Use PowerShell + curl.exe on the Windows runner (no WSL), and clone cinny via a relative/origin-derived URL so act runners do not hairpin through public HTTPS.
Publish build outputs straight to Gitea/GitHub releases via the REST API with no HTTP timeout, since Gitea's artifact pipeline keeps timing out on ~130MB binaries.
- Implemented main plugin structure including manifest, HTML, and JavaScript files.
- Added actions for toggling mute, toggling deafen, changing channels, sending messages, and getting status.
- Created property inspector for changing channels and sending messages.
- Developed SVG icons for actions and status display.
- Established WebSocket connection for communication with the Stream Deck.
- Implemented API calls to interact with the Paarrot voice chat application.
- Added validation script to ensure proper plugin structure and manifest compliance.
- Included test Electron application for window creation and loading content.