turbine-orm 0.67.0 → 0.70.0

package/dist/cli/migrate.d.ts

@@ -11,9 +11,9 @@
  *   -- DOWN
  *   DROP TABLE users;
  */
-import pg from 'pg';
 import type { DatabaseAdapter } from '../adapters/index.js';
 import { type Dialect } from '../dialect.js';
+import type { PgCompatQueryResult } from '../pg-types.js';
 import { type DestructiveStatement } from './destructive.js';
 import { splitSqlStatements } from './sql-statements.js';
 /**
@@ -289,6 +289,23 @@ export interface MigrationLockClient {
     query(sql: string, params?: unknown[]): Promise<unknown>;
     end(): Promise<void>;
 }
+/**
+ * The ROW-RETURNING query surface the runner needs, for the paths that read the
+ * tracking table back rather than just issuing a statement.
+ *
+ * Deliberately not `PgCompatPoolClient`: this connection is a `pg.Client`,
+ * which has no `release()`, so the pooled-client interface does not fit. Naming
+ * the driver type itself would put a pg module import back into the published
+ * declarations, which is what `src/pg-types.ts` exists to prevent, and it is
+ * also why this comment does not spell that import form out: the `consumer-types`
+ * CI job greps the built `.d.ts` files for it and cannot tell prose from code.
+ * `pg.Client` satisfies this structurally; tests supply a fake.
+ *
+ * @internal
+ */
+export interface MigrationQueryClient {
+    query<R = Record<string, unknown>>(sql: string, params?: unknown[]): Promise<PgCompatQueryResult<R>>;
+}
 /** A held (or refused) migration lock, and whatever must be released with it. */
 export interface MigrationLock {
     /** False when another migration already holds the lock. */
@@ -373,7 +390,7 @@ export interface MigrationDeployPlan {
  *
  * @internal exported for tests; not part of the CLI's public surface.
  */
-export declare function validateChecksums(client: pg.Client, migrationsDir: string, dialect?: Dialect): Promise<ChecksumMismatch[]>;
+export declare function validateChecksums(client: MigrationQueryClient, migrationsDir: string, dialect?: Dialect): Promise<ChecksumMismatch[]>;
 export declare function formatChecksumMismatchError(mismatches: ChecksumMismatch[]): string;
 /**
  * Build a deploy plan from local migration files and applied migration rows.

package/dist/cli/observe.d.ts

@@ -6,7 +6,7 @@
  * random token, HttpOnly cookie, CSP headers, read-only transactions.
  */
 import { type IncomingMessage, type ServerResponse } from 'node:http';
-import pg from 'pg';
+import type { PgCompatPool } from '../pg-types.js';
 export interface ObserveOptions {
     url: string;
     port: number;
@@ -19,7 +19,7 @@ export interface ObserveServerHandle {
     url: string;
 }
 export declare function startObserve(options: ObserveOptions): Promise<ObserveServerHandle>;
-export declare function handleRequest(req: IncomingMessage, res: ServerResponse, pool: pg.Pool, options: ObserveOptions, authToken: string, rateLimiter: Map<string, {
+export declare function handleRequest(req: IncomingMessage, res: ServerResponse, pool: PgCompatPool, options: ObserveOptions, authToken: string, rateLimiter: Map<string, {
     count: number;
     resetAt: number;
 }>): Promise<void>;

package/dist/cli/observe.js

@@ -170,7 +170,16 @@ async function apiLatency(res, pool, params) {
         try {
             await client.query('ROLLBACK');
         }
-        catch { }
+        catch {
+            // Deliberately swallowed, and only this one. `err` above is the failure
+            // worth reporting and it is what the 500 below carries; a ROLLBACK that
+            // also fails means the connection is already gone, which node-postgres
+            // handles by discarding the client on the release() in `finally`.
+            // Surfacing it instead would replace a real diagnosis ("statement
+            // timeout", "relation does not exist") with "connection terminated", and
+            // this server writes no log of its own, so the HTTP response is the only
+            // channel either error could reach. Same shape as cli/studio.ts.
+        }
         sendJson(res, 500, { error: err instanceof Error ? err.message : String(err) });
     }
     finally {
@@ -202,7 +211,16 @@ async function apiModels(res, pool, params) {
         try {
             await client.query('ROLLBACK');
         }
-        catch { }
+        catch {
+            // Deliberately swallowed, and only this one. `err` above is the failure
+            // worth reporting and it is what the 500 below carries; a ROLLBACK that
+            // also fails means the connection is already gone, which node-postgres
+            // handles by discarding the client on the release() in `finally`.
+            // Surfacing it instead would replace a real diagnosis ("statement
+            // timeout", "relation does not exist") with "connection terminated", and
+            // this server writes no log of its own, so the HTTP response is the only
+            // channel either error could reach. Same shape as cli/studio.ts.
+        }
         sendJson(res, 500, { error: err instanceof Error ? err.message : String(err) });
     }
     finally {

package/dist/cli/pii-predicate-guard.d.ts

@@ -55,8 +55,12 @@ import type { SchemaMetadata, TableMetadata } from '../schema.js';
  * Copy 2 belongs to the SQL compiler and cannot import this one (a query-path
  * module must not depend on `cli/`), so the deduplication has to go the other
  * way: the list wants to live in `query/filters.ts` and be imported here, the
- * way {@link COLUMN_REF_OPERATORS} above now is. Until that export exists this
- * comment is the only thing holding the three in step.
+ * way {@link COLUMN_REF_OPERATORS} above now is.
+ *
+ * That destination now EXISTS (`RELATION_FILTER_WRAPPERS` in `query/filters.ts`)
+ * and nothing imports it, including this file, so it is a fourth copy rather
+ * than a deduplication and this comment is still the only thing holding them in
+ * step. Moving each walk onto it is a change per walk, each with its own tests.
  */
 export declare const RELATION_FILTER_WRAPPERS: readonly ["some", "none", "every", "is", "isNot"];
 /**

package/dist/cli/pii-predicate-guard.js

@@ -56,8 +56,12 @@ import { ownLookup } from '../query/utils.js';
  * Copy 2 belongs to the SQL compiler and cannot import this one (a query-path
  * module must not depend on `cli/`), so the deduplication has to go the other
  * way: the list wants to live in `query/filters.ts` and be imported here, the
- * way {@link COLUMN_REF_OPERATORS} above now is. Until that export exists this
- * comment is the only thing holding the three in step.
+ * way {@link COLUMN_REF_OPERATORS} above now is.
+ *
+ * That destination now EXISTS (`RELATION_FILTER_WRAPPERS` in `query/filters.ts`)
+ * and nothing imports it, including this file, so it is a fourth copy rather
+ * than a deduplication and this comment is still the only thing holding them in
+ * step. Moving each walk onto it is a change per walk, each with its own tests.
  */
 export const RELATION_FILTER_WRAPPERS = ['some', 'none', 'every', 'is', 'isNot'];
 const RELATION_FILTER_WRAPPER_SET = new Set(RELATION_FILTER_WRAPPERS);