feat(transactional-adapter-drizzle-orm): accept drizzle-orm v1 in the peer range#604
Open
rodrigobnogueira wants to merge 1 commit into
Open
Conversation
… peer range drizzle-orm v1 is at 1.0.0-rc.4 and the ^0 peer pin makes any install next to it fail resolution, even though the adapter itself never imports drizzle-orm — the client is an opaque value, so nothing in src is affected by the v1 API changes. The new range needs the explicit prerelease comparator because plain semver ranges never match prereleases; >=1.0.0-rc.1 <2.0.0 admits the RC line and stable 1.x alike while keeping ^0. Runtime evidence: nest-native/drizzle's CI runs this adapter's real commit/rollback through @transactional against drizzle-orm@1.0.0-rc.4 on every push and it passes. The package's own tests intentionally stay on the stable 0.45.x devDependency; migrating their RQB usage to v1's relations API only becomes relevant if a dedicated v1 test lane is added. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 5, 2026
rodrigobnogueira
added a commit
to nest-native/drizzle
that referenced
this pull request
Jul 5, 2026
…e it in the canary (#138) The support policy claimed drizzle-zod has no v1-compatible release. The real story: on the v1 line the integration moved INTO drizzle-orm as the drizzle-orm/zod subpath (zod is an optional peer there; valibot/typebox/arktype moved the same way), and the standalone drizzle-zod package stays on 0.x — its v1 builds stopped in February when the validator packages were removed from the beta/rc branches. Verified against 1.0.0-rc.4: createSelectSchema/createInsertSchema derive working schemas from a sqliteTable and parse correctly. A new feature-detecting spec proves this on every canary run and skips on 0.x base lanes where the subpath does not exist. Docs-only + test-only: no release; also freshens the CLS-adapter links with the proposed fix (Papooch/nestjs-cls#604). Co-authored-by: Claude Fable 5 <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.
Closes #599.
drizzle-orm v1 is at
1.0.0-rc.4and the^0peer pin fails resolution for anyone installing the adapter next to it. The adapter itself is unaffected by v1's API changes —srchas nodrizzle-ormimport at all; the client is an opaque value — so the pin is the only blocker.Change (2 lines): peer range →
"^0 || >=1.0.0-rc.1 <2.0.0"+ the matchingyarn.lockentry. The explicit prerelease comparator is required because plain semver ranges never match prereleases (<2.0.0alone does not admit1.0.0-rc.4); the range also covers stable1.x, so GA needs no further change.Runtime evidence: nest-native/drizzle's CI runs a real commit/rollback through
TransactionalAdapterDrizzleOrm(viaClsPluginTransactional+@Transactional(), libSQL driver) againstdrizzle-orm@rcon every push — green on1.0.0-rc.4(spec, canary job).This package's own jest specs stay on the stable
0.45.xdevDependency, so CI here is unaffected. (They use RQB v1's{ schema }config, which v1 replaces with the relations API — worth migrating only if you want a dedicated v1 test lane; happy to follow up with that separately if useful.)