nxtgauge-backend-rust

History

Ashwin Kumar Sivakumar eefc0457be All checks were successful build-and-release / build (catering-services) (push) Successful in 1m31s Details build-and-release / build (cron) (push) Successful in 1m54s Details build-and-release / build (companies) (push) Successful in 2m7s Details build-and-release / build (customers) (push) Successful in 2m53s Details build-and-release / build (fitness-trainers) (push) Successful in 1m29s Details build-and-release / build (developers) (push) Successful in 1m43s Details build-and-release / build (gateway) (push) Successful in 1m35s Details build-and-release / build (employees) (push) Successful in 2m15s Details build-and-release / build (jobs) (push) Successful in 1m10s Details build-and-release / build (graphic-designers) (push) Successful in 2m9s Details build-and-release / build (makeup-artists) (push) Successful in 1m35s Details build-and-release / build (photographers) (push) Successful in 1m44s Details build-and-release / build (job-seekers) (push) Successful in 3m8s Details build-and-release / build (payments) (push) Successful in 2m45s Details build-and-release / build (social-media-managers) (push) Successful in 2m35s Details backend-integration-tests / ai-credits (push) Successful in 50s Details build-and-release / build (tutors) (push) Successful in 3m10s Details build-and-release / build (ugc-content-creators) (push) Successful in 2m49s Details build-and-release / build (video-editors) (push) Successful in 2m48s Details build-and-release / build (users) (push) Successful in 4m38s Details fix(test): use a fresh random user per ai_credits_reaper.rs run The fixed UUID (33333333-...) meant every re-run against the same persistent test database reused the same wallet - any earlier partial run that panicked before its own capture/release step left reserved_credits permanently stuck above zero, so this run's fresh reserve (expected to bring it to exactly 4) actually reads 8, 12, etc. depending on how many times the suite had previously failed midway. Matches ai_credits.rs's make_user() pattern (Uuid::new_v4()) instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>		2026-08-13 22:09:33 +05:30
..
auth	fix payments runtime and jwt backend	2026-06-09 22:52:30 +02:00
cache	Fix security audit findings: admin authz, captcha, secret leak, CORS	2026-07-23 17:31:48 +05:30
contracts	fix: security, wallet holds, printpdf upgrade	2026-08-12 13:38:17 +02:00
db	fix(test): use a fresh random user per ai_credits_reaper.rs run	2026-08-13 22:09:33 +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: generate a GST invoice automatically after a successful Tracecoin/PayU purchase	2026-07-21 03:02:47 +05:30
storage	Add presigned document URLs to stop leaking permanent Backblaze links	2026-07-27 18:07:15 +05:30
wallet	feat: profile photo upload, PDF resume generation, AI auto-apply, schema fixes	2026-07-02 13:31:06 +02:00