Skip to content

[codex] refactor plugin catalogs and registration #170

[codex] refactor plugin catalogs and registration

[codex] refactor plugin catalogs and registration #170

Triggered via pull request April 12, 2026 22:58
Status Failure
Total duration 1m 32s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 4 warnings
Lint
Process completed with exit code 1.
Unhandled error: node_modules/.bun/postgres@3.4.9/node_modules/postgres/cf/polyfills.js#L210
Error: Stream was cancelled. ❯ read ../../node_modules/.bun/postgres@3.4.9/node_modules/postgres/cf/polyfills.js:210:33 This error originated in "src/services/db.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
Unhandled error: node_modules/.bun/postgres@3.4.9/node_modules/postgres/cf/polyfills.js#L210
Error: Stream was cancelled. ❯ read ../../node_modules/.bun/postgres@3.4.9/node_modules/postgres/cf/polyfills.js:210:33 This error originated in "src/services/db.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "supports nested scopes within a single outer scope (regression: /api/scope pattern)". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
Unhandled error: node_modules/.bun/postgres@3.4.9/node_modules/postgres/cf/polyfills.js#L210
Error: Stream was cancelled. ❯ read ../../node_modules/.bun/postgres@3.4.9/node_modules/postgres/cf/polyfills.js:210:33 This error originated in "src/services/db.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "supports nested scopes within a single outer scope (regression: /api/scope pattern)". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
Unhandled error: node_modules/.bun/postgres@3.4.9/node_modules/postgres/cf/polyfills.js#L210
Error: Stream was cancelled. ❯ read ../../node_modules/.bun/postgres@3.4.9/node_modules/postgres/cf/polyfills.js:210:33 This error originated in "src/services/db.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "supports multiple sequential scopes (regression: pg socket reuse hang)". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
Unhandled error: node_modules/.bun/postgres@3.4.9/node_modules/postgres/cf/polyfills.js#L210
Error: Stream was cancelled. ❯ read ../../node_modules/.bun/postgres@3.4.9/node_modules/postgres/cf/polyfills.js:210:33 This error originated in "src/services/db.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "supports multiple sequential scopes (regression: pg socket reuse hang)". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
Unhandled error: node_modules/.bun/postgres@3.4.9/node_modules/postgres/cf/polyfills.js#L210
Error: Stream was cancelled. ❯ read ../../node_modules/.bun/postgres@3.4.9/node_modules/postgres/cf/polyfills.js:210:33 This error originated in "src/services/db.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "round-trips an account through the user store". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
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 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/
eslint(no-unused-vars): packages/react/src/pages/secrets.tsx#L4
Type 'SecretProviderPlugin' is imported but never used.
Typecheck
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/
Test
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/