@tailor-platform/sdk 2.27.0 → 2.28.0

package/CHANGELOG.md

@@ -1,5 +1,53 @@
 # @tailor-platform/sdk
 
+## 2.28.0
+
+### Minor Changes
+
+- [#2589](https://github.com/tailor-platform/sdk/pull/2589) [`4bf9fd5`](https://github.com/tailor-platform/sdk/commit/4bf9fd5cae3b240f39647002adfdb55b93afb15b) Thanks [@dqn](https://github.com/dqn)! - Default to JSON output when an AI coding agent such as Claude Code, Codex, Cursor, or Gemini CLI runs `tailor`, so the agent reads parseable output even without the bundled agent skill, and start `--help` with guidance for the agent. Pass `--json=false` or set `TAILOR_JSON_OUTPUT=false` to keep table output under an agent, or set `POLITTY_NO_AGENT=1` to turn agent detection off. CLI plugins keep their current output.
+
+- [#2595](https://github.com/tailor-platform/sdk/pull/2595) [`928a0cf`](https://github.com/tailor-platform/sdk/commit/928a0cf2d12deeb680f1319ae5cfc90d3c52873d) Thanks [@toiroakr](https://github.com/toiroakr)! - Add `tailor data clone` to copy the data of an application from one workspace to another, and `tailor data operation get` to check on a started clone or wait for it with `--wait`. It copies the TailorDB namespaces registered in the application's subgraph; `--copy-files` and `--copy-idp-users` also copy TailorDB file content and IdP users. `--name` defaults to the application name in the config file. `data clone` waits for the clone to finish; pass `--no-wait` to start it and exit.
+
+- [#2595](https://github.com/tailor-platform/sdk/pull/2595) [`a99be0b`](https://github.com/tailor-platform/sdk/commit/a99be0b905bf95a5057e52e19d146b53a78475cc) Thanks [@toiroakr](https://github.com/toiroakr)! - Add `--clone-timeout` to `tailor tailordb migration test` to set how long `--data clone` waits for the data clone to finish, for example `30s` or `10m`. The default is now 30 minutes, up from 5, and the option is rejected with `--data seed`. If your CI job time limit is shorter than 30 minutes, pass a shorter `--clone-timeout` so the command can time out and delete its temporary workspace before the job is stopped.
+
+- [#2595](https://github.com/tailor-platform/sdk/pull/2595) [`a99be0b`](https://github.com/tailor-platform/sdk/commit/a99be0b905bf95a5057e52e19d146b53a78475cc) Thanks [@toiroakr](https://github.com/toiroakr)! - Add `--keep-ttl` to `tailor tailordb migration test` to record an expiry, for example `24h` or `7d`, on the temporary workspace that `--keep` retains, so `tailor workspace prune --expired` can delete it later. It requires `--keep`.
+
+- [#2586](https://github.com/tailor-platform/sdk/pull/2586) [`65b793b`](https://github.com/tailor-platform/sdk/commit/65b793b86896b939946851a49cbf65f6465fbee7) Thanks [@dqn](https://github.com/dqn)! - Keep scenario and per-environment seed data side by side as datasets: directories under `<distPath>/data/` holding JSONL rows for some of the tables. `tailor seed apply`, `validate`, and `fill` take `--dataset <name>` (repeatable) to use datasets on top of the base seed data, and `tailor seed dump --dataset <name>` writes into one. `--all-datasets` selects every dataset directory in name order for `apply`, `validate`, and `fill`, including gitignored local datasets and directories added later; it cannot be combined with `--dataset`, and fails if no dataset directories exist. `apply --truncate --all-datasets` keeps the existing truncate scope and confirmation. `validate` checks foreign keys across the base data and the selected datasets and reports an id defined in more than one of them at its own file and line; `apply` rejects such an id before it changes anything. `--no-base` applies or validates the selected datasets alone, so a dump written with `--dataset` restores on its own. Name the combinations you use in the new `datasets` option of `seedPlugin` (for example `datasets: { preview: ["cogs", "shipments"] }`) to select them with one `--dataset`. Projects without datasets work as before, except that `tailor seed apply` now reads all seed rows before truncating or seeding anything, so a malformed file stops the run with the workspace untouched. Naming a dataset directory, or a file in one, as the path of `tailor seed validate` or `fill` points you at `--dataset`.
+
+- [#2600](https://github.com/tailor-platform/sdk/pull/2600) [`ea634ba`](https://github.com/tailor-platform/sdk/commit/ea634ba08df767730a1e8f415c87e60dfc4c0300) Thanks [@ikawaha](https://github.com/ikawaha)! - Add the `gapless` option to `.serial()` (preview), which numbers records without gaps: a number is used only by a create that commits.
+
+- [#2583](https://github.com/tailor-platform/sdk/pull/2583) [`23b3b36`](https://github.com/tailor-platform/sdk/commit/23b3b363cc09bbf6c48e7d84d8b32068898062dd) Thanks [@dqn](https://github.com/dqn)! - Add `maintenanceMode` to `defineConfig()` to choose whether `tailor deploy` restricts the TailorDB namespaces it migrates while pending migrations run. `"migration"` restricts them (no generated GraphQL create, update, delete, or bulk upsert, and no record events) until the migrations complete, as every deploy did before; `"deploy"` keeps them restricted until the deploy has also applied resolvers, executors, and workflows, so executors from the previous deploy do not receive events from the migrated tables while the deploy replaces them; `false` does not restrict them.
+  
+  Tables that a deploy left restricted after its migrations completed, for example because the deploy was interrupted, no longer make the next deploy stop with remote schema drift; that deploy releases them when it applies its TailorDB changes.
+  
+  Restoring table settings after a failed migration no longer fails for a table whose checkpoint sets `publishEvents: false` while an executor in the same deploy subscribes to it, which left that table restricted.
+
+- [#2577](https://github.com/tailor-platform/sdk/pull/2577) [`eab2d88`](https://github.com/tailor-platform/sdk/commit/eab2d8867b4e74c79a31a7f47eaeb958c6381370) Thanks [@dqn](https://github.com/dqn)! - Show how long `tailor deploy` keeps tables in maintenance mode while it applies TailorDB migrations. Deploy now tells waiting for a migration job to start apart from the script running: it reports when the script starts running, how long it waited and ran, and a summary of the whole maintenance window by phase. `tailor deploy --json` returns the same breakdown under `tailordbMaintenance`. Each migration job now logs `[tailor-sdk] migration script started` before the script runs.
+
+- [#2579](https://github.com/tailor-platform/sdk/pull/2579) [`a139e89`](https://github.com/tailor-platform/sdk/commit/a139e899b087858677aa9e4cc03bf54e49dba95b) Thanks [@dqn](https://github.com/dqn)! - Add `tailor user update --default-organization-id <id> [--default-folder-id <id>]` to store where `tailor workspace create`, workspace creation during `deploy`, and the programmatic `createWorkspace()` put new workspaces when neither organization nor folder is given. The defaults are kept per user and platform, and any explicit organization or folder, including through `TAILOR_PLATFORM_ORGANIZATION_ID` / `TAILOR_PLATFORM_FOLDER_ID` for CLI commands, replaces both. `deploy --create-workspace` also uses the resolved default location when checking whether an existing workspace matches. `workspace create`, `deploy --create-workspace`, and the programmatic `createWorkspace()` now reject a folder ID without an organization ID with a clear error instead of failing with an internal error.
+  
+  `workspace create` and `deploy` now use organization and folder IDs from `--env-file`, even when no user defaults are stored. Previously these values were ignored; a folder-only env file now fails unless an organization is also given. Command-line options take precedence, and empty env-file values are treated as not given.
+
+### Patch Changes
+
+- [#2609](https://github.com/tailor-platform/sdk/pull/2609) [`1c36c61`](https://github.com/tailor-platform/sdk/commit/1c36c618e9c4ad2ee4373a5962c8ea278e9aac07) Thanks [@toiroakr](https://github.com/toiroakr)! - `tailor deploy` now warns when an IdP `permission` rule allows every authenticated user (a condition on `_loggedIn`, such as `[{ user: "_loggedIn" }, "=", true]`, as its only condition). Such a rule lets any signed-in user run that operation against any IdP user, for example reading and changing login information such as email addresses or sending password reset emails to anyone. The deploy still succeeds; restrict the rule to an administrator role unless every user who can sign in is trusted.
+
+- [#2588](https://github.com/tailor-platform/sdk/pull/2588) [`3de270f`](https://github.com/tailor-platform/sdk/commit/3de270f6bb1d75b74ed4d277593f0e70ecc2b59b) Thanks [@dqn](https://github.com/dqn)! - Update `@politty/zod` to 0.4.3. A positional argument is no longer accepted under its own name as an option, so pass the value positionally: `tailor profile create dev`, not `tailor profile create --name dev`. Most commands report such an option as unknown; a few, such as `tailor completion` and `npm create @tailor-platform/sdk`, only warn and ignore it. `tailor secret vault create --name`, `tailor secret vault delete --name`, and `tailor tailordb truncate --tables`, which the documentation and earlier release notes use, still accept both forms. Mixing the two forms, as in `tailor tailordb truncate --tables User Order`, is rejected; repeat the option for each table, as in `--tables User --tables Order`.
+
+- [#2578](https://github.com/tailor-platform/sdk/pull/2578) [`b57a21f`](https://github.com/tailor-platform/sdk/commit/b57a21f9b6e16d6e3a87e19f7504429a41988a9c) Thanks [@dqn](https://github.com/dqn)! - Keep settings that a newer SDK version wrote to the CLI config file (`~/.config/tailor-platform/config.yaml`) when this version rewrites the file, for example after logging in or refreshing a token, instead of silently dropping them.
+
+- [#2580](https://github.com/tailor-platform/sdk/pull/2580) [`9c54e51`](https://github.com/tailor-platform/sdk/commit/9c54e516264276dd453d6ad3b546452c830b4006) Thanks [@dqn](https://github.com/dqn)! - Clarify in `tailor workspace prune --help` and error suggestions that location options must be given on the command line and that the defaults from `tailor user update` are not used. Warn before an unscoped sweep that every visible workspace is a candidate for the name and age filters, including with `--yes` or `--dry-run`.
+
+- [#2612](https://github.com/tailor-platform/sdk/pull/2612) [`34a67e3`](https://github.com/tailor-platform/sdk/commit/34a67e33a34533bd62f34b7e5bc358c2448eb038) Thanks [@toiroakr](https://github.com/toiroakr)! - Reject `.serial()` on fields inside `db.object()`. TailorDB cannot number a serial field nested in an object, so a create that omitted the value failed with an internal error. It is now a type error, and a build that still defines one fails; remove `.serial()` from the nested field (or move the field out of the object) to upgrade.
+
+- [#2556](https://github.com/tailor-platform/sdk/pull/2556) [`56abcc9`](https://github.com/tailor-platform/sdk/commit/56abcc9a063ca90c4561d908c1975296227a3480) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update @​inquirer
+
+- [#2604](https://github.com/tailor-platform/sdk/pull/2604) [`4dde6ea`](https://github.com/tailor-platform/sdk/commit/4dde6ea565c97b1bfbdc8606bd0c565d25af6623) Thanks [@renovate](https://github.com/apps/renovate)! - chore(deps): update dependency @​types/node to v24.19.2
+
+- [#2607](https://github.com/tailor-platform/sdk/pull/2607) [`b517e0a`](https://github.com/tailor-platform/sdk/commit/b517e0aeede87d34eb518b79c5cfdd8378eb0e50) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency @​napi-rs/keyring to v2.1.1
+
+- [#2611](https://github.com/tailor-platform/sdk/pull/2611) [`938f418`](https://github.com/tailor-platform/sdk/commit/938f418c4d847402e579f458f1e3ef3941906288) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update rolldown
+
 ## 2.27.0
 
 ### Minor Changes

package/agent-skills/tailor/SKILL.md

@@ -26,8 +26,10 @@ Use these files as the single source of truth:
 1. Prefer SDK docs above assumptions. If behavior is unclear, cite the exact doc path used.
 2. Keep examples compatible with Node.js 22+.
 3. For CLI questions, verify command and option names from `docs/cli-reference.md` and `docs/cli/*.md`.
-4. When running CLI commands, set `TAILOR_JSON_OUTPUT=true` (or pass `--json`) and parse the JSON
-   instead of the table output, which is formatted for humans and may change.
+4. When running CLI commands, parse the JSON instead of the table output, which is formatted for
+   humans and may change. The CLI defaults to JSON when it detects an AI coding agent; if a command
+   still prints a table (an undetected agent, or a CLI plugin command), set `TAILOR_JSON_OUTPUT=true`
+   or pass `--json`. Use `--help-json` for machine-readable help.
 5. For configuration questions, validate examples against `docs/configuration.md` and related service docs.
 
 ## Quick Navigation