Skip to content

docs(readme): update for v0.3.0 — registry, BS detector, local models… #88

docs(readme): update for v0.3.0 — registry, BS detector, local models…

docs(readme): update for v0.3.0 — registry, BS detector, local models… #88

Triggered via push April 10, 2026 14:29
Status Failure
Total duration 1m 42s
Artifacts 1

ci.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 5 warnings
LOC Gate (Max 800 lines): src/support/chatTui.ts#L0
File exceeds 800 lines (1268)
LOC Gate (Max 800 lines): src/support/web.ts#L0
File exceeds 800 lines (995)
LOC Gate (Max 800 lines): src/linear/linear.ts#L0
File exceeds 800 lines (1259)
LOC Gate (Max 800 lines): src/automation/autonomousRunner.ts#L0
File exceeds 800 lines (1263)
LOC Gate (Max 800 lines): src/automation/runnerExecution.ts#L0
File exceeds 800 lines (889)
LOC Gate (Max 800 lines): src/automation/prProcessor.ts#L0
File exceeds 800 lines (872)
LOC Gate (Max 800 lines): src/discord/discordHandlers.ts#L0
File exceeds 800 lines (991)
LOC Gate (Max 800 lines): src/discord/discordCore.ts#L0
File exceeds 800 lines (887)
LOC Gate (Max 800 lines): src/registry/sqliteStore.ts#L0
File exceeds 800 lines (1038)
LOC Gate (Max 800 lines): src/agents/pairPipeline.ts#L0
File exceeds 800 lines (1013)
Tests
Process completed with exit code 1.
src/core/config.test.ts > config > Zod schema validation > should reject config without required linear team ID: src/core/config.test.ts#L497
AssertionError: expected [Function] to throw an error - Expected: null + Received: undefined ❯ src/core/config.test.ts:497:52
src/core/config.test.ts > config > Zod schema validation > should reject config without required discord token: src/core/config.test.ts#L478
AssertionError: expected [Function] to throw an error - Expected: null + Received: undefined ❯ src/core/config.test.ts:478:52
LOC Gate (Max 800 lines)
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 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/
Lint
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/
Type Check
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/
Build
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/upload-artifact@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/
Tests
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/

Artifacts

Produced during runtime
Name Size Digest
dist Expired
821 KB
sha256:631a6a617d7bdef84011f9d7b1969f3e13fb86fcbc7275b4ab77b8cf38a87b31