@prisma-next/extension-pgvector 0.12.0-dev.4 → 0.12.0-dev.40

package/README.md

@@ -200,16 +200,9 @@ The extension declares the following capabilities:
 
 ## Authoring (maintainers)
 
-The extension's contract + baseline migration are emitted on-disk inside this package using the same pipeline application authors use:
+After changing the contract source, run `pnpm migrations:regen` from the repo root to keep migration metadata, `refs/head.json`, and `end-contract.*` consistent with the freshly-built `src/contract.json`; it is also wired into `pnpm fixtures:emit` automatically.
 
-- `pnpm build:contract-space` — runs `prisma-next contract emit` to produce `src/contract.{json,d.ts}` from the TS source at `src/contract.ts`.
-- `pnpm exec prisma-next migration plan --name <slug>` (run from this package directory) — scaffolds a new migration directory under `migrations/<dirName>/` for schema changes that touch tables / models. **Not chained into `pnpm build`**: `migration plan` is non-idempotent (each invocation generates a new timestamped directory), so it runs manually when the contract source changes. Note: pgvector's contract declares only the parameterised `vector` native type under `storage.types` (no tables / models), so the planner currently refuses to scaffold the baseline migration with `PN-CLI-4020 Contract changed but planner produced no operations` (this is **Path B** authoring per [ADR 212](../../../docs/architecture%20docs/adrs/ADR%20212%20-%20Contract%20spaces.md#contract-space-package-layout)). That directory was hand-authored once (Migration subclass + seed `migration.json` preserving the full `toContract`) and `pnpm tsx migrations/<dirName>/migration.ts` re-emits `ops.json` + `migration.json` deterministically. Future migrations that add tables / models can use `migration plan` directly (Path A).
-- `pnpm tsx migrations/<dirName>/migration.ts` (run from this package directory) — re-emits `ops.json` + `migration.json` from the hand-edited subclass. Use `tsx`, not bare `node`, because the Migration subclass imports relative TypeScript siblings which Node's native loader can't resolve without a TS-aware loader.
-- `migrations/refs/head.json` is hand-pinned with the latest migration's `to` hash + `providedInvariants`.
-
-The descriptor at `src/exports/control.ts` then JSON-imports those artefacts and synthesises the framework's `MigrationPackage` shape.
-
-See [ADR 212 — Contract spaces](../../../docs/architecture%20docs/adrs/ADR%20212%20-%20Contract%20spaces.md) ("Contract-space package layout") for the canonical layout and rationale.
+See [ADR 212 — Contract spaces](../../../docs/architecture%20docs/adrs/ADR%20212%20-%20Contract%20spaces.md) ("Contract-space package layout") for the layout and rationale.
 
 ## References
 

package/package.json

@@ -1,39 +1,39 @@
 {
   "name": "@prisma-next/extension-pgvector",
-  "version": "0.12.0-dev.4",
+  "version": "0.12.0-dev.40",
   "license": "Apache-2.0",
   "type": "module",
   "sideEffects": false,
   "dependencies": {
-    "@prisma-next/contract": "0.12.0-dev.4",
-    "@prisma-next/contract-authoring": "0.12.0-dev.4",
-    "@prisma-next/family-sql": "0.12.0-dev.4",
-    "@prisma-next/framework-components": "0.12.0-dev.4",
-    "@prisma-next/migration-tools": "0.12.0-dev.4",
-    "@prisma-next/sql-contract": "0.12.0-dev.4",
-    "@prisma-next/sql-operations": "0.12.0-dev.4",
-    "@prisma-next/sql-relational-core": "0.12.0-dev.4",
-    "@prisma-next/sql-runtime": "0.12.0-dev.4",
-    "@prisma-next/sql-schema-ir": "0.12.0-dev.4",
+    "@prisma-next/contract": "0.12.0-dev.40",
+    "@prisma-next/contract-authoring": "0.12.0-dev.40",
+    "@prisma-next/family-sql": "0.12.0-dev.40",
+    "@prisma-next/framework-components": "0.12.0-dev.40",
+    "@prisma-next/migration-tools": "0.12.0-dev.40",
+    "@prisma-next/sql-contract": "0.12.0-dev.40",
+    "@prisma-next/sql-operations": "0.12.0-dev.40",
+    "@prisma-next/sql-relational-core": "0.12.0-dev.40",
+    "@prisma-next/sql-runtime": "0.12.0-dev.40",
+    "@prisma-next/sql-schema-ir": "0.12.0-dev.40",
     "@standard-schema/spec": "^1.1.0",
     "arktype": "^2.2.0"
   },
   "devDependencies": {
-    "@prisma-next/adapter-postgres": "0.12.0-dev.4",
-    "@prisma-next/cli": "0.12.0-dev.4",
-    "@prisma-next/operations": "0.12.0-dev.4",
-    "@prisma-next/postgres": "0.12.0-dev.4",
-    "@prisma-next/sql-contract-ts": "0.12.0-dev.4",
-    "@prisma-next/target-postgres": "0.12.0-dev.4",
-    "@prisma-next/test-utils": "0.12.0-dev.4",
-    "@prisma-next/tsconfig": "0.12.0-dev.4",
-    "@prisma-next/tsdown": "0.12.0-dev.4",
+    "@prisma-next/adapter-postgres": "0.12.0-dev.40",
+    "@prisma-next/cli": "0.12.0-dev.40",
+    "@prisma-next/operations": "0.12.0-dev.40",
+    "@prisma-next/postgres": "0.12.0-dev.40",
+    "@prisma-next/sql-contract-ts": "0.12.0-dev.40",
+    "@prisma-next/target-postgres": "0.12.0-dev.40",
+    "@prisma-next/test-utils": "0.12.0-dev.40",
+    "@prisma-next/tsconfig": "0.12.0-dev.40",
+    "@prisma-next/tsdown": "0.12.0-dev.40",
     "tsdown": "0.22.0",
     "typescript": "5.9.3",
     "vitest": "4.1.6"
   },
   "peerDependencies": {
-    "@prisma-next/adapter-postgres": "0.12.0-dev.4",
+    "@prisma-next/adapter-postgres": "0.12.0-dev.40",
     "typescript": ">=5.9"
   },
   "peerDependenciesMeta": {

package/src/contract.d.ts

@@ -23,7 +23,7 @@ import type {
 } from '@prisma-next/sql-contract/types';
 import type {
   Contract as ContractType,
-  ContractModelsMap,
+  ContractModelDefinitions,
   ExecutionHashBase,
   NamespaceId,
   ProfileHashBase,
@@ -108,7 +108,8 @@ type ContractBase = Omit<
   readonly profileHash: ProfileHash;
 };
 
+export type Models = ContractModelDefinitions<Contract>;
+
 export type Contract = ContractWithTypeMaps<ContractBase, TypeMaps>;
 
 export type Namespaces = Contract['storage']['namespaces'];
-export type Models = ContractModelsMap<Contract>;