From e53ad6c67bb978f2e7b7b19ff109ed81270edae3 Mon Sep 17 00:00:00 2001
From: Pablo Pettinari <pettinarip@gmail.com>
Date: Tue, 14 Apr 2026 19:31:10 +0200
Subject: [PATCH] Fix Trigger.dev CI auth: use TRIGGER_ACCESS_TOKEN

The deploy-data-layer workflow was failing because the Trigger.dev CLI
requires TRIGGER_ACCESS_TOKEN (a Personal Access Token) for CI
authentication, not TRIGGER_SECRET_KEY.
---
 .github/workflows/deploy-data-layer.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/deploy-data-layer.yml b/.github/workflows/deploy-data-layer.yml
index fa8c92bcdd4..c396f9f0fb5 100644
--- a/.github/workflows/deploy-data-layer.yml
+++ b/.github/workflows/deploy-data-layer.yml
@@ -32,4 +32,4 @@ jobs:
       - name: Deploy to Trigger.dev
         run: pnpm exec trigger deploy
         env:
-          TRIGGER_SECRET_KEY: ${{ secrets.TRIGGER_SECRET_KEY }}
+          TRIGGER_ACCESS_TOKEN: ${{ secrets.TRIGGER_ACCESS_TOKEN }}