fix(drizzle): fall back to drizzle-kit CLI#632
Open
utopyin wants to merge 1 commit into
Open
Conversation
60adc20 to
9dac5e7
Compare
9dac5e7 to
17d6c90
Compare
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
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.
Handle Drizzle dialect modules that no longer expose the programmatic migration API by falling back to
drizzle-kit generate.For diff, the fallback copies the current migrations into a temp directory and runs drizzle-kit there so planning can detect whether the CLI would create a new migration without mutating the real
outdirectory.For reconcile, drizzle-kit owns the write path directly:
The CLI invocation uses the repo's Effect child-process wrapper and resolves the package-local
drizzle-kit/bin.cjsentrypoint. Local TTY runs inherit stdio so Drizzle rename prompts can be answered; CI/non-TTY runs keep piped stdio so interactive prompts fail fast.Adds sqlite coverage for initial generation, no-drift repeated deploys, drift updates through the CLI fallback and any interactive prompt in CI/non-TTY exit with a failure.