ci(docs): Add agentic workflows for codebase documentation #7728
dingsdaxsecret-scan.yml Required
on: pull_request
Secret Scan
13s
Annotations
4 errors
|
MCP Gateway receives empty API key and port due to incorrect step output references:
.github/workflows/docs-codebase-refresh.lock.yml#L647
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 'Start Safe Outputs MCP HTTP Server' step (id: safe-outputs-start) never sets these outputs. The API key and port are actually set by 'Generate Safe Outputs MCP Server Config' step (id: safe-outputs-config) with output names `safe_outputs_api_key` and `safe_outputs_port`. This causes the MCP Gateway to receive empty/undefined credentials, potentially causing authentication failures or security bypasses if the safeoutputs server accepts empty Authorization headers.
|
|
[ZZX-7RN] MCP Gateway receives empty API key and port due to incorrect step output references (additional location):
.github/workflows/docs-codebase-update.lock.yml#L647
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 'Start Safe Outputs MCP HTTP Server' step (id: safe-outputs-start) never sets these outputs. The API key and port are actually set by 'Generate Safe Outputs MCP Server Config' step (id: safe-outputs-config) with output names `safe_outputs_api_key` and `safe_outputs_port`. This causes the MCP Gateway to receive empty/undefined credentials, potentially causing authentication failures or security bypasses if the safeoutputs server accepts empty Authorization headers.
|
|
MCP Gateway step references wrong step outputs, causing API key and port to be empty:
.github/workflows/docs-codebase-update.lock.yml#L647
Lines 647-648 reference `steps.safe-outputs-start.outputs.api_key` and `steps.safe-outputs-start.outputs.port`, but the `safe-outputs-start` step (lines 623-641) never sets these outputs. The API key and port are actually set in the `safe-outputs-config` step via `$GITHUB_OUTPUT`. This will cause `GH_AW_SAFE_OUTPUTS_API_KEY` and `GH_AW_SAFE_OUTPUTS_PORT` to be empty in the MCP Gateway step, breaking authentication to the Safe Outputs server.
|
|
[A5K-NUZ] MCP Gateway step references wrong step outputs, causing API key and port to be empty (additional location):
.github/workflows/docs-codebase-refresh.lock.yml#L647
Lines 647-648 reference `steps.safe-outputs-start.outputs.api_key` and `steps.safe-outputs-start.outputs.port`, but the `safe-outputs-start` step (lines 623-641) never sets these outputs. The API key and port are actually set in the `safe-outputs-config` step via `$GITHUB_OUTPUT`. This will cause `GH_AW_SAFE_OUTPUTS_API_KEY` and `GH_AW_SAFE_OUTPUTS_PORT` to be empty in the MCP Gateway step, breaking authentication to the Safe Outputs server.
|