@tailor-platform/sdk 2.5.0 → 2.7.0

package/docs/cli-reference.md

@@ -386,22 +386,6 @@ Commands for managing crash reports.
 | [crashreport list](./cli/crashreport.md#crashreport-list) | List local crash report files.                 |
 | [crashreport send](./cli/crashreport.md#crashreport-send) | Submit a crash report to help improve the SDK. |
 
-### [Setup Commands](./cli/setup.md)
-
-Commands for setting up project infrastructure.
-
-| Command                                             | Description                                                                                      |
-| --------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
-| [setup](./cli/setup.md#setup)                       | Set up repository automation for your project. (beta)                                            |
-| [setup action](./cli/setup.md#setup-action)         | Generate a per-app composite action for use with setup coordinate (monorepo multi-app deploys).  |
-| [setup branch](./cli/setup.md#setup-branch)         | Generate a branch-target deploy workflow (push to branch triggers deploy).                       |
-| [setup check](./cli/setup.md#setup-check)           | Audit generated workflows for drift against the current config/repo (read-only).                 |
-| [setup coordinate](./cli/setup.md#setup-coordinate) | Generate a coordinator workflow that orchestrates multiple --action-generated composite actions. |
-| [setup delete](./cli/setup.md#setup-delete)         | Delete managed workflow/action file(s) and their .github/tailor.lock entries.                    |
-| [setup deps](./cli/setup.md#setup-deps)             | Generate a dependency update config for Tailor dependency and workflow updates.                  |
-| [setup preview](./cli/setup.md#setup-preview)       | Generate a preview workflow (PR open/sync triggers deploy to a per-PR workspace).                |
-| [setup tag](./cli/setup.md#setup-tag)               | Generate a tag-target deploy workflow (tag push triggers deploy).                                |
-
 ### [Upgrade Commands](./cli/upgrade.md)
 
 Commands for upgrading SDK versions with automated code migration.

package/docs/github-actions.md

@@ -7,6 +7,18 @@ application, including deploy workflows and Renovate configuration.
 > workflow, and the `.github/tailor.lock` schema may change before general
 > availability.
 
+## Installation
+
+The `setup` commands are provided by the `@tailor-platform/sdk-plugin-setup` CLI
+plugin. Install it next to the SDK:
+
+```bash
+npm install -D @tailor-platform/sdk-plugin-setup
+```
+
+The Tailor CLI discovers the plugin automatically from `node_modules/.bin` (or
+your `PATH`). Run `tailor plugin list` to confirm it resolves.
+
 ## Quick start
 
 Run the command from the root of your SDK project (where `tailor.config.ts`
@@ -383,9 +395,10 @@ standard root, `.github`, `.gitlab`, and `.renovaterc` locations, including the
 deprecated `package.json` configuration. When that configuration already extends
 the preset, the command reports that Renovate is set up and changes nothing.
 
-Configuration written in JSON5 or JSONC — with comments or trailing commas —
-cannot be edited without losing those comments, so the command leaves it
-unchanged and asks you to add the preset to its `extends` array yourself.
+JSONC and JSON5 configurations are updated in place while preserving their
+comments and formatting. Configurations that Renovate itself cannot load — such
+as invalid syntax, or duplicate keys outside JSON5 — are left unchanged and
+reported for manual inspection.
 
 `renovate.json` is yours to edit — it is not tracked in `.github/tailor.lock`.
 Add your own rules freely; re-running `tailor setup deps` does not overwrite

package/docs/migration/v2.md

@@ -661,7 +661,7 @@ After:
 ```ts
 ownerId: db.uuid().relation({
   type: "n-1",
-  toward: { type: user, as: "user" },
+  toward: { table: user, as: "user" },
 }),
 ```
 
@@ -1669,6 +1669,10 @@ The CLI stores human users by their stable subject ID instead of email (email is
 
 `tailor function logs` maps stack traces against the function bundle only when the execution recorded a `contentHash`. Executions without one now show raw stack traces instead of mapped frames. No source change is required.
 
+### `db.fields.timestamps()`: `updatedAt` becomes required
+
+The `updatedAt` field from `db.fields.timestamps()` changes from optional to required (non-null): it defaults to the current time and keeps refreshing automatically on every update, though a value you provide explicitly is still respected. Applying this change to a table that already has rows with `updatedAt: null` makes `deploy` fail with `field "updatedAt" cannot be updated from non-required to required when records with null values exist`. Backfill those rows first, e.g. `UPDATE <table> SET "updatedAt" = "createdAt" WHERE "updatedAt" IS NULL` for each affected table — see [TailorDB migrations](../services/tailordb-migration.md#performance-and-large-tables) for splitting a large backfill across primary-key ranges if a single `UPDATE` times out.
+
 ### Node.js minimum version raised to 22.15.0
 
 v2 requires Node.js **22.15.0** or later. This is the first version that includes `module.registerHooks()`, which the SDK uses to register its TypeScript loader hook synchronously in the main thread. The actual floor is now **22.18.0**: Node 22.15.0–22.17.x has a bug that crashes `tailor seed validate` when requiring `node:`-scheme-only builtins such as `node:sqlite`, fixed upstream by [nodejs/node#58612](https://github.com/nodejs/node/pull/58612) in 22.18.0. No source change is required; ensure your environment runs Node.js 22.18.0+.

package/docs/migration/v3.md

@@ -121,3 +121,42 @@ that merely mentions the option unchanged unless it documents a command to type.
 ```
 
 </details>
+
+## relation() toward.type → toward.table
+
+**Migration:** Partially automatic
+
+Rename the `.relation()` option `toward.type` to `toward.table`, matching the `db.type()` → `db.table()` rename. The relation's own `type` (its cardinality, e.g. `"n-1"`) is unchanged — only the target-table reference nested under `toward` moves.
+
+Before:
+
+```ts
+customerId: db.uuid().relation({
+  type: "n-1",
+  toward: { type: customer },
+}),
+```
+
+After:
+
+```ts
+customerId: db.uuid().relation({
+  type: "n-1",
+  toward: { table: customer },
+}),
+```
+
+<details>
+<summary>Prompt for an AI agent (to finish the cases the codemod could not migrate)</summary>
+
+```text
+In Tailor SDK v3, `.relation()`'s `toward.type` option is renamed to
+`toward.table` (it names a target table, not a TypeScript/GraphQL type).
+Rename any remaining `toward.type` the codemod did not rewrite (e.g. a
+`toward` object reached through a shared variable, spread, or computed
+key) to `toward.table`. Do not touch the relation's own outer `type`
+property, which is the relation's cardinality (e.g. "n-1", "1-1",
+"keyOnly") and keeps its name.
+```
+
+</details>

package/docs/services/tailordb-migration.md

@@ -757,6 +757,18 @@ The migration script runs in a single transaction. For tables with many rows:
 - Long-running transactions can hit platform timeouts and hold locks. For very large backfills, consider splitting the work across multiple migrations, each operating on a subset.
 - Add `LIMIT` and resumability (idempotent `where` clauses) so a re-run after a transient failure converges.
 
+### Migrations that take longer than a minute
+
+Migration scripts run as workflow jobs, so they are not bound by the 60-second
+limit that applies to synchronous script execution. `tailor deploy` waits for
+the migration and reports its logs as usual. Execution time is still bounded —
+a workflow job has its own, far longer, execution-time limit.
+
+The script still runs in a single transaction, so the guidance above about
+locks and transaction size continues to apply — prefer splitting a very large
+backfill across several migrations over holding one transaction open for a
+long time.
+
 ## Testing Migrations Locally
 
 ### Unit-testing migrate.ts

package/docs/services/tailordb.md

@@ -69,8 +69,8 @@ db.table("User", "User in the system", {
 | `db.float()`                      | Float    | number         |
 | [`db.decimal()`](#decimal-fields) | Decimal  | string         |
 | `db.bool()`                       | Boolean  | boolean        |
-| `db.date()`                       | Date     | string         |
-| `db.datetime()`                   | DateTime | string \| Date |
+| `db.date()`                       | Date     | Date \| string |
+| `db.datetime()`                   | DateTime | Date \| string |
 | `db.time()`                       | Time     | string         |
 | `db.uuid()`                       | UUID     | string         |
 | [`db.enum()`](#enum-fields)       | Enum     | string         |
@@ -182,18 +182,20 @@ const user = db.table("User", {
   name: db.string(),
   roleId: db.uuid().relation({
     type: "n-1",
-    toward: { type: role },
+    toward: { table: role },
   }),
 });
 ```
 
+`toward.type` is a deprecated alias for `toward.table` and will be removed in v3; `tailor upgrade` offers a codemod to rewrite it.
+
 For one-to-one relations, use `type: "1-1"`:
 
 ```typescript
 const userProfile = db.table("UserProfile", {
   userId: db.uuid().relation({
     type: "1-1",
-    toward: { type: user },
+    toward: { table: user },
   }),
   bio: db.string(),
 });
@@ -205,7 +207,7 @@ For foreign key constraint without creating a relation, use `type: "keyOnly"`:
 const user = db.table("User", {
   roleId: db.uuid().relation({
     type: "keyOnly",
-    toward: { type: role },
+    toward: { table: role },
   }),
 });
 ```
@@ -220,7 +222,7 @@ const user = db.table("User", {
 const userProfile = db.table("UserProfile", {
   userEmail: db.string().relation({
     type: "1-1",
-    toward: { type: user, key: "email", as: "user" },
+    toward: { table: user, key: "email", as: "user" },
   }),
 });
 ```
@@ -234,7 +236,7 @@ Customize relation names using `toward.as` / `backward` options:
 const userProfile = db.table("UserProfile", {
   userId: db.uuid().relation({
     type: "1-1",
-    toward: { type: user, as: "base" },
+    toward: { table: user, as: "base" },
     backward: "profile",
   }),
 });
@@ -266,12 +268,12 @@ removed. This lets multiple fields point to the same target table with distinct
 const post = db.table("Post", {
   authorID: db.uuid().relation({
     type: "n-1",
-    toward: { type: user },
+    toward: { table: user },
     backward: "authoredPosts",
   }),
   reviewerID: db.uuid().relation({
     type: "n-1",
-    toward: { type: user },
+    toward: { table: user },
     backward: "reviewedPosts",
   }),
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tailor-platform/sdk",
-  "version": "2.5.0",
+  "version": "2.7.0",
   "description": "Tailor Platform SDK - The SDK to work with Tailor Platform",
   "license": "MIT",
   "repository": {
@@ -149,14 +149,14 @@
     }
   },
   "dependencies": {
-    "@0no-co/graphql.web": "1.3.3",
+    "@0no-co/graphql.web": "1.3.4",
     "@badgateway/oauth2-client": "3.3.1",
     "@bufbuild/protobuf": "2.14.0",
     "@bufbuild/protovalidate": "1.2.0",
     "@connectrpc/connect": "2.1.2",
     "@connectrpc/connect-node": "2.1.2",
-    "@inquirer/core": "11.2.1",
-    "@inquirer/prompts": "8.5.2",
+    "@inquirer/core": "12.0.0",
+    "@inquirer/prompts": "8.6.0",
     "@jridgewell/trace-mapping": "0.3.31",
     "@napi-rs/keyring": "1.3.0",
     "@opentelemetry/api": "1.9.1",
@@ -164,7 +164,7 @@
     "@opentelemetry/resources": "2.10.0",
     "@opentelemetry/sdk-trace-node": "2.10.0",
     "@opentelemetry/semantic-conventions": "1.43.0",
-    "@oxc-project/types": "0.144.0",
+    "@oxc-project/types": "0.146.0",
     "@secretlint/core": "13.0.4",
     "@secretlint/secretlint-rule-preset-recommend": "13.0.4",
     "@standard-schema/spec": "1.1.0",
@@ -178,20 +178,20 @@
     "es-toolkit": "1.51.0",
     "find-up-simple": "1.0.1",
     "get-east-asian-width": "1.6.0",
-    "get-tsconfig": "4.14.2",
+    "get-tsconfig": "4.14.3",
     "globals": "17.11.0",
     "graphql": "17.0.2",
     "inflection": "3.0.2",
     "kysely": "0.29.5",
     "mime-types": "3.0.2",
     "open": "11.0.1",
-    "oxc-parser": "0.144.0",
+    "oxc-parser": "0.146.0",
     "p-limit": "7.3.1",
     "pathe": "2.0.3",
     "pgsql-ast-parser": "12.0.2",
     "pkg-types": "2.3.1",
-    "politty": "0.11.6",
-    "rolldown": "1.2.4",
+    "politty": "0.11.9",
+    "rolldown": "1.2.5",
     "semver": "7.8.5",
     "sql-highlight": "6.1.0",
     "std-env": "4.2.0",
@@ -206,15 +206,15 @@
     "@types/node": "24.13.3",
     "@types/semver": "7.8.0",
     "@typescript/native-preview": "7.0.0-dev.20260707.2",
-    "@vitest/coverage-v8": "4.1.10",
+    "@vitest/coverage-v8": "4.1.11",
     "eslint-plugin-zod": "4.9.1",
-    "oxfmt": "0.63.0",
-    "oxlint": "1.78.0",
+    "oxfmt": "0.64.0",
+    "oxlint": "1.79.0",
     "oxlint-tsgolint": "7.0.2001",
     "sonda": "0.14.0",
     "tsdown": "0.22.14",
     "typescript": "6.0.3",
-    "vitest": "4.1.10",
+    "vitest": "4.1.11",
     "zinfer": "0.2.8",
     "@tailor-platform/shared": "^0.0.0",
     "@tailor-platform/tailor-proto": "^0.0.1"
@@ -256,7 +256,6 @@
     "typecheck:go": "tsgo --tsBuildInfoFile ./.tsgo.tsbuildinfo",
     "perf:typecheck": "bash scripts/perf/exec.sh",
     "perf:runtime": "bash scripts/perf/runtime-perf.sh",
-    "prepublish": "pnpm run build",
     "postinstall": "node postinstall.mjs",
     "measure:bundle": "node ../../scripts/measure-bundle-size-sonda.js",
     "knip": "knip",

package/dist/application-DFOUovmN.mjs

@@ -1 +0,0 @@
-import{n as e,t}from"./application-D_4vg1KR.mjs";export{t as defineApplication,e as generatePluginFilesIfNeeded};