Skip to content

feat: add MCP file support for ACP server configuration #653

feat: add MCP file support for ACP server configuration

feat: add MCP file support for ACP server configuration #653

Triggered via pull request April 6, 2026 02:40
Status Failure
Total duration 35s
Artifacts

go-test.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 2 warnings
lint
Process completed with exit code 2.
lint: x/acpio/mcp_internal_test.go#L312
undefined: AgentapiMcpServer (typecheck)
lint: x/acpio/mcp_internal_test.go#L302
undefined: AgentapiMcpServer
lint: x/acpio/mcp_internal_test.go#L291
undefined: AgentapiMcpServer
lint: x/acpio/mcp_internal_test.go#L273
undefined: AgentapiMcpServer
lint: x/acpio/mcp_internal_test.go#L254
undefined: AgentapiMcpServer
lint: x/acpio/acpio.go#L202
undefined: AgentapiMcpConfig
test
Process completed with exit code 1.
test: x/acpio/acpio.go#L202
undefined: AgentapiMcpConfig
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-go@v5. 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/setup-go@v5. 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/