@tailor-platform/sdk 2.36.0 → 2.38.0

package/docs/testing.md

@@ -18,14 +18,14 @@ Unit-test entrypoints exposed by the SDK:
 - `resolver.body({ input, caller, invoker, env })` — invoke a resolver
 - `workflowJob.body(input, { env, invoker })` — invoke a workflow job body directly
 - `workflowJob.start(input)` — chain a workflow job through the workflow runtime
-- `runWorkflowLocally(workflow, args)` — run a workflow chain locally with real job bodies
+- `runWorkflowLocally(workflow, args)` (Beta) — run a workflow chain locally with real job bodies
 - `executor.operation.body({ ...args, invoker })` — invoke a function-kind executor
 
 For anonymous direct calls:
 
 - Pass `null` for anonymous `caller` / `invoker` context in direct unit tests.
 
-Platform API mocks under `@tailor-platform/sdk/vitest` (for use with the [`tailor-runtime` Vitest environment](#runtime-environment-emulation-beta) below):
+Platform API mocks under `@tailor-platform/sdk/vitest` (Beta), for use with the [`tailor-runtime` Vitest environment](#runtime-environment-emulation-beta) below:
 
 - `mockTailordb` — TailorDB query stubs and call recording
 - `mockTailordbWithPGlite` — TailorDB backed by a real in-memory Postgres (PGlite)
@@ -214,7 +214,6 @@ The generated columns follow the Kysely types, not TailorDB's storage: `text` fo
 What the script cannot reproduce:
 
 - Hooks, validations, and permissions do not run. A required field whose value only its own field-level create hook supplies is created nullable, so inserts that omit it succeed; give it a `.default()` if the test reads it back. A field filled by a table-level hook stays `NOT NULL`, as its Kysely type still requires it on insert.
-- Serial formats are reproduced for a single `%d`, `%x`, or `%X` specifier with an optional zero-padded width; an octal `%o` format fails generation with an error naming the field.
 - `gapless` is not reproduced: the numbers come from a sequence, so an insert that fails still uses up its number.
 - A date or datetime inside a nested object reads back as a string from `jsonb`, not a `Date`, or a `Temporal.PlainDate` or `Temporal.Instant` under `kyselyTypePlugin({ temporal: true })`, although the platform returns those types.
 - A `.unique()` date, datetime, or time inside a nested object compares the stored text, so two spellings of the same instant (`2026-01-01T00:00:00Z` and `2026-01-01T01:00:00+01:00`) are both accepted, although the platform rejects the second. Use one spelling in tests.
@@ -227,7 +226,7 @@ To hand-write DDL instead — for a table not in the schema, or to add a constra
 - Seed through `getDB` itself. When a column type rejects a value that only the test must stage, use `createKyselyPGlite<Unmigrated<...>>(pglite)` instead — see [Testing Migrations Locally](./services/tailordb/migration.md#testing-migrations-locally). This only affects test setup; it cannot supply a `.serial()` value for an insert issued by the code under test.
 - With `kyselyTypePlugin({ temporal: true })`, the generated `getDB` reads top-level date, datetime, and time columns back from PGlite as `Temporal.PlainDate`, `Temporal.Instant`, and `Temporal.PlainTime`, as it does on the platform. Values inside nested objects stay strings in PGlite (see above); on the platform, nested date/datetime fields are Temporal values while nested time fields remain strings.
 - Transactions on a shared instance are serialized: while one is open, queries from other `getDB` instances wait. Do not use `test.concurrent` with a shared instance, and do not query the same instance through a second `getDB` from inside a transaction — that waits on itself.
-- PGlite runs full PostgreSQL while TailorDB supports a subset of it, and TailorDB hooks, validations, and permissions do not run here — a test passing on PGlite can still behave differently on the platform. Keep [`mockTailordb`](#tailordb-mock) or [`createKyselyMock`](#kysely-layer-mock-createkyselymock) tests for query shape and error paths, and E2E tests for platform behavior.
+- PGlite runs full PostgreSQL while TailorDB supports a subset of it, and TailorDB hooks, validations, and permissions do not run here — a test passing on PGlite can still behave differently on the platform. Keep [`mockTailordb`](#tailordb-mock) or [`createKyselyMock`](#kysely-layer-mock-createkyselymock-beta) tests for query shape and error paths, and E2E tests for platform behavior.
 
 ### Workflow Mock
 
@@ -642,7 +641,7 @@ describe("decrementUserAge", () => {
 
 **Use when:** multi-step business logic. The tests survive query rewrites because they assert high-level intent, not SQL shape.
 
-#### Kysely-layer mock (`createKyselyMock`)
+#### Kysely-layer mock (`createKyselyMock`) (Beta)
 
 `createKyselyMock` returns a real Kysely instance whose execution is mocked. Stage the rows each query returns, run your code, then assert what it did — each query's SQL and parameters, how many `selects`/`inserts`/`updates`/`deletes` ran, and the value your code returned. Queries stay fully typed and compile to the same SQL as production.
 
@@ -697,7 +696,7 @@ Reach for [`mockTailordb`](#mocking-the-tailordb-client) instead when you want t
 
 TailorDB migration scripts (`migrate.ts`) are unit-tested the same way: the generated `db.ts` exports the `Database` interface to type the mock, and `tailor tailordb migration script <N> --with-test` scaffolds a ready-to-fill test. To execute a migration script against real rows in an in-memory Postgres, use `createKyselyPGlite` with `@electric-sql/pglite` and the generated `db.pglite.ts` schema. See [Testing Migrations Locally](./services/tailordb/migration.md#testing-migrations-locally).
 
-#### Resolvers that resume a workflow
+#### Resolvers that resume a workflow (Beta)
 
 Resolvers that call `waitPoint.resolve(...)` delegate to `tailor.workflow.resolve` at runtime. With the `tailor-runtime` environment active, use `mockWorkflow().waitPoint(definition)` to invoke the callback with the payload that originally suspended the job:
 
@@ -731,7 +730,7 @@ describe("resolveApproval resolver", () => {
 
 `setResolvePayload` is typed from the wait-point definition. The lower-level `setResolveHandler` and `resolveCalls` APIs remain available when a test must control several wait points together.
 
-#### Resolvers that resume failed workflows
+#### Resolvers that resume failed workflows (Beta)
 
 Resolvers or executors that call `workflow.resumeWorkflowExecution(executionId)` delegate to `tailor.workflow.resumeWorkflowExecution` at runtime. With the `tailor-runtime` environment active, use `mockWorkflow().setResumeHandler` to control the returned execution ID and inspect `resumeWorkflowExecution.mock.calls`:
 
@@ -838,7 +837,7 @@ describe("validateOrder", () => {
 });
 ```
 
-#### Jobs that start other jobs
+#### Jobs that start other jobs (Beta)
 
 Use `mockWorkflow().job(definition)` to replace dependent jobs with deterministic results:
 
@@ -878,7 +877,7 @@ describe("fulfillOrder", () => {
 
 **Use when:** you want to isolate the orchestrating job from its dependencies.
 
-#### Jobs that wait on approval
+#### Jobs that wait on approval (Beta)
 
 `.wait()` calls delegate to `tailor.workflow.wait`. With the `tailor-runtime` environment active, use `mockWorkflow().waitPoint(definition)` to drive each branch with a typed mock:
 
@@ -921,7 +920,7 @@ describe("processWithApproval", () => {
 
 The lower-level `setWaitHandler` and `waitCalls` APIs remain available when one handler must cover several wait points.
 
-#### Running a full workflow locally
+#### Running a full workflow locally (Beta)
 
 To exercise the full chain with real job bodies, call `runWorkflowLocally(workflow, args)`. Dependent jobs run their real `.body()` functions, and start args/results cross the same JSON boundary as the platform, so a non-serializable payload fails the test exactly as it would in production:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tailor-platform/sdk",
-  "version": "2.36.0",
+  "version": "2.38.0",
   "description": "Tailor Platform SDK - The SDK to work with Tailor Platform",
   "license": "MIT",
   "repository": {
@@ -151,6 +151,9 @@
       "types": "./dist/runtime/logger.d.mts",
       "import": "./dist/runtime/logger.mjs",
       "default": "./dist/runtime/logger.mjs"
+    },
+    "./vendor/graphql/*": {
+      "types": "./dist/vendor/graphql/*.d.mts"
     }
   },
   "dependencies": {
@@ -160,8 +163,11 @@
     "@bufbuild/protovalidate": "1.3.0",
     "@connectrpc/connect": "2.2.0",
     "@connectrpc/connect-node": "2.2.0",
-    "@inquirer/core": "12.0.5",
-    "@inquirer/prompts": "8.7.4",
+    "@enlumine/graphql": "0.2.0",
+    "@enlumine/sql": "0.2.0",
+    "@enlumine/terminal": "0.2.0",
+    "@inquirer/core": "12.0.6",
+    "@inquirer/prompts": "8.7.5",
     "@jridgewell/trace-mapping": "0.3.31",
     "@napi-rs/keyring": "2.1.2",
     "@opentelemetry/api": "1.10.0",
@@ -170,36 +176,33 @@
     "@opentelemetry/resources": "3.0.0",
     "@opentelemetry/sdk-trace": "3.0.0",
     "@opentelemetry/semantic-conventions": "1.43.0",
-    "@oxc-project/types": "0.155.0",
+    "@oxc-project/types": "0.156.0",
     "@politty/zod": "0.6.3",
-    "@secretlint/core": "13.0.7",
-    "@secretlint/secretlint-rule-preset-recommend": "13.0.7",
+    "@secretlint/core": "13.1.0",
+    "@secretlint/secretlint-rule-preset-recommend": "13.1.0",
     "@standard-schema/spec": "1.1.0",
     "@tailor-platform/function-kysely-tailordb": "0.1.3",
     "@toiroakr/read-multiline": "0.4.3",
-    "@urql/core": "6.0.3",
-    "amaro": "1.2.2",
-    "confbox": "0.3.1",
+    "amaro": "1.3.0",
+    "confbox": "0.3.2",
     "date-fns": "4.4.0",
-    "es-toolkit": "1.53.0",
+    "es-toolkit": "1.53.1",
     "find-up-simple": "1.0.1",
     "get-east-asian-width": "1.7.0",
     "get-tsconfig": "4.14.3",
     "globals": "17.13.0",
-    "graphql": "17.0.2",
     "inflection": "3.0.2",
     "kysely": "0.29.7",
-    "lines-db": "0.18.0",
+    "lines-db": "0.18.1",
     "mime-types": "3.0.2",
     "open": "11.0.4",
-    "oxc-parser": "0.155.0",
+    "oxc-parser": "0.156.0",
     "p-limit": "7.3.3",
     "pathe": "2.0.3",
     "pgsql-ast-parser": "12.0.2",
     "pkg-types": "2.4.0",
     "rolldown": "1.2.15",
     "semver": "7.8.5",
-    "sql-highlight": "6.1.0",
     "std-env": "4.3.0",
     "temporal-polyfill": "1.0.6",
     "temporal-spec": "1.0.1",
@@ -210,16 +213,17 @@
   },
   "devDependencies": {
     "@ark/attest": "0.58.0",
-    "@electric-sql/pglite": "0.5.11",
+    "@electric-sql/pglite": "0.5.14",
     "@tailor-platform/shared": "^0.0.0",
     "@tailor-platform/tailor-proto": "^0.0.1",
     "@types/mime-types": "3.0.1",
-    "@types/node": "24.19.2",
+    "@types/node": "26.6.6",
     "@types/semver": "7.8.0",
     "@vitest/coverage-v8": "5.0.5",
     "eslint-plugin-zod": "5.2.2",
-    "oxfmt": "0.74.0",
-    "oxlint": "1.89.0",
+    "graphql": "17.0.2",
+    "oxfmt": "0.75.0",
+    "oxlint": "1.90.0",
     "oxlint-tsgolint": "7.0.2005",
     "sonda": "0.14.0",
     "tsdown": "0.23.2",
@@ -227,7 +231,7 @@
     "tsx": "4.23.15",
     "typescript": "6.0.3",
     "vitest": "5.0.5",
-    "zinfer": "0.4.7"
+    "zinfer": "0.5.2"
   },
   "peerDependencies": {
     "@electric-sql/pglite": ">=0.2.0",