Skip to content

fix: vendor @faf/engine tgz for CI compatibility #21

fix: vendor @faf/engine tgz for CI compatibility

fix: vendor @faf/engine tgz for CI compatibility #21

Triggered via push March 24, 2026 22:36
Status Failure
Total duration 32s
Artifacts
📊 Coverage Gate
13s
📊 Coverage Gate
⚡ Performance Gate
13s
⚡ Performance Gate
📝 TypeScript Gate
21s
📝 TypeScript Gate
🧹 Lint Gate
12s
🧹 Lint Gate
🔒 Security Gate
15s
🔒 Security Gate
📋 Quality Gates Summary
4s
📋 Quality Gates Summary
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 5 warnings
🧹 Lint Gate
Process completed with exit code 1.
⚡ Performance Gate
Process completed with exit code 1.
📊 Coverage Gate
Process completed with exit code 1.
📝 TypeScript Gate: src/adapters/mcp.ts#L192
Object literal may only specify known properties, and 'method' does not exist in type '{ readonly cause?: Error | undefined; readonly userMessage?: string | undefined; readonly technicalDetails?: string | undefined; readonly context?: Partial<{ readonly platform?: "github" | "gitlab" | ... 9 more ... | undefined; readonly url?: string | undefined; readonly userAgent?: string | undefined; readonly time...'.
📝 TypeScript Gate: src/adapters/mcp.ts#L171
Object literal may only specify known properties, and 'status' does not exist in type '{ readonly cause?: Error | undefined; readonly userMessage?: string | undefined; readonly technicalDetails?: string | undefined; readonly context?: Partial<{ readonly platform?: "github" | "gitlab" | ... 9 more ... | undefined; readonly url?: string | undefined; readonly userAgent?: string | undefined; readonly time...'.
📝 TypeScript Gate: src/adapters/mcp.ts#L139
Object literal may only specify known properties, and 'tool' does not exist in type '{ readonly cause?: Error | undefined; readonly userMessage?: string | undefined; readonly technicalDetails?: string | undefined; readonly context?: Partial<{ readonly platform?: "github" | "gitlab" | ... 9 more ... | undefined; readonly url?: string | undefined; readonly userAgent?: string | undefined; readonly time...'.
📝 TypeScript Gate: src/adapters/mcp.ts#L60
Object literal may only specify known properties, and 'mcpError' does not exist in type '{ readonly cause?: Error | undefined; readonly userMessage?: string | undefined; readonly technicalDetails?: string | undefined; readonly context?: Partial<{ readonly platform?: "github" | "gitlab" | ... 9 more ... | undefined; readonly url?: string | undefined; readonly userAgent?: string | undefined; readonly time...'.
📝 TypeScript Gate: src/adapters/mcp.ts#L7
'FileInfo' is declared but never used.
📝 TypeScript Gate: src/adapters/downloads.ts#L167
'getUniqueLanguages' is declared but its value is never read.
📝 TypeScript Gate: src/adapters/clipboard.ts#L166
Property 'score' does not exist on type 'FAFFile'.
📝 TypeScript Gate: src/adapters/clipboard.ts#L86
Property 'score' does not exist on type 'FAFFile'.
📝 TypeScript Gate: src/adapters/chrome.ts#L314
'score' is declared but its value is never read.
📝 TypeScript Gate: src/adapters/chrome.ts#L7
Module '"@/core/types"' has no exported member 'Score'.
📋 Quality Gates Summary
Process completed with exit code 1.
🧹 Lint Gate
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. 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/
⚡ Performance Gate
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. 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/
📊 Coverage Gate
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. 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/
🔒 Security Gate
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. 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/
📝 TypeScript Gate
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. 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/