From 340ce938f667f94dd708a4b1d133efb29fa6961c Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Mon, 12 Oct 2026 23:55:34 +0000 Subject: [PATCH] chore: version packages --- .changeset/opt-in-tenant-enforcement.md | 5 ----- .changeset/pg-enums-unique-constraints.md | 5 ----- .changeset/runnable-typescript-5.md | 5 ----- CHANGELOG.md | 11 +++++++++++ package.json | 2 +- 5 files changed, 12 insertions(+), 16 deletions(-) delete mode 100644 .changeset/opt-in-tenant-enforcement.md delete mode 100644 .changeset/pg-enums-unique-constraints.md delete mode 100644 .changeset/runnable-typescript-5.md diff --git a/.changeset/opt-in-tenant-enforcement.md b/.changeset/opt-in-tenant-enforcement.md deleted file mode 100644 index c5f770a..0000000 --- a/.changeset/opt-in-tenant-enforcement.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@maple-dev/effect-orm": minor ---- - -Tenant scoping is now opt-in and enforceable. `fromSqlClient` / `layerSqlClient` take `requireTenantScope: true`, which refuses an undeclared `"cross-tenant"` statement with a `TenantScopeViolation` defect. Compiled queries carry `crossTenantDeclared` when the opt-out was explicit, and unions, inserts, updates and deletes gain `.crossTenant()`. `rawCompiledQuery`'s `tenantScope` is now optional and defaults to `"cross-tenant"`. diff --git a/.changeset/pg-enums-unique-constraints.md b/.changeset/pg-enums-unique-constraints.md deleted file mode 100644 index 15ed6c9..0000000 --- a/.changeset/pg-enums-unique-constraints.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@maple-dev/effect-orm": minor ---- - -Postgres enum types and unique constraints are first-class. `PG.enumType(name, labels, { schema? })` is a column type (rows decode to its labels; inserts and comparisons take only them; `nullable` and `array` wrap it, and enum arrays decode from the text form drivers send) and a schema object: `generate` creates the type before the tables that use it, adds labels with `ADD VALUE ... BEFORE`, renames one behind a `confirm_rename` hint, asks before dropping the type, and reports removing or reordering labels, or using a label in the migration that adds it, as unsupported. `PG.unique(name, columns, { nullsNotDistinct? })` in a table's `uniqueConstraints`, or `unique` in `PG.column` (named `__unique` by default), declares an `ADD CONSTRAINT ... UNIQUE` constraint, diffed as a constraint rather than an index. `verify` reads enums from `pg_enum` and unique constraints from `pg_constraint`, and resolves types of the current schema during its scratch rebuild, so `PG.custom("public.x", ...)` enums no longer report false drift. `generate --baseline --from-drizzle` converts drizzle-kit enums, enum columns and unique constraints. diff --git a/.changeset/runnable-typescript-5.md b/.changeset/runnable-typescript-5.md deleted file mode 100644 index 6225f6c..0000000 --- a/.changeset/runnable-typescript-5.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@maple-dev/effect-orm": patch ---- - -A concrete insert is assignable to `Runnable` (from `/database`) and accepted by `compile` under TypeScript 5.x again. Both took `CHInsert`, which TypeScript 5 compares method by method, and the generic `onConflictDoUpdate` failed that comparison; they now take an insert by its tag, state and phantom (`AnyInsert`). A workaround such as `type Runnable = Orm.Runnable | { readonly _tag: "CHInsert" }` can be removed. diff --git a/CHANGELOG.md b/CHANGELOG.md index 25719d0..8a400dd 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,16 @@ # @maple-dev/effect-orm +## 0.6.0 + +### Minor Changes + +- a379869: Tenant scoping is now opt-in and enforceable. `fromSqlClient` / `layerSqlClient` take `requireTenantScope: true`, which refuses an undeclared `"cross-tenant"` statement with a `TenantScopeViolation` defect. Compiled queries carry `crossTenantDeclared` when the opt-out was explicit, and unions, inserts, updates and deletes gain `.crossTenant()`. `rawCompiledQuery`'s `tenantScope` is now optional and defaults to `"cross-tenant"`. +- e26a29d: Postgres enum types and unique constraints are first-class. `PG.enumType(name, labels, { schema? })` is a column type (rows decode to its labels; inserts and comparisons take only them; `nullable` and `array` wrap it, and enum arrays decode from the text form drivers send) and a schema object: `generate` creates the type before the tables that use it, adds labels with `ADD VALUE ... BEFORE`, renames one behind a `confirm_rename` hint, asks before dropping the type, and reports removing or reordering labels, or using a label in the migration that adds it, as unsupported. `PG.unique(name, columns, { nullsNotDistinct? })` in a table's `uniqueConstraints`, or `unique` in `PG.column` (named `
__unique` by default), declares an `ADD CONSTRAINT ... UNIQUE` constraint, diffed as a constraint rather than an index. `verify` reads enums from `pg_enum` and unique constraints from `pg_constraint`, and resolves types of the current schema during its scratch rebuild, so `PG.custom("public.x", ...)` enums no longer report false drift. `generate --baseline --from-drizzle` converts drizzle-kit enums, enum columns and unique constraints. + +### Patch Changes + +- 852429b: A concrete insert is assignable to `Runnable` (from `/database`) and accepted by `compile` under TypeScript 5.x again. Both took `CHInsert`, which TypeScript 5 compares method by method, and the generic `onConflictDoUpdate` failed that comparison; they now take an insert by its tag, state and phantom (`AnyInsert`). A workaround such as `type Runnable = Orm.Runnable | { readonly _tag: "CHInsert" }` can be removed. + ## 0.4.0 - **Breaking:** definitions never throw. `CH.table`, `PG.table`, `CH.materializedView`, diff --git a/package.json b/package.json index 5a24338..cf43063 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@maple-dev/effect-orm", - "version": "0.5.0", + "version": "0.6.0", "description": "Type-safe ClickHouse and Postgres queries, result decoding, and reproducible benchmarks for Effect and TypeScript", "keywords": [ "clickhouse",