Skip to content

fix: use last step output instead of longest in MCP response extraction #2114

fix: use last step output instead of longest in MCP response extraction

fix: use last step output instead of longest in MCP response extraction #2114

Triggered via push March 21, 2026 19:02
Status Failure
Total duration
Artifacts

This workflow graph cannot be shown

A graph will be generated the next time this workflow is run.

Annotations

1 error
Invalid workflow file: .github/workflows/ai-battle-test.yml#L1
(Line: 186, Col: 13): Unrecognized named-value: 'secrets'. Located at position 44 within expression: matrix.ai_provider.api_key_secret != '' && secrets[matrix.ai_provider.api_key_secret] != '', (Line: 278, Col: 13): Unrecognized named-value: 'secrets'. Located at position 47 within expression: matrix.ai_provider.name == 'Google Gemini' && secrets.GOOGLE_API_KEY != ''