fix: deploy the dashboard agent one environment at a time#4133
Conversation
Parallel legs deploying the same Trigger.dev project raced: one leg failed to create the background worker while the other succeeded. Run the matrix with max-parallel 1 so the environments deploy sequentially.
|
WalkthroughThe dashboard agent deploy workflow now sets Changes
Related Issues: No related issues linked. Related PRs: No related PRs found. Suggested Labels: ci, github-actions Suggested Reviewers: No specific reviewer suggestions available. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Aligns node-version to 22.23.1 (.nvmrc), matching every other workflow.
The dashboard agent deploy runs a matrix leg per environment (staging, prod). Running them in parallel deployed the same Trigger.dev project twice at once, and one leg failed to create the background worker while the other succeeded.
max-parallel: 1runs the legs sequentially so a deploy never races itself.Also aligns the workflow's Node version to the repo standard (
22.23.1, per.nvmrc).Verified: re-running the staging leg on its own (no parallel prod) deployed cleanly.