@tailor-platform/sdk 2.3.0 → 2.5.0

package/CHANGELOG.md

@@ -1,5 +1,176 @@
 # @tailor-platform/sdk
 
+## 2.5.0
+
+### Minor Changes
+
+- [#2076](https://github.com/tailor-platform/sdk/pull/2076) [`d4a23f0`](https://github.com/tailor-platform/sdk/commit/d4a23f05dfe7044db69fd3f58f7653619ef4607e) Thanks [@dqn](https://github.com/dqn)! - Add `tailor function script`, which scaffolds a one-off script executed by `tailor function run` without deploying. By default, the skeleton imports the project's generated `getDB()` when `kyselyTypePlugin` is configured; without the plugin, the command generates a script-scoped `db.ts` and `db.snapshot.json` from local table definitions. Pass `--remote` to generate those script-scoped files from a deployed or external namespace instead. `function run` refuses to execute the script when that snapshot no longer matches the deployed or locally defined table and field structure (override with `--allow-schema-drift`).
+
+- [#2103](https://github.com/tailor-platform/sdk/pull/2103) [`0578df4`](https://github.com/tailor-platform/sdk/commit/0578df4bed1b82a6ee1fa775ec3cdecac0d81d48) Thanks [@toiroakr](https://github.com/toiroakr)! - Add `PluginConfigRegistry` to `@tailor-platform/sdk/plugin`, an interface builtin plugins extend via declaration merging to register their config type under their own id. `kyselyTypePlugin` and `seedPlugin` now register through it.
+
+- [#2088](https://github.com/tailor-platform/sdk/pull/2088) [`c9f91d9`](https://github.com/tailor-platform/sdk/commit/c9f91d944e4b041250979ec4438c36cabf818e14) Thanks [@dqn](https://github.com/dqn)! - The `--branch` option of `tailor setup branch` is renamed to `--target`, so it no longer collides with the subcommand name. The old spelling keeps working as a deprecated alias until v3 and prints a deprecation warning when used; `tailor upgrade` offers the `v3/setup-branch-flag-rename` codemod to rewrite `setup branch --branch` invocations across package.json scripts, shell and Windows scripts, YAML, Markdown, and JavaScript/TypeScript sources. The `--branch` option of `setup tag`, `setup preview`, and `setup coordinate` is unchanged.
+
+- [#2110](https://github.com/tailor-platform/sdk/pull/2110) [`fca0ff0`](https://github.com/tailor-platform/sdk/commit/fca0ff0a951a683cf5760b9cc693c19987ca8b36) Thanks [@dqn](https://github.com/dqn)! - **Breaking change (beta)**: Rename `tailor setup renovate` to `tailor setup deps`, which selects the dependency update provider with `--provider` (currently `renovate`, the default).
+
+- [#2124](https://github.com/tailor-platform/sdk/pull/2124) [`e8e8097`](https://github.com/tailor-platform/sdk/commit/e8e8097eb9cd08523f545df114379f7848293168) Thanks [@dqn](https://github.com/dqn)! - **Breaking change (beta)**: Rename the remaining TailorDB identifiers that named a `db.table()` definition a type:
+  
+  - record trigger config `typeName` → `tableName`
+  - `PluginRecordTriggerConfig.typeName` → `tableName`
+  - generator auth input `userProfile.typeName` → `tableName`
+  - `mockFile().calls[]` entries expose `tableName`
+  - `tailordb.file` runtime parameters and their JSDoc
+  
+  Update custom plugins that build a record trigger config, and test assertions that read `mockFile().calls[].typeName`. Executor runtime args keep `typeName`, since that is the key the platform sends into a deployed executor; the proto `type_name` wire field, TRN `type` segments, and the `.typeName()` field builder are unchanged.
+
+- [#2067](https://github.com/tailor-platform/sdk/pull/2067) [`a2e431f`](https://github.com/tailor-platform/sdk/commit/a2e431fe068a956123c00b100467c7083f9f2e08) Thanks [@dqn](https://github.com/dqn)! - Add `tailor tailordb migration generate --data-only` to create a migration with no schema changes that exists to run a data transformation script. Pass `--namespace` to pick the target when more than one namespace configures migrations.
+
+### Patch Changes
+
+- [#2128](https://github.com/tailor-platform/sdk/pull/2128) [`2a97723`](https://github.com/tailor-platform/sdk/commit/2a977238325a20f5b2c7d525ed4fec535108c175) Thanks [@dqn](https://github.com/dqn)! - Simplify how build-only resolver bundles are merged across config files. No observable behavior change.
+
+- [#2087](https://github.com/tailor-platform/sdk/pull/2087) [`e98a03d`](https://github.com/tailor-platform/sdk/commit/e98a03dc3f2638f439c766afe76342111ecde452) Thanks [@toiroakr](https://github.com/toiroakr)! - Deprecate `execJobFunction` on the `workflow` value imported from `@tailor-platform/sdk/runtime`(`/workflow`); it is removed in v3. Calling a workflow job by name through it has no working use — the build already rejects a direct call to it from inside a job body — so call the target job's own `.start()` method instead. The ambient `tailor.workflow.execJobFunction` global (what `.start()` itself compiles down to) is unaffected.
+
+- [#2134](https://github.com/tailor-platform/sdk/pull/2134) [`46e2b6e`](https://github.com/tailor-platform/sdk/commit/46e2b6e386daba1c3a9b72395ebd6e7c7c5095ce) Thanks [@dqn](https://github.com/dqn)! - Prevent unchanged Executor, pipeline resolver, Auth IdP, user-profile, and tenant-provider resources from appearing as updates when the platform returns omitted fields with their default values.
+
+- [#2110](https://github.com/tailor-platform/sdk/pull/2110) [`a588f78`](https://github.com/tailor-platform/sdk/commit/a588f7823a46581d649776f866962f2689417bb6) Thanks [@dqn](https://github.com/dqn)! - Fix the missing deprecation warning for `tailor function test-run` when a global option precedes the subcommand, such as `tailor function --json test-run`.
+
+- [#2138](https://github.com/tailor-platform/sdk/pull/2138) [`870c8cd`](https://github.com/tailor-platform/sdk/commit/870c8cdaa007adcbb8f565fe9b4d238d98c00e6d) Thanks [@dqn](https://github.com/dqn)! - Stop exporting internal declarations that were only used within their own module.
+
+- [#2102](https://github.com/tailor-platform/sdk/pull/2102) [`4f017f2`](https://github.com/tailor-platform/sdk/commit/4f017f20f6682820855bd9ab49193effd5722b32) Thanks [@dqn](https://github.com/dqn)! - Report a connection failure while preparing the login or auth-connection authorization URL as a normal command error, instead of treating it as an SDK crash.
+
+- [#2122](https://github.com/tailor-platform/sdk/pull/2122) [`f5b5b24`](https://github.com/tailor-platform/sdk/commit/f5b5b2409a2e797c667602672d3fab6034145ab9) Thanks [@toiroakr](https://github.com/toiroakr)! - Minify the SDK's build output (function names are preserved for readable stack traces), shrinking the CLI bundle by roughly 40%. Pin the script expression generated for `db.fields.timestamps()`'s built-in `updatedAt` hook so it no longer changes across SDK builds, which previously could surface as a spurious "hooks modified" migration diff for every table using it.
+
+- [#2120](https://github.com/tailor-platform/sdk/pull/2120) [`e4966ec`](https://github.com/tailor-platform/sdk/commit/e4966ec9f7dba0604d3f0b6e7b0cd89a4bbe35ef) Thanks [@toiroakr](https://github.com/toiroakr)! - Fix `tailor deploy` warning `Could not validate OAuth2 client "<name>": unresolved attribute`. The pre-flight check could not evaluate the rule that rejects `requireDpop: true` on a browser client, so it skipped it for every OAuth2 client. The rule now runs: a browser client with `requireDpop: true` fails pre-flight, and other client types no longer produce the warning.
+
+- [#2129](https://github.com/tailor-platform/sdk/pull/2129) [`124db73`](https://github.com/tailor-platform/sdk/commit/124db731293f896889c666b95d0aa63686af9a5b) Thanks [@dqn](https://github.com/dqn)! - Report the real error when the folder lookup in `tailor organization folder delete` fails with something other than "not found" (e.g. network, permission, or authentication errors), instead of always claiming the folder was not found.
+
+- [#2074](https://github.com/tailor-platform/sdk/pull/2074) [`13cd666`](https://github.com/tailor-platform/sdk/commit/13cd6661e45caeaf9c7c1fb7eb487b888209efac) Thanks [@dqn](https://github.com/dqn)! - Prevent TailorDB migration processing from changing object prototypes when snapshots contain special record keys
+
+- [#2006](https://github.com/tailor-platform/sdk/pull/2006) [`1aca9f2`](https://github.com/tailor-platform/sdk/commit/1aca9f283b19f6ca392c8f53d725d7375e580dc4) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update oxc
+
+- [#2030](https://github.com/tailor-platform/sdk/pull/2030) [`943b577`](https://github.com/tailor-platform/sdk/commit/943b577c004b5d08c0753710d447959b29054c80) Thanks [@renovate](https://github.com/apps/renovate)! - chore(deps): update dependency tsx to v4.23.12
+
+- [#2081](https://github.com/tailor-platform/sdk/pull/2081) [`80403ce`](https://github.com/tailor-platform/sdk/commit/80403cee8e8dd1650f5288358845d0dfabfd8b98) Thanks [@renovate](https://github.com/apps/renovate)! - chore(deps): update dependency @electric-sql/pglite to v0.5.5
+
+- [#2083](https://github.com/tailor-platform/sdk/pull/2083) [`fa4fc36`](https://github.com/tailor-platform/sdk/commit/fa4fc36969dddc241c10c332b1091afbfdc6b7d8) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency get-tsconfig to v4.14.2
+
+- [#2084](https://github.com/tailor-platform/sdk/pull/2084) [`bb85f06`](https://github.com/tailor-platform/sdk/commit/bb85f06f9386b6dfcdc1cd46135c8bc2b55f087b) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency kysely to v0.29.5
+
+- [#2085](https://github.com/tailor-platform/sdk/pull/2085) [`98542d3`](https://github.com/tailor-platform/sdk/commit/98542d3aef9e791ca5fa4aaf38e8cbeed7e477f0) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency open to v11.0.1
+
+- [#2108](https://github.com/tailor-platform/sdk/pull/2108) [`c2a1fb5`](https://github.com/tailor-platform/sdk/commit/c2a1fb5fdd0c52a0147f04ee3421bb95ed549943) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency @bufbuild/protobuf to v2.14.0
+
+- [#2109](https://github.com/tailor-platform/sdk/pull/2109) [`b48e4e0`](https://github.com/tailor-platform/sdk/commit/b48e4e0dd9f86ed12f571727dbf96e543ceebb65) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency globals to v17.11.0
+
+- [#2117](https://github.com/tailor-platform/sdk/pull/2117) [`cedf0f6`](https://github.com/tailor-platform/sdk/commit/cedf0f6fb2b6e31afe3f2cf9e8a1134904bc26d7) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency es-toolkit to v1.51.0
+
+- [#2132](https://github.com/tailor-platform/sdk/pull/2132) [`bec3a20`](https://github.com/tailor-platform/sdk/commit/bec3a20445f580a97d4d3e05499d1cbc4d228287) Thanks [@dqn](https://github.com/dqn)! - Skip reloading resolver files when a namespace's resolvers were already loaded but yielded none, avoiding duplicate imports and log output.
+
+- [#2064](https://github.com/tailor-platform/sdk/pull/2064) [`737edfe`](https://github.com/tailor-platform/sdk/commit/737edfe5c17a954430c91e67c89398ab40771450) Thanks [@dqn](https://github.com/dqn)! - Fix `tailor seed apply` timing out with `deadline_exceeded` when seeding 100+ IdP `_User` rows. `_User` rows are now sent in chunks of 25, and when a chunk fails the confirmed created/updated counts are reported so re-running with `--upsert` is an informed choice.
+
+- [#2126](https://github.com/tailor-platform/sdk/pull/2126) [`889bd16`](https://github.com/tailor-platform/sdk/commit/889bd1647895d04934175ca52f15a03302f0e960) Thanks [@dqn](https://github.com/dqn)! - Refactor TailorDB migration snapshot internals into focused modules without changing CLI behavior or persisted formats.
+
+- [#2130](https://github.com/tailor-platform/sdk/pull/2130) [`f67de20`](https://github.com/tailor-platform/sdk/commit/f67de209e49d418372aa8d572d836ef9c927d580) Thanks [@dqn](https://github.com/dqn)! - Output an empty JSON array from `tailor staticwebsite domain list --json` when no custom domains exist, instead of producing no stdout output.
+
+- [#2127](https://github.com/tailor-platform/sdk/pull/2127) [`37e3105`](https://github.com/tailor-platform/sdk/commit/37e310570d4dd1d28327f3330fb1b5cf9115d2b4) Thanks [@dqn](https://github.com/dqn)! - Fix TailorDB hooks and validators sharing one function reference (e.g. `hooks: { create: fn, update: fn }`) being deployed with the argument shape of only the last role, which made the other role read undefined values at runtime.
+
+- [#2073](https://github.com/tailor-platform/sdk/pull/2073) [`f03ea04`](https://github.com/tailor-platform/sdk/commit/f03ea0414ae022e88de5535d2e2ec4c2faf128f0) Thanks [@dqn](https://github.com/dqn)! - Rename the plugin authoring APIs that model TailorDB tables:
+  
+  - `PluginGeneratedType` → `PluginGeneratedTable`
+  - `TailorDBTypeForPlugin` → `TailorDBTableForPlugin`
+  - `TypePluginOutput` → `TablePluginOutput`
+  - `PluginProcessContext` → `PluginTableProcessContext`
+  - `typeConfigRequired` → `tableConfigRequired`
+  - `onTypeLoaded` → `onTableLoaded`
+  - callback context `type` / `typeConfig` → `table` / `tableConfig`
+  - plugin output `types` → `tables`
+  - `TailorDBNamespaceData.types` → `TailorDBNamespaceData.tables`
+  - executor context `sourceType` → `sourceTable`
+  - `getGeneratedType` → `getGeneratedTable`
+  - `PluginGeneratedTypeSource` → `PluginGeneratedTableSource`
+  - `isPluginGeneratedType` → `isPluginGeneratedTable`
+  - source metadata `generatedTypeKind` → `generatedTableKind`
+  
+  Update custom plugins, generated-table lookups, and CLI source metadata consumers to use the new names. The generated `.tailor/<plugin-id>/types` directory and the TailorDB ERD artifact's `generatedTypeKind` field are unchanged.
+
+- [#2070](https://github.com/tailor-platform/sdk/pull/2070) [`fea7726`](https://github.com/tailor-platform/sdk/commit/fea7726df32ec2483f9ddb45565a479aa7e70e37) Thanks [@dqn](https://github.com/dqn)! - The remaining internal comments, JSDoc, and test titles that named a `db.table()` definition a type now say table (table-level hooks, table-attached plugins, table renames, and so on). Behavior is unchanged; a few internal error messages follow the rename, such as `Plugin "..." does not support table-attached processing`. Identifiers and persisted formats are untouched.
+
+- [#2089](https://github.com/tailor-platform/sdk/pull/2089) [`90948e6`](https://github.com/tailor-platform/sdk/commit/90948e6f6e1f3624a9c30595b3ff3a46ffbbced0) Thanks [@toiroakr](https://github.com/toiroakr)! - Add a targeted hint to the `Remote schema drift detected` error when every reported drift is a missing script hash — the pattern left by an environment last deployed with the pre-v2 CLI, which never wrote script hashes. The hint points at `migration sync <N>`, which is already listed as one of the general resolution options. The v2 migration guide (`docs/migration/v2.md`) now also documents that the first `tailor deploy` against such an environment needs a `migration sync` first.
+
+- [#2131](https://github.com/tailor-platform/sdk/pull/2131) [`cb83f59`](https://github.com/tailor-platform/sdk/commit/cb83f59ff2ef0b149f04e0230af4d966bdc029ad) Thanks [@dqn](https://github.com/dqn)! - Cancel the internal upload timeout timer in `tailor staticwebsite deploy` once each upload settles, so finished deploys no longer hold the process open for the remaining timeout when the CLI is used programmatically.
+
+- [#2087](https://github.com/tailor-platform/sdk/pull/2087) [`9e0ad76`](https://github.com/tailor-platform/sdk/commit/9e0ad768968292f2c8481365362518ca716a5c63) Thanks [@toiroakr](https://github.com/toiroakr)! - Fail the build instead of silently dropping a workflow job. A `createWorkflowJob` whose `name`/`body` isn't a static literal (e.g. `body: someWrapper(fn)`), a job's `.start()` call factored into a helper function outside any job body (including a helper defined in another file, even one outside the workflow service's `files` pattern), or a job called by calling `execJobFunction` directly instead of `<job>.start()` (on the ambient `tailor.workflow` global or the `workflow` value imported from `@tailor-platform/sdk/runtime`) — previously passed typecheck/lint/apply but either threw at runtime ("...is rewritten at build time and is unavailable in the bundle") or silently dropped the target job from the bundle the first time it was invoked. All of these now fail the build with the offending job name and file. A workflow file with a syntax error now fails with a clear parse error instead of the same job-detection error. The runtime stub error also names the job so a leftover case is easier to diagnose.
+
+- [#2133](https://github.com/tailor-platform/sdk/pull/2133) [`35b2997`](https://github.com/tailor-platform/sdk/commit/35b2997646d87eec91725ae30cd09b92dd7d05b9) Thanks [@dqn](https://github.com/dqn)! - Report the real error when the workspace lookup in `tailor workspace delete` fails for a reason other than the workspace not existing (e.g. network or authentication errors), instead of always claiming the workspace was not found.
+
+## 2.4.0
+
+### Minor Changes
+
+- [#2054](https://github.com/tailor-platform/sdk/pull/2054) [`6a753cb`](https://github.com/tailor-platform/sdk/commit/6a753cb750df779c91b29b0103bdd24343f18dbb) Thanks [@toiroakr](https://github.com/toiroakr)! - `defineAIGateway()`'s `authNamespace` is now optional, defaulting to the application's own Auth service (local or external) — the common case, since an AI Gateway usually authenticates against its own app's auth. To authenticate against a different application's Auth service, reference it via `auth: { name, external: true }` and let `authNamespace` default to it, the same way a local `defineAuth()` does. Once `tailor.d.ts` is generated, `authNamespace` is type-narrowed to your application's own auth namespace name; register additional names via `declare module "@tailor-platform/sdk" { interface AuthNamespaceNameRegistry { ... } }` only if you need to set `authNamespace` explicitly to a namespace your own `auth` doesn't reference.
+
+- [#2075](https://github.com/tailor-platform/sdk/pull/2075) [`bd0e397`](https://github.com/tailor-platform/sdk/commit/bd0e39720015248e6ebb2c31efca49f9238b7060) Thanks [@dqn](https://github.com/dqn)! - `tailor function test-run` is renamed to `tailor function run`. The old name keeps working as a deprecated alias until v3 and prints a deprecation warning when used; `tailor upgrade` offers the `v3/function-test-run-rename` codemod to rewrite `function test-run` invocations across package.json scripts, shell and Windows scripts, YAML, Markdown, and JavaScript/TypeScript sources.
+
+### Patch Changes
+
+- [#2071](https://github.com/tailor-platform/sdk/pull/2071) [`7ae89fe`](https://github.com/tailor-platform/sdk/commit/7ae89fefb9510b7fea217ccd0d05c79de9fb7d98) Thanks [@dqn](https://github.com/dqn)! - Fix `tailor deploy` never creating TailorDB types that appear in no pending migration diff and define no GraphQL permission — for example baseline tables when a migration history is replayed into a fresh workspace. Such types are now created before any migration script runs.
+
+- [#2050](https://github.com/tailor-platform/sdk/pull/2050) [`a124fed`](https://github.com/tailor-platform/sdk/commit/a124fede0d692c8dc4e60ac7d6da9acee9d02e52) Thanks [@toiroakr](https://github.com/toiroakr)! - Stop dumping the request payload in API error messages. Failed requests (including `tailor query` timeouts) previously printed the full request body, which could expose credentials such as machine user access tokens embedded in query arguments to terminal and CI logs. Error messages now carry only allowlisted identifiers (resource names, namespaces, and ids) so a failing resource can still be identified.
+
+- [#1970](https://github.com/tailor-platform/sdk/pull/1970) [`2b70c30`](https://github.com/tailor-platform/sdk/commit/2b70c30502e84bcf57ab2b237ec9f075cbc9e600) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update rolldown
+
+- [#2036](https://github.com/tailor-platform/sdk/pull/2036) [`d8ec141`](https://github.com/tailor-platform/sdk/commit/d8ec141c16c284a7337f6b7723a686ecb3dcdcf5) Thanks [@renovate](https://github.com/apps/renovate)! - chore(deps): update dependency esbuild@>=0.17.0 <0.28.1 to v0.28.2
+
+- [#2047](https://github.com/tailor-platform/sdk/pull/2047) [`228e394`](https://github.com/tailor-platform/sdk/commit/228e3944237cd6d17022e66792efff3826ee594d) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency @toiroakr/lines-db to v0.12.1
+
+- [#2065](https://github.com/tailor-platform/sdk/pull/2065) [`5a3a0e1`](https://github.com/tailor-platform/sdk/commit/5a3a0e1ce8bfadb769dc4540ef257e944f0c077e) Thanks [@toiroakr](https://github.com/toiroakr)! - Raise the minimum supported Node.js version to 22.18.0 (from 22.15.0).
+  
+  `tailor seed validate` crashed on Node 22.15.0–22.17.x with `Expected a string, an ArrayBuffer, or a TypedArray to be returned for the "source" from the "load" hook but got null`. This is a Node.js bug ([nodejs/node#58607](https://github.com/nodejs/node/issues/58607)): requiring a `node:`-scheme-only builtin (`node:sqlite`, used internally by the seed validator) while both a synchronous `resolve` and `load` hook are registered via `module.registerHooks()` crashes the loader on those versions. The SDK always registers both hooks, so any project on Node 22.15.0–22.17.x hit this. Node fixed it upstream in 22.18.0 ([nodejs/node#58612](https://github.com/nodejs/node/pull/58612)); this release raises `engines.node` to match, since Node 22.15.0–22.17.x never actually supported `tailor seed validate`.
+
+- [#2068](https://github.com/tailor-platform/sdk/pull/2068) [`80260b3`](https://github.com/tailor-platform/sdk/commit/80260b38787da3ed7d7e67ca4ae3116cc8cd07e3) Thanks [@dqn](https://github.com/dqn)! - The remaining CLI output and generated artifacts that named a `db.table()` definition a type now say table.
+  
+  - The deploy plan labels a TailorDB table change `(table)` instead of `(type)`. This also changes the machine-readable `deploy --dry-run --json` output: the `changes[].labels` value `"type"` becomes `"table"`. Update any CI that matches on the old label.
+  - The seed chunker's oversized-record error reads `A single record in table "Order" ...`.
+  - The duplicate plugin-generated table name error reads `Duplicate plugin-generated table name "..."`, and the header of each generated `.tailor/<plugin-id>/types/*.ts` file reads `Auto-generated table by plugin`. Both name the originating table (or `(namespace)`) under a neutral `source:` / `Source:` key.
+  - The seed plugin's generated `_User.schema.ts` comment reads `no TailorDB backing table`. The next `tailor generate` rewrites the file; existing files keep working as-is.
+
+- [#2069](https://github.com/tailor-platform/sdk/pull/2069) [`d07a120`](https://github.com/tailor-platform/sdk/commit/d07a120950c5bac0bd8b5d2e341ad80dd6694448) Thanks [@dqn](https://github.com/dqn)! - The remaining published docs that named a `db.table()` definition a type now say table: the migration guide's rebaseline description, the testing guide's executor trigger description, and the create-sdk `tailordb` template README's feature list (`field-level and table-level` validations).
+
+- [#2062](https://github.com/tailor-platform/sdk/pull/2062) [`153a780`](https://github.com/tailor-platform/sdk/commit/153a78038c65f4376f2f9f75eec8a7a37ea3f6dc) Thanks [@dqn](https://github.com/dqn)! - `tailor seed` now calls a `db.table()` definition a table instead of a type, in its help, progress, and errors — `Seeding 3 tables via Kysely batch insert`. The `fillSeedData` documentation and the `create-sdk` template hint follow.
+  
+  Messages that list the seed targets say entities rather than tables, because `_User` is an IdP entity rather than a TailorDB table and can appear in the same list.
+  
+  The positional is now named `entities`, so `--help` shows `[entities]` instead of `[types]`. Positionals are matched by argv order, so existing invocations are unaffected.
+
+- [#2063](https://github.com/tailor-platform/sdk/pull/2063) [`5d16dc9`](https://github.com/tailor-platform/sdk/commit/5d16dc918f77bd4c76d0d90811207ec15ac30f4e) Thanks [@dqn](https://github.com/dqn)! - The remaining docs and editor tooltips now describe a `db.table()` definition as a table instead of a type. The TailorDB docs say table-level (matching the sentences around them that already say table), the file-upload runtime API documents its `typeName` parameters as table names, and the create-sdk tailordb template's test titles follow suit.
+
+- [#2060](https://github.com/tailor-platform/sdk/pull/2060) [`c880f23`](https://github.com/tailor-platform/sdk/commit/c880f236be87d9cf2bed968fc15d9034e5200793) Thanks [@dqn](https://github.com/dqn)! - `deploy`, schema loading, and the config parser now call a `db.table()` definition a table instead of a type, matching the vocabulary the docs and `db.table()` already use. The deploy plan lists a `TailorDB tables` section and names a deleted table as `TailorDB table "Order"`, a table missing `.permission()` is reported as `TailorDB table "User" has no .permission() configured`, and relation errors read `Field "userID" on table "Employee"`.
+  
+  The built-in plugin descriptions say table for the same reason — `kyselyTypePlugin` now reads "Generates Kysely type definitions for TailorDB tables", keeping "type definitions" for the TypeScript output it writes.
+  
+  Messages about a field's data type, and the TypeScript types generated into `db.ts`, are unchanged.
+
+- [#2055](https://github.com/tailor-platform/sdk/pull/2055) [`303e209`](https://github.com/tailor-platform/sdk/commit/303e2098804c44f63cee2724b917b9158f327802) Thanks [@dqn](https://github.com/dqn)! - TailorDB migration output now calls a `db.table()` definition a table instead of a type, matching the vocabulary the docs already use. Schema drift details read `Table 'User' exists in snapshot but not in remote`, a removal warning reads `Table removed (all records in this table will be deleted during post-migration cleanup)`, and the `--rename` / `--drop` / `--expand-contract` help and errors describe their arguments as `"Table.field"` and `"OldTable:NewTable"`.
+  
+  Only the wording changed: those flags accept exactly the values they did before, and the removal warning recorded in `diff.json` is never read back, so migrations generated earlier keep their wording and stay valid.
+  
+  Messages about a field's data type are unchanged, as is the `DB types:` line naming the generated `db.ts`.
+
+- [#2061](https://github.com/tailor-platform/sdk/pull/2061) [`c2be0d3`](https://github.com/tailor-platform/sdk/commit/c2be0d3fe6422d0161943c858bbc560b234281a8) Thanks [@dqn](https://github.com/dqn)! - The config types now describe a `db.table()` definition as a table instead of a type, so editor tooltips match the vocabulary `db.table()` already uses. Hovering `db.table(...).features({ ... })` documents `gqlOperations` and `publishEvents` in terms of a table, `aggregation` and `bulkUpsert` gain the descriptions they were missing, and an executor's record trigger documents `typeName` as "TailorDB table name to watch for events".
+  
+  `tailordb query` reports an unresolvable name as `Could not find namespace for tables in query: …`.
+  
+  Field-level descriptions still say type where they mean a field's data type, and the key names themselves are unchanged.
+
+- [#2057](https://github.com/tailor-platform/sdk/pull/2057) [`6bee645`](https://github.com/tailor-platform/sdk/commit/6bee645ed513df1e18af4e1178a40b7c55b84166) Thanks [@dqn](https://github.com/dqn)! - `tailor tailordb truncate` now calls a `db.table()` definition a table instead of a type, in its help, prompts, and results. The positional argument is named `tables`, and `TruncateOptions.types` from `@tailor-platform/sdk/cli` is now `TruncateOptions.tables`:
+  
+  ```ts
+  await truncate({ types: ["User"] }); // before
+  await truncate({ tables: ["User"] }); // after
+  ```
+  
+  Passing table names positionally is unchanged, as in `tailor tailordb truncate User Post`. The argument also binds by name, so an invocation spelled `--types User` now has to read `--tables User`.
+
 ## 2.3.0
 
 ### Minor Changes

package/README.md

@@ -96,5 +96,5 @@ See [Create Tailor Platform SDK](https://github.com/tailor-platform/sdk/tree/mai
 
 ## Requirements
 
-- Node.js 22.15.0 or later (or Bun)
+- Node.js 22.18.0 or later (or Bun)
 - A Tailor Platform account ([request access](https://www.tailor.tech/demo))

package/dist/aigateway-DsWDjzk4.mjs

@@ -0,0 +1,2 @@
+const api=()=>globalThis.tailor.aigateway,e={get:(...e)=>api().get(...e)};export{e as t};
+//# sourceMappingURL=aigateway-DsWDjzk4.mjs.map

package/dist/{aigateway-DR4Kwuik.mjs.map → aigateway-DsWDjzk4.mjs.map}

@@ -1 +1 @@
-{"version":3,"file":"aigateway-DR4Kwuik.mjs","names":[],"sources":["../src/runtime/aigateway.ts"],"sourcesContent":["/**\n * AI Gateway utilities.\n *\n * Thin typed wrapper around the platform-provided `tailor.aigateway` runtime API.\n * At runtime this delegates to `globalThis.tailor.aigateway`. Use `mockAigateway`\n * from `@tailor-platform/sdk/vitest` to mock these calls in unit tests.\n *\n * `name` is narrowed to the AI Gateway names defined via `defineAIGateway()`\n * once `tailor.d.ts` has been generated (via `tailor deploy`/`generate`).\n * @example\n * import { aigateway } from \"@tailor-platform/sdk/runtime\";\n *\n * const { url } = await aigateway.get(\"my-aigateway\");\n */\n\n// Import from the public entry (not `#/configure/types/aigateway-name`) so this d.ts\n// references `@tailor-platform/sdk` externally instead of inlining the registry — the\n// same generated `declare module \"@tailor-platform/sdk\"` that narrows\n// `authconnection.getConnectionToken` then also narrows this entry.\nimport type { AIGatewayName } from \"@tailor-platform/sdk\";\n\n/** Result of {@link TailorAigatewayAPI.get}. */\nexport interface GetAIGatewayResult {\n  /** The platform-assigned URL of the AI Gateway. */\n  url: string;\n}\n\n/**\n * Platform API surface for `tailor.aigateway`. Describes the shape the\n * platform runtime injects on `globalThis.tailor.aigateway`.\n */\nexport interface TailorAigatewayAPI {\n  /**\n   * Resolves an AI Gateway defined in the caller's own workspace.\n   * @param name - AI Gateway name, as passed to `defineAIGateway()`\n   * @returns The resolved AI Gateway's platform-assigned URL\n   */\n  get(name: AIGatewayName): Promise<GetAIGatewayResult>;\n}\n\nconst api = (): TailorAigatewayAPI =>\n  (globalThis as unknown as { tailor: { aigateway: TailorAigatewayAPI } }).tailor.aigateway;\n\nconst get: TailorAigatewayAPI[\"get\"] = (...args) => api().get(...args);\n\n/** Runtime wrapper namespace for `tailor.aigateway`. */\nexport const aigateway = { get } as const satisfies TailorAigatewayAPI;\n"],"mappings":";AAwCA,MAAM,YACH,WAAwE,OAAO;AAElF,MAAM,OAAkC,GAAG,SAAS,IAAI,CAAC,CAAC,IAAI,GAAG,IAAI;;AAGrE,MAAa,YAAY,EAAE,IAAI"}
+{"version":3,"file":"aigateway-DsWDjzk4.mjs","names":[],"sources":["../src/runtime/aigateway.ts"],"sourcesContent":["/**\n * AI Gateway utilities.\n *\n * Thin typed wrapper around the platform-provided `tailor.aigateway` runtime API.\n * At runtime this delegates to `globalThis.tailor.aigateway`. Use `mockAigateway`\n * from `@tailor-platform/sdk/vitest` to mock these calls in unit tests.\n *\n * `name` is narrowed to the AI Gateway names defined via `defineAIGateway()`\n * once `tailor.d.ts` has been generated (via `tailor deploy`/`generate`).\n * @example\n * import { aigateway } from \"@tailor-platform/sdk/runtime\";\n *\n * const { url } = await aigateway.get(\"my-aigateway\");\n */\n\n// Import from the public entry (not `#/configure/types/aigateway-name`) so this d.ts\n// references `@tailor-platform/sdk` externally instead of inlining the registry — the\n// same generated `declare module \"@tailor-platform/sdk\"` that narrows\n// `authconnection.getConnectionToken` then also narrows this entry.\nimport type { AIGatewayName } from \"@tailor-platform/sdk\";\n\n/** Result of {@link TailorAigatewayAPI.get}. */\nexport interface GetAIGatewayResult {\n  /** The platform-assigned URL of the AI Gateway. */\n  url: string;\n}\n\n/**\n * Platform API surface for `tailor.aigateway`. Describes the shape the\n * platform runtime injects on `globalThis.tailor.aigateway`.\n */\nexport interface TailorAigatewayAPI {\n  /**\n   * Resolves an AI Gateway defined in the caller's own workspace.\n   * @param name - AI Gateway name, as passed to `defineAIGateway()`\n   * @returns The resolved AI Gateway's platform-assigned URL\n   */\n  get(name: AIGatewayName): Promise<GetAIGatewayResult>;\n}\n\nconst api = (): TailorAigatewayAPI =>\n  (globalThis as unknown as { tailor: { aigateway: TailorAigatewayAPI } }).tailor.aigateway;\n\nconst get: TailorAigatewayAPI[\"get\"] = (...args) => api().get(...args);\n\n/** Runtime wrapper namespace for `tailor.aigateway`. */\nexport const aigateway = { get } as const satisfies TailorAigatewayAPI;\n"],"mappings":"AAwCA,MAAM,QACH,WAAwE,OAAO,UAKrE,EAAY,CAAE,KAHa,GAAG,IAAS,IAAI,CAAC,CAAC,IAAI,GAAG,CAAI,CAGtC"}

package/dist/application-DFOUovmN.mjs

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