From 2cc8b1c2af0fa040b169bd57d8123582cfbc73ba Mon Sep 17 00:00:00 2001
From: Vansh Gilhotra <140490653+Vansh5632@users.noreply.github.com>
Date: Wed, 10 Sep 2025 12:16:46 +0530
Subject: [PATCH] fix: Use db-deploy instead of db-migrate for yarn dx in
 non-interactive environments (#23253)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Fixes the issue where 'yarn dx' fails in non-interactive environments
(CI/CD, Docker, automated scripts) by changing Turbo dependencies:

- @calcom/prisma#db-seed: db-migrate → db-deploy
- @calcom/prisma#dx: db-migrate → db-up

This ensures that non-interactive 'prisma migrate deploy' is used
instead of interactive 'prisma migrate dev', allowing yarn dx to
work correctly in automated environments.

Resolves: Cal.com App Store performance optimization - yarn dx failure

Co-authored-by: Anik Dhabal Babu <81948346+anikdhabal@users.noreply.github.com>
---
 turbo.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/turbo.json b/turbo.json
index 6dca728b79..16912a4316 100644
--- a/turbo.json
+++ b/turbo.json
@@ -276,14 +276,14 @@
     },
     "@calcom/prisma#db-seed": {
       "cache": false,
-      "dependsOn": ["@calcom/prisma#db-migrate"]
+      "dependsOn": ["@calcom/prisma#db-deploy"]
     },
     "@calcom/prisma#db-up": {
       "cache": false
     },
     "@calcom/prisma#dx": {
       "cache": false,
-      "dependsOn": ["@calcom/prisma#db-migrate"]
+      "dependsOn": ["@calcom/prisma#db-up"]
     },
     "@calcom/trpc#build": {
       "outputs": ["./types"]