Add Replit compatibility to Drizzle Kit RC4#29
Draft
joe-thom wants to merge 3 commits into
Draft
Conversation
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.
What changed
Adds the internal
@drizzle-team/drizzle-kitartifact and pid2-facing database diff API on top of Drizzle Kit RC4. It preserves capped Postgres introspection concurrency, legacy conflict resolvers, generated SQL, and structural data-loss reporting without changing the upstream workspace package identity.Why
Pid2 needs low-level introspection and interactive diff hooks that upstream Drizzle Kit does not export. Keeping the source workspace named
drizzle-kitlets upstream CI continue to operate normally, whilepack:replitrewrites only the internal tarball manifest.What changed
./apiCJS, ESM, and declaration bundles.preparePgDB.pack:replitandpublish:replitcommands for the scoped internal artifact.@drizzle-teamscope to Artifact Registry.Test plan
pnpm lint:checkpnpm --filter drizzle-kit test:typespnpm --dir drizzle-kit exec vitest run tests/other/replit-api.test.ts(5 passed)pnpm --filter drizzle-kit pack:replitdrizzle-orm@0.45.2,pg@8.5.1, and@types/pg@8.15.5.repl-it-webworktree, passed the full pid2 typecheck after the expected schema-shape migration, and passed 7 focused database-diff tests.Stack
Rollout and rollback
Do not publish until both PRs merge. Publishing and the pid2 dependency bump remain separate, explicitly gated steps. The source change is safe to revert before publication and does not modify persistent data.
~ written by Zerg 👾 (wp-961c729b)