Skip to content

Chore/adopt drizzle kit - #19

Merged
devtofunmi merged 4 commits into
mainfrom
chore/adopt-drizzle-kit
Aug 12, 2026
Merged

Chore/adopt drizzle kit#19
devtofunmi merged 4 commits into
mainfrom
chore/adopt-drizzle-kit

Conversation

@devtofunmi

Copy link
Copy Markdown
Owner

No description provided.

The db:generate/db:migrate/db:studio scripts and drizzle.config.ts referenced drizzle-kit, but it was never installed (tsc reported 'Cannot find module drizzle-kit'). Add it as a dev dependency so migrations can actually be generated and applied.
drizzle-kit writes migration SQL and meta/*.json snapshots; they're tool-managed and re-emitted on every generate, so Prettier shouldn't police them.
The prior 0000-0002 migrations had drifted from schema.ts: 0001/0002 were hand-written SQL whose meta snapshots were never updated, so the history was internally inconsistent (a regenerated catch-up re-added columns 0002 already added). Replace them with a single baseline generated from schema.ts covering all 10 tables, 5 enums, every column (plan/runs_used/runs_period_start/bachs_*, workspace_settings, review_runs.head_sha, users.onboarded_at), FKs, and the 4 unique indexes. Existing databases must be baselined (mark this migration applied) so db:migrate is a no-op on them; a fresh clone gets the correct schema in one step.
@vercel

vercel Bot commented Aug 12, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
jargons-8yyz Ready Ready Preview Aug 12, 2026 10:12pm

@devtofunmi
devtofunmi merged commit d6a7d87 into main Aug 12, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant