Skip to content

Live drift check failing #2375

Description

@github-actions

The live Supabase drift check is failing. This issue is updated in place by
.github/workflows/live-drift.yml; it is closed automatically on the next green run.

Drift findings

Drift manifest: generated 2026-08-27T06:12:59.010Z from schema.sql 4048b5d3ea15…
Compared 6 extensions, 43 tables, 1 views, 97 functions, 222 indexes, 53 policies, 207 constraints, 26 triggers, 2 storage_buckets against live.
UNEXPECTED DRIFT (3):
  ! [functions] mismatch public.correct_clinical_query_terms(text,real) :: def_hash: manifest="cb65883a561cb1f5cd2247213f417a41" live="e2356565197b3d4c13f1b3d7a624696b"
  ! [functions] mismatch public.create_uploaded_document_with_ingestion_job(jsonb,integer) :: def_hash: manifest="54f1ab21c9d7cee9555b187dec088371" live="93bd4e366deaf415b35e8a287d0067fe"
  ! [functions] mismatch public.set_owner_id_from_auth_uid() :: def_hash: manifest="fefc17c166d7a65a9816e73a14341c1a" live="0612ff7fc739f006b2a4251c5081cb20"
Migration-history check output:

> prompt-for-codex-medical-knowledge-base@0.1.0 check:migration-history
> node scripts/run-tsx.mjs scripts/check-migration-history-alignment.ts

Local migration versions: 221
Remote migration versions: 221 (read via rpc)
Remote-only (Preview blockers): 0
Local-only (pending apply): 0
Migration history alignment OK: every remote version exists locally.

Remediation context: docs/database-remediation-plan.md, docs/database-drift-detection.md.
Never fix drift with raw SQL against live — codify it (migration + schema.sql mirror + regenerated manifest).

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions