Skip to content

beta#263

Draft
0xcadams wants to merge 17 commits into
mainfrom
beta
Draft

beta#263
0xcadams wants to merge 17 commits into
mainfrom
beta

Conversation

@0xcadams

@0xcadams 0xcadams commented Mar 27, 2026

Copy link
Copy Markdown
Member

This PR is tracking the upcoming drizzle-orm v2 relations and beta releases.

Install this version with:

npm install drizzle-zero@beta drizzle-orm@beta
# or
bun add drizzle-zero@beta drizzle-orm@beta
# or
yarn add drizzle-zero@beta drizzle-orm@beta
# or
pnpm add drizzle-zero@beta drizzle-orm@beta

Feel free to leave comments on this PR.

@0xcadams

0xcadams commented Mar 27, 2026

Copy link
Copy Markdown
Member Author

A new version, drizzle-zero@1.0.0-beta.0, has been published to npm: https://www.npmjs.com/package/drizzle-zero?activeTab=versions

(this is now outdated, see below)

@typedrat

Copy link
Copy Markdown

The PR I was going to submit does some gymnastics to simultaneously support either V1 or V2 tables, if you would like me to link you to the code.

@0xcadams

Copy link
Copy Markdown
Member Author

It became too complex to support both. I wanted that and started down that road, but the code was too complex.

0xcadams and others added 15 commits July 13, 2026 12:01
Pin the workspace to drizzle-orm and drizzle-kit 1.0.0-beta.19 so the repo is aligned on the beta-only migration target. Move drizzle-zero onto a prerelease version to land the breaking change on a dedicated release line.
Centralize beta Drizzle column normalization so the rest of the migration can resolve arrays, enums, and extended data types consistently. This keeps runtime type resolution stable while moving away from legacy column internals.
Move the type-level column mapping onto beta Column metadata so custom types, enums, arrays, and logical Zero defaults are resolved from built columns instead of legacy internals. This keeps the migration aligned across tables and schema type helpers before the runtime table builder switches over.
Route Zero table generation through the beta column helpers so arrays, enums, and SQL fallbacks resolve consistently at runtime. This preserves the existing table-shaping rules while moving the runtime path off legacy Drizzle type assumptions.
Build relationships from beta defineRelations and defineRelationsPart exports so direct and through hops share one normalization path. Drop legacy relations and removed manyToMany config support to align the schema generator with the beta-only release target.
Move the relation fixture suite onto defineRelations and through so the regression coverage matches the beta-only schema format. Remove legacy manyToMany and reverse-inference fixtures to keep the remaining tests focused on the supported relation model.
Move the integration schema and generator paths onto beta defineRelations and through so generated relationships come from the supported Drizzle 1.0 model. Fix the related custom-type regressions for nullable string enums and array-typed jsonb fields so the generated Zero schema stays stable.
Update the README to document the beta-only relation APIs, through-based many-to-many setup, and the removed legacy configuration paths. Add explicit upgrade notes so users can move from legacy relations onto the supported Drizzle beta workflow.
@socket-security

socket-security Bot commented Jul 13, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updateddrizzle-orm@​0.45.2 ⏵ 1.0.0-beta.1998 +1085 -1588 +199 +3100
Addeddrizzle-kit@​1.0.0-beta.19881009699100

View full report

@socket-security

socket-security Bot commented Jul 13, 2026

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm drizzle-kit is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: db/package.jsonnpm/drizzle-kit@1.0.0-beta.19

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/drizzle-kit@1.0.0-beta.19. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@0xcadams
0xcadams deployed to drizzle-zero-release-npm July 13, 2026 19:49 — with GitHub Actions Active
@0xcadams

Copy link
Copy Markdown
Member Author

1.0.0-beta.1 has been published.

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.

2 participants