ci(docs): Add agentic workflows for codebase documentation #5649
1 issue
find-bugs: Found 1 issue (1 high)
High
MCP Gateway receives empty API key and port due to referencing non-existent step outputs - `.github/workflows/docs-codebase-refresh.lock.yml:647-648`
The start-mcp-gateway step (lines 647-648) references steps.safe-outputs-start.outputs.api_key and steps.safe-outputs-start.outputs.port, but the safe-outputs-start step does not set any outputs via GITHUB_OUTPUT. The actual outputs are set in safe-outputs-config step with names safe_outputs_api_key and safe_outputs_port. This causes GH_AW_SAFE_OUTPUTS_API_KEY and GH_AW_SAFE_OUTPUTS_PORT environment variables to be empty strings when passed to the Docker container, leading to authentication/connection failures with the Safe Outputs MCP server.
Also found at:
.github/workflows/docs-codebase-update.lock.yml:647-648
Duration: 4m 28s · Tokens: 2.5M in / 26.6k out · Cost: $8.15 (+merge: $0.00, +fix_gate: $0.00)
Annotations
Check failure on line 648 in .github/workflows/docs-codebase-refresh.lock.yml
sentry-warden / warden: find-bugs
MCP Gateway receives empty API key and port due to referencing non-existent step outputs
The `start-mcp-gateway` step (lines 647-648) references `steps.safe-outputs-start.outputs.api_key` and `steps.safe-outputs-start.outputs.port`, but the `safe-outputs-start` step does not set any outputs via `GITHUB_OUTPUT`. The actual outputs are set in `safe-outputs-config` step with names `safe_outputs_api_key` and `safe_outputs_port`. This causes `GH_AW_SAFE_OUTPUTS_API_KEY` and `GH_AW_SAFE_OUTPUTS_PORT` environment variables to be empty strings when passed to the Docker container, leading to authentication/connection failures with the Safe Outputs MCP server.
Check failure on line 648 in .github/workflows/docs-codebase-update.lock.yml
sentry-warden / warden: find-bugs
[BC7-ENL] MCP Gateway receives empty API key and port due to referencing non-existent step outputs (additional location)
The `start-mcp-gateway` step (lines 647-648) references `steps.safe-outputs-start.outputs.api_key` and `steps.safe-outputs-start.outputs.port`, but the `safe-outputs-start` step does not set any outputs via `GITHUB_OUTPUT`. The actual outputs are set in `safe-outputs-config` step with names `safe_outputs_api_key` and `safe_outputs_port`. This causes `GH_AW_SAFE_OUTPUTS_API_KEY` and `GH_AW_SAFE_OUTPUTS_PORT` environment variables to be empty strings when passed to the Docker container, leading to authentication/connection failures with the Safe Outputs MCP server.