Fix Trigger.dev CI deploy authentication#17977
Merged
Conversation
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.
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
wackerow
approved these changes
Apr 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
TRIGGER_SECRET_KEYwithTRIGGER_ACCESS_TOKENin the deploy-data-layer workflowTRIGGER_ACCESS_TOKEN) for CI authenticationAction required
Add the
TRIGGER_ACCESS_TOKENsecret to the repo (Settings → Secrets → Actions) with a Trigger.dev Personal Access Token.Test plan
TRIGGER_ACCESS_TOKENsecret is set in repo settingssrc/data-layer/on master and confirm the workflow passes