Marc-André Bombeck 873f3eb8d0 fix(db): backfill the users.locale column as a migration (#140) ...

`users.locale` has been on `schema.prisma` since the v1.3 locale-aware
reminder work but never landed in the migration history — the column
was applied via `prisma db push` to dev/prod and not committed as a
migration. The drift is invisible against any environment that was
ever pushed to, and only surfaces when a fresh database is built
strictly from `prisma/migrations/` (CI integration test containers,
brand-new self-host installs from a tagged image, etc.) — Postgres
then reports `column users.locale does not exist` the first time the
Prisma client touches the column.

The migration is `ADD COLUMN IF NOT EXISTS`, so it's a clean add on a
fresh database and a safe no-op against any environment that was
already pushed-to.

2026-05-08 14:29:44 +02:00

..

migrations

fix(db): backfill the users.locale column as a migration (#140)

2026-05-08 14:29:44 +02:00

schema.prisma

audit(v1.3.3): SpO2 + body-composition + 14 CRITICAL/HIGH security/correctness fixes (#121)

2026-05-08 01:05:56 +02:00