Skip to content

feat: unify Free session and host management #25

feat: unify Free session and host management

feat: unify Free session and host management #25

Triggered via push May 18, 2026 01:08
Status Failure
Total duration 54s
Artifacts
Deploy Relay Worker
0s
Deploy Relay Worker
Deploy Workbench Pages
0s
Deploy Workbench Pages
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
Verify
Process completed with exit code 2.
src/host/runtime-service.test.ts > ACP runtime service > exits on SIGTERM when it owns an open ACP runtime session: src/host/runtime-service.test.ts#L141
Error: Runtime service did not start. ❯ waitForRuntimeService src/host/runtime-service.test.ts:141:9 ❯ src/host/runtime-service.test.ts:110:5
src/host/runtime-service.test.ts > ACP runtime service > keeps an in-flight turn alive after the host client disconnects and reattaches: src/host/runtime-service.test.ts#L141
Error: Runtime service did not start. ❯ waitForRuntimeService src/host/runtime-service.test.ts:141:9 ❯ src/host/runtime-service.test.ts:48:5
Verify
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/