nxtgauge-backend-rust

History

Ashwin Kumar Sivakumar e80ce2901c All checks were successful build-and-release / build (cron) (push) Successful in 48s Details build-and-release / build (catering-services) (push) Successful in 1m31s Details build-and-release / build (companies) (push) Successful in 1m34s Details build-and-release / build (developers) (push) Successful in 1m59s Details build-and-release / build (customers) (push) Successful in 2m10s Details build-and-release / build (employees) (push) Successful in 2m15s Details build-and-release / build (gateway) (push) Successful in 59s Details build-and-release / build (jobs) (push) Successful in 46s Details build-and-release / build (graphic-designers) (push) Successful in 1m33s Details build-and-release / build (fitness-trainers) (push) Successful in 2m44s Details build-and-release / build (makeup-artists) (push) Successful in 1m53s Details build-and-release / build (job-seekers) (push) Successful in 2m30s Details build-and-release / build (leads) (push) Successful in 2m32s Details build-and-release / build (photographers) (push) Successful in 2m33s Details build-and-release / build (payments) (push) Successful in 2m53s Details build-and-release / build (social-media-managers) (push) Successful in 2m38s Details build-and-release / build (ugc-content-creators) (push) Successful in 2m19s Details build-and-release / build (tutors) (push) Successful in 2m53s Details build-and-release / build (video-editors) (push) Successful in 2m14s Details build-and-release / build (users) (push) Successful in 4m35s Details fix(db): make ai_plans_and_limits migration idempotent The db-migrate job (crates/db-migrate) has no applied-migrations tracking table - it replays every .sql file on every run, relying on each file being idempotent (IF NOT EXISTS / ON CONFLICT), which is the pattern virtually every other migration in this directory follows. This one wasn't: plain CREATE TABLE/CREATE INDEX and two INSERTs with no ON CONFLICT guard. Since the tables/data already exist from this file's one successful run, every subsequent migration job run failed immediately on "relation ai_plans already exists" - before ever reaching any migration after it, including ones genuinely needed (see the verification_logs FK fix two commits back). Confirmed via a live job run: this was the actual reason db-migrate had never completed successfully before. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>		2026-07-19 03:14:02 +05:30
..
auth	fix payments runtime and jwt backend	2026-06-09 22:52:30 +02:00
cache	feat(employees): add forgot-password/reset-password for admin accounts	2026-07-14 23:28:39 +05:30
contracts	fix: end-to-end workflow fixes for company/job-seeker and profession flows	2026-07-18 11:40:01 +02:00
db	fix(db): make ai_plans_and_limits migration idempotent	2026-07-19 03:14:02 +05:30
db-migrate	feat(db): update service handlers and models for new schema	2026-04-13 00:29:44 +02:00
email	Update backend services: catering_services, companies, developers, gateway, job_seekers, photographers, social_media_managers, tutors, ugc_content_creators, users; update cache (otp, token), contracts (profession_shared, profession_state), db (job_seeker, verification), email; add revision-requested email template; update init-db.sql and start-services.sh	2026-05-08 15:34:29 +02:00
invoice	feat: profile photo upload, PDF resume generation, AI auto-apply, schema fixes	2026-07-02 13:31:06 +02:00
storage	fix: end-to-end workflow fixes for company/job-seeker and profession flows	2026-07-18 11:40:01 +02:00
wallet	feat: profile photo upload, PDF resume generation, AI auto-apply, schema fixes	2026-07-02 13:31:06 +02:00