Version Packages (next) (#35)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: github-actions[bot]

.changeset/pre.json

@@ -6,6 +6,7 @@
   },
   "changesets": [
     "effect-v4-beta",
-    "insertable-null-and-jointable-fk"
+    "insertable-null-and-jointable-fk",
+    "legacy-customtype-detector"
   ]
 }

CHANGELOG.md

@@ -1,5 +1,26 @@
 # Changelog
 
+## 6.0.0-next.2
+
+### Patch Changes
+
+- ded938b: Warn on Effect 3 syntax in `@customType` annotations.
+
+  `@customType(...)` expressions are emitted verbatim, so an Effect 3 expression
+  (e.g. `Schema.Number.pipe(Schema.int(), Schema.between(1, 5))` or the variadic
+  `Schema.Union(A, B)`) compiles against Effect 3 but breaks against Effect 4. The
+  generator now scans `@customType` strings at `prisma generate` time and prints a
+  warning that names the field and the v4 replacement — for filters
+  (`Schema.int()` → `Schema.check(Schema.isInt())`, `Schema.between(a, b)` →
+  `Schema.check(Schema.isBetween({ minimum, maximum }))`, etc.), variadic
+  combinators (`Schema.Union(a, b)` → `Schema.Union([a, b])`), and removed schemas
+  (`Schema.UUID`, `Schema.DateFromSelf`). It only warns; it never rewrites the
+  expression (regex-transforming arbitrary user TypeScript is unsafe).
+
+  Also bumps the dev/test Effect pin to `4.0.0-beta.70` and documents that
+  consumers must pin the exact `6.0.0-next.x` version — a `"*"` range resolves to
+  the stable `5.x` line because npm/pnpm exclude prereleases from version ranges.
+
 ## 6.0.0-next.1
 
 ### Patch Changes

package.json

@@ -1,6 +1,6 @@
 {
   "name": "prisma-effect-kysely",
-  "version": "6.0.0-next.1",
+  "version": "6.0.0-next.2",
   "description": "Prisma generator that creates Effect Schema types from Prisma schema compatible with Kysely",
   "license": "MIT",
   "author": "Samuel Ho",