@prisma-next/extension-paradedb 0.12.0-dev.36 → 0.12.0-dev.37

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +2 -9
  2. package/package.json +18 -18
package/README.md CHANGED
@@ -73,16 +73,9 @@ ParadeDB BM25 indexes require a `key_field` — a unique column that identifies
73
73
 
74
74
  ## Authoring (maintainers)
75
75
 
76
- The extension's contract + baseline migration are emitted on-disk inside this package using the same pipeline application authors use:
76
+ 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.
77
77
 
78
- - `pnpm build:contract-space` — runs `prisma-next contract emit` to produce `src/contract.{json,d.ts}` from `emptyContract({ output: 'src/contract.json', target })` in `prisma-next.config.ts` (migrations-only space: no `contract.prisma` source file).
79
- - `pnpm exec prisma-next migration plan --name <slug>` (run from this package directory) — scaffolds a new migration directory under `migrations/<dirName>/` for schema changes. **Not chained into `pnpm build`**: `migration plan` is non-idempotent (each invocation generates a new timestamped directory), so it runs manually when the contract changes. Note: paradedb's contract declares no tables or models, so the planner currently refuses to scaffold the baseline migration (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 or models can use `migration plan` directly (Path A).
80
- - `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.
81
- - `migrations/refs/head.json` is hand-pinned with the latest migration's `to` hash + `providedInvariants`.
82
-
83
- The descriptor at `src/exports/control.ts` then JSON-imports those artefacts and synthesises the framework's `MigrationPackage` shape.
84
-
85
- 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.
78
+ See [ADR 212 — Contract spaces](../../../docs/architecture%20docs/adrs/ADR%20212%20-%20Contract%20spaces.md) ("Contract-space package layout") for the layout and rationale.
86
79
 
87
80
  ## Not yet implemented
88
81
 
package/package.json CHANGED
@@ -1,30 +1,30 @@
1
1
  {
2
2
  "name": "@prisma-next/extension-paradedb",
3
- "version": "0.12.0-dev.36",
3
+ "version": "0.12.0-dev.37",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "sideEffects": false,
7
7
  "dependencies": {
8
- "@prisma-next/contract": "0.12.0-dev.36",
9
- "@prisma-next/contract-authoring": "0.12.0-dev.36",
10
- "@prisma-next/family-sql": "0.12.0-dev.36",
11
- "@prisma-next/framework-components": "0.12.0-dev.36",
12
- "@prisma-next/migration-tools": "0.12.0-dev.36",
13
- "@prisma-next/sql-contract": "0.12.0-dev.36",
14
- "@prisma-next/sql-operations": "0.12.0-dev.36",
15
- "@prisma-next/sql-relational-core": "0.12.0-dev.36",
16
- "@prisma-next/sql-runtime": "0.12.0-dev.36",
8
+ "@prisma-next/contract": "0.12.0-dev.37",
9
+ "@prisma-next/contract-authoring": "0.12.0-dev.37",
10
+ "@prisma-next/family-sql": "0.12.0-dev.37",
11
+ "@prisma-next/framework-components": "0.12.0-dev.37",
12
+ "@prisma-next/migration-tools": "0.12.0-dev.37",
13
+ "@prisma-next/sql-contract": "0.12.0-dev.37",
14
+ "@prisma-next/sql-operations": "0.12.0-dev.37",
15
+ "@prisma-next/sql-relational-core": "0.12.0-dev.37",
16
+ "@prisma-next/sql-runtime": "0.12.0-dev.37",
17
17
  "arktype": "^2.2.0"
18
18
  },
19
19
  "devDependencies": {
20
- "@prisma-next/adapter-postgres": "0.12.0-dev.36",
21
- "@prisma-next/cli": "0.12.0-dev.36",
22
- "@prisma-next/operations": "0.12.0-dev.36",
23
- "@prisma-next/sql-contract-ts": "0.12.0-dev.36",
24
- "@prisma-next/target-postgres": "0.12.0-dev.36",
25
- "@prisma-next/test-utils": "0.12.0-dev.36",
26
- "@prisma-next/tsconfig": "0.12.0-dev.36",
27
- "@prisma-next/tsdown": "0.12.0-dev.36",
20
+ "@prisma-next/adapter-postgres": "0.12.0-dev.37",
21
+ "@prisma-next/cli": "0.12.0-dev.37",
22
+ "@prisma-next/operations": "0.12.0-dev.37",
23
+ "@prisma-next/sql-contract-ts": "0.12.0-dev.37",
24
+ "@prisma-next/target-postgres": "0.12.0-dev.37",
25
+ "@prisma-next/test-utils": "0.12.0-dev.37",
26
+ "@prisma-next/tsconfig": "0.12.0-dev.37",
27
+ "@prisma-next/tsdown": "0.12.0-dev.37",
28
28
  "tsdown": "0.22.0",
29
29
  "typescript": "5.9.3",
30
30
  "vitest": "4.1.6"