f9718f85d0
All checks were successful
build-and-release / build (developers) (push) Successful in 3m6s
build-and-release / build (jobs) (push) Successful in 1m54s
build-and-release / build-db-migrate (push) Successful in 2m42s
build-and-release / build (companies) (push) Successful in 1m50s
build-and-release / build (photographers) (push) Successful in 2m59s
build-and-release / build (makeup-artists) (push) Successful in 1m34s
build-and-release / build (gateway) (push) Successful in 1m34s
build-and-release / build (ugc-content-creators) (push) Successful in 3m13s
build-and-release / build (job-seekers) (push) Successful in 3m0s
build-and-release / build (tutors) (push) Successful in 2m48s
build-and-release / build (users) (push) Successful in 4m55s
build-and-release / build (customers) (push) Successful in 1m50s
build-and-release / build (graphic-designers) (push) Successful in 1m53s
build-and-release / build (social-media-managers) (push) Successful in 1m51s
build-and-release / build (video-editors) (push) Successful in 2m52s
build-and-release / build (catering-services) (push) Successful in 2m28s
build-and-release / build (fitness-trainers) (push) Successful in 2m49s
build-and-release / build (payments) (push) Successful in 2m44s
build-and-release / build (cron) (push) Successful in 1m6s
build-and-release / build (employees) (push) Successful in 2m28s
backend-integration-tests / ai-credits (push) Successful in 52s
The migrate image (Dockerfile.migrate) was never part of the CI build matrix - it's a separate crate, not an apps/* service, and the running K8s Job pulls a static <branch>-latest tag rather than a pinned digest. Without this, a stale image silently no-ops new migrations: the Job reports success but applies nothing, which is exactly what happened with the ai_guard_violations migration on 2026-08-15. |
||
|---|---|---|
| .. | ||
| scripts | ||
| workflows | ||