Parent
What to build
Deploy the verified vv1.89.1 to production on modelharbor. Push vv1.89.1 so the CI image-build workflow builds the real amd64 image (NOT the throwaway local arm64 image) and pushes it to the registry. Before touching the running proxy, capture a current production database backup and check prisma migrate status for drift. Then docker compose pull litellm && docker compose up -d litellm, verify the proxy is healthy, and confirm one live glm request records response_cost > 0. Retain the previous vv1.82.3-stable.patch.4 image and the database backup as the rollback path (Prisma migrations are forward-only, so rollback is image-swap plus backup-restore).
Acceptance criteria
Blocked by
Parent
What to build
Deploy the verified
vv1.89.1to production on modelharbor. Pushvv1.89.1so the CI image-build workflow builds the real amd64 image (NOT the throwaway local arm64 image) and pushes it to the registry. Before touching the running proxy, capture a current production database backup and checkprisma migrate statusfor drift. Thendocker compose pull litellm && docker compose up -d litellm, verify the proxy is healthy, and confirm one live glm request recordsresponse_cost > 0. Retain the previousvv1.82.3-stable.patch.4image and the database backup as the rollback path (Prisma migrations are forward-only, so rollback is image-swap plus backup-restore).Acceptance criteria
vv1.89.1is pushed and CI builds + pushes the amd64 image to the registryprisma migrate statusis checked for drift before deploydocker compose up -d litellmsucceedsSpendLogs.response_cost > 0vv1.82.3-stable.patch.4image and DB backup are retained for rollbackBlocked by