From b4ee36c5c868cad51a5524d6bb32c40051f881dd Mon Sep 17 00:00:00 2001 From: yuneng-jiang Date: Thu, 12 Mar 2026 12:24:46 -0700 Subject: [PATCH] Restore _mark_all_migrations_applied for P3005 baselining path P3005 fires only during the db-push-to-migrate transition, when the _prisma_migrations table doesn't exist yet. Since db push already kept the schema in sync, all shipped migrations are already reflected in the DB. Mark them all as applied (standard Prisma baselining) instead of running deploy-with-resolution, which would fail on pre-existing data issues like duplicate rows preventing unique index creation. Co-Authored-By: Claude Opus 4.6 --- litellm-proxy-extras/litellm_proxy_extras/utils.py | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/litellm-proxy-extras/litellm_proxy_extras/utils.py b/litellm-proxy-extras/litellm_proxy_extras/utils.py index 30aba6b1f49..30bbdc9a57b 100644 --- a/litellm-proxy-extras/litellm_proxy_extras/utils.py +++ b/litellm-proxy-extras/litellm_proxy_extras/utils.py @@ -449,11 +449,14 @@ class ProxyExtrasDBManager: ) ProxyExtrasDBManager._create_baseline_migration(schema_path) logger.info( - "Baseline migration created, running deploy with idempotent resolution " - "to apply remaining migrations..." + "Baseline migration created, marking all existing migrations as applied. " + "This is the standard Prisma baselining approach for databases " + "previously managed by db push." ) - ProxyExtrasDBManager._deploy_with_idempotent_resolution() - logger.info("✅ All migrations applied.") + ProxyExtrasDBManager._mark_all_migrations_applied( + migrations_dir + ) + logger.info("✅ All migrations marked as applied.") return True else: raise