fix: make db:migrate work with proper journal and env loading#284
Merged
zbigniewsobiecki merged 2 commits intodevfrom Feb 16, 2026
Merged
fix: make db:migrate work with proper journal and env loading#284zbigniewsobiecki merged 2 commits intodevfrom
zbigniewsobiecki merged 2 commits intodevfrom
Conversation
- Populate meta/_journal.json with entries for all 5 migrations (was empty because migrations were hand-written, not generated) - Add db-bootstrap-journal.ts tool to seed drizzle.__drizzle_migrations tracking table for databases set up with drizzle-kit push - Fix db:migrate/push/studio package.json scripts to load .env via node --env-file=.env (drizzle-kit doesn't load dotenv) - Add db:bootstrap-journal script to package.json - Document migration workflow in CLAUDE.md Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
zbigniewsobiecki
force-pushed
the
fix/migration-journal
branch
from
7fe8c5d to
9e930a8
Compare
Deduplicate respond-to-pr-comment and respond-to-review agents into a shared prResponseAgent module with common PR context fetching, comment handling, and response formatting. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
meta/_journal.jsonwith entries for all 5 migrations (was empty because migrations were hand-written, not generated bydrizzle-kit generate)db-bootstrap-journal.tstool to seeddrizzle.__drizzle_migrationstracking table for databases previously set up withdrizzle-kit pushdb:migrate/db:push/db:studiopackage.json scripts to load.envvianode --env-file=.env(drizzle-kit doesn't load dotenv)db:bootstrap-journalscript to package.jsonRoot cause
The database was originally set up with
drizzle-kit pushwhich doesn't create a migration journal. Whendrizzle-kit migrateruns, it readsmeta/_journal.jsonfor the list of migrations — empty journal means nothing to apply.Test plan
npm run db:migrateworks without manualsource .envnpm run db:migrateis idempotent (no-op when all migrations applied)db:migrate🤖 Generated with Claude Code