From 98d3328def3c28c5dde5e7cff2da333ddcc4fa42 Mon Sep 17 00:00:00 2001 From: Stephen Belanger Date: Wed, 6 May 2026 17:51:41 -0700 Subject: [PATCH] fix(ci): add COPILOT_API_KEY to e2e-canary workflow env The key was set as a GHA secret but not forwarded to the canary step, causing the copilot scenario subprocess to fail the "COPILOT_API_KEY or BRAINTRUST_E2E_MODEL_BASE_URL must be set" guard. Already present in integration-tests.yaml; this aligns the canary job. Co-Authored-By: Claude Sonnet 4.6 --- .github/workflows/e2e-canary.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/e2e-canary.yaml b/.github/workflows/e2e-canary.yaml index 728c4f069..5542baa47 100644 --- a/.github/workflows/e2e-canary.yaml +++ b/.github/workflows/e2e-canary.yaml @@ -35,6 +35,7 @@ jobs: BRAINTRUST_E2E_PROJECT_NAME: ${{ vars.BRAINTRUST_E2E_PROJECT_NAME }} GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }} COHERE_API_KEY: ${{ secrets.COHERE_API_KEY }} + COPILOT_API_KEY: ${{ secrets.COPILOT_API_KEY }} CURSOR_API_KEY: ${{ secrets.CURSOR_API_KEY }} GROQ_API_KEY: ${{ secrets.GROQ_API_KEY }} OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}