@tailor-platform/sdk 2.32.0 → 2.34.0

package/CHANGELOG.md

@@ -1,5 +1,107 @@
 # @tailor-platform/sdk
 
+## 2.34.0
+
+### Minor Changes
+
+- [#2669](https://github.com/tailor-platform/sdk/pull/2669) [`f59f06e`](https://github.com/tailor-platform/sdk/commit/f59f06e14ecc3c22553d5da7b13b87dd7376c059) Thanks [@dqn](https://github.com/dqn)! - The `tailor` CLI and its command groups, such as `tailor tailordb` and `tailor workspace`, and the setup, seed, and TailorDB ERD plugins now exit with code 2 when run without a subcommand and given an unknown option or an invalid option value, including one set through its environment variable. They previously printed their help or a warning, or ran their default subcommand, and exited with 0. A script or CI job that passes a mistyped option after a group name, such as `tailor workspace --bogus`, now fails with 2 instead of printing a warning and exiting with 0. `--no-json` and `--no-verbose` now turn JSON output and verbose logging off, where they were previously ignored with a warning, so `--no-json` also turns off the JSON output an AI coding agent gets by default. `--no-verbose` and `--verbose=false` also override `DEBUG=true` and `RUNNER_DEBUG=1`, which previously kept verbose logging on. Likewise, setting `logger.verbose` from `@tailor-platform/sdk/cli` overrides them, and setting it to `undefined` defers to them.
+
+- [#2708](https://github.com/tailor-platform/sdk/pull/2708) [`bc16821`](https://github.com/tailor-platform/sdk/commit/bc168219a64972f0830cff380942b3cc4d4e0060) Thanks [@toiroakr](https://github.com/toiroakr)! - A relation set on a field inside `db.object()` now becomes a foreign key on that inner field, in the deployed schema and in the PGlite schema `kyselyTypePlugin` generates. Before, the relation was accepted but had no effect, so a row pointing at a missing parent was stored. For a project that already has such a relation, the next `tailor deploy` stops with a schema check error until you run `tailor tailordb migration generate`, which records one non-breaking `field_modified` change. Values already stored are not checked when the foreign key is added; after that deploy, the platform rejects a nested value that points at a missing parent.
+
+- [#2755](https://github.com/tailor-platform/sdk/pull/2755) [`9ddec31`](https://github.com/tailor-platform/sdk/commit/9ddec318f1a9f01f1773042df485ecee48cf71e2) Thanks [@toiroakr](https://github.com/toiroakr)! - Added `buildOptions.inlineSourcemapProjectSources` to choose which of your own source files embed their text in the inline sourcemap. `exclude: ["src/generated/**"]` leaves out the text of generated files, and `include` keeps only the matching files. The globs are relative to the directory containing your config file. Files under `node_modules` stay controlled by `inlineSourcemapDependencySources`.
+
+### Patch Changes
+
+- [#2769](https://github.com/tailor-platform/sdk/pull/2769) [`c9bc40b`](https://github.com/tailor-platform/sdk/commit/c9bc40b22d710ae03070c13112559d0db5d260b3) Thanks [@dqn](https://github.com/dqn)! - Internal: the build-only result of `deploy`, used by the SDK's own tests, now also includes HTTP adapter bundles grouped by application name. A build-only deploy now rejects two configs that share an application name and both define HTTP adapters, which a regular deploy already rejects.
+
+- [#2767](https://github.com/tailor-platform/sdk/pull/2767) [`4c42666`](https://github.com/tailor-platform/sdk/commit/4c4266603730b39a21b92f698105f1d720c8892f) Thanks [@dqn](https://github.com/dqn)! - `tailor deploy --dry-run` no longer asks to confirm resource deletions, owner conflicts, unmanaged resources, or missing dependent applications, so it reaches the plan without `--yes`, including under `--json` or without a terminal. The warnings that list those resources are still shown, and the warning that lists the TailorDB migration checkpoints the deploy would reset is now shown too.
+  
+  With `--dry-run --json`, `warnings` now also has a `type: "missingDependentApp"` entry for each resource whose recorded dependent application is missing from the deploy. Before, this was only printed to stderr.
+
+- [#2749](https://github.com/tailor-platform/sdk/pull/2749) [`468bd4b`](https://github.com/tailor-platform/sdk/commit/468bd4b1f5d87ce11c3eda99c16752910e8df333) Thanks [@dqn](https://github.com/dqn)! - Internal refactor of the ownership checks `tailor deploy` and `tailor remove` run on existing resources. No observable behavior change.
+
+- [#2752](https://github.com/tailor-platform/sdk/pull/2752) [`b09d3c9`](https://github.com/tailor-platform/sdk/commit/b09d3c9b21e68d290b19bc8bf3672726cb5baf48) Thanks [@dqn](https://github.com/dqn)! - Internal refactoring: `tailor tailordb migration generate` now handles field, table, and nested member renames and drops with one shared implementation. Prompts, error messages and codes, and JSON output are unchanged.
+
+- [#2787](https://github.com/tailor-platform/sdk/pull/2787) [`039f6f5`](https://github.com/tailor-platform/sdk/commit/039f6f51422b865c3cd041394aaeea9b49a0360b) Thanks [@dqn](https://github.com/dqn)! - `tailor tailordb migration generate` and `tailor tailordb migration script` open the file they scaffold in `EDITOR` or `VISUAL` only when they run in an interactive terminal outside CI. Run from a script, a CI step, or an agent shell with human output, they used to start the editor and wait for it with no terminal attached, so the command hung. An editor that opens its own window, such as `code --wait`, also no longer opens when the command's input or output is piped.
+
+- [#2780](https://github.com/tailor-platform/sdk/pull/2780) [`8000beb`](https://github.com/tailor-platform/sdk/commit/8000beb99b6fe5f3602467c79b69668c46392545) Thanks [@dqn](https://github.com/dqn)! - `tailor deploy` and every `tailor tailordb migration` subcommand except `script` now reject a migration directory that has `migrate.ts` or other generated files but no `diff.json`. Previously, such a leftover in the latest migration number let the next `migration generate` reuse that number and deploy run the stale script. They also reject a `diff.json` in `0000/`, which was previously ignored. `tailor tailordb migration status` now reports invalid migration files as an error for that namespace.
+
+- [#2792](https://github.com/tailor-platform/sdk/pull/2792) [`66c8c85`](https://github.com/tailor-platform/sdk/commit/66c8c8580ea7a11b54fe61b13416bcb492a11dc2) Thanks [@dqn](https://github.com/dqn)! - `tailor tailordb migration resolve` now refuses to run when the in-progress migration is not the one right after the checkpoint. Previously, `--rollback` moved the checkpoint forward in that state, and `--complete` moved it past migrations whose `migrate.ts` never ran.
+
+- [#2750](https://github.com/tailor-platform/sdk/pull/2750) [`0628ad3`](https://github.com/tailor-platform/sdk/commit/0628ad30fa1ad21010f4f16d59ab2af9d66eb79e) Thanks [@dqn](https://github.com/dqn)! - Build resolver, executor, workflow job, and auth hook bundles through one shared step. Bundled output is unchanged.
+
+- [#2748](https://github.com/tailor-platform/sdk/pull/2748) [`35ce933`](https://github.com/tailor-platform/sdk/commit/35ce9330b64ebea35469797c592cb0a368bf0d4c) Thanks [@dqn](https://github.com/dqn)! - Internal refactoring: remove unused internal helpers from the plugin manager, the TailorDB migration modules, and the SDK's own test setup. No user-facing behavior change.
+
+- [#2786](https://github.com/tailor-platform/sdk/pull/2786) [`deeb82f`](https://github.com/tailor-platform/sdk/commit/deeb82ff6a2fc4418f761a34cfdec01f9a26def2) Thanks [@dqn](https://github.com/dqn)! - Long-running `tailor` commands, such as a deploy waiting on a migration job, `tailor workflow start --wait`, or `tailor function logs --follow`, no longer fail with `[unauthenticated] ... invalid token` when the access token expires partway through. They renew the token when it is about to expire, and retry a request once with a new token if the Platform rejects the one it sent. A client from `initOperatorClient` in `@tailor-platform/sdk/cli`, created with a token from `loadAccessToken`, does the same and may refresh and save the stored login while it runs. Commands that use `TAILOR_PLATFORM_TOKEN` or a machine-user login are still limited to the token's lifetime. The notice that a newer config version is available now appears once per command instead of on every read of the config.
+
+- [#2762](https://github.com/tailor-platform/sdk/pull/2762) [`30b9fa8`](https://github.com/tailor-platform/sdk/commit/30b9fa87c8897937a13ec16747047c5679223fe7) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update oxc
+
+- [#2765](https://github.com/tailor-platform/sdk/pull/2765) [`eb01ec6`](https://github.com/tailor-platform/sdk/commit/eb01ec6b2286e71c04a1b009f859846f91c603d0) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency @​politty/zod to v0.6.0
+
+- [#2797](https://github.com/tailor-platform/sdk/pull/2797) [`f202845`](https://github.com/tailor-platform/sdk/commit/f2028455919ca87dc77c0b0deb5dd84d4a1335c9) Thanks [@renovate](https://github.com/apps/renovate)! - chore(deps): lock file maintenance
+
+- [#2804](https://github.com/tailor-platform/sdk/pull/2804) [`8c20b0b`](https://github.com/tailor-platform/sdk/commit/8c20b0b09824c0cb01ad49375d7e712e9afdbd53) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency amaro to v1.2.2
+
+- [#2805](https://github.com/tailor-platform/sdk/pull/2805) [`c0641d2`](https://github.com/tailor-platform/sdk/commit/c0641d2c315cacb34f83b9b39244a4404a19830b) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency rolldown to v1.2.15
+
+- [#2709](https://github.com/tailor-platform/sdk/pull/2709) [`6eb202f`](https://github.com/tailor-platform/sdk/commit/6eb202feaee7b80524111599f3e47d4a22faf462) Thanks [@toiroakr](https://github.com/toiroakr)! - `tailor deploy` now fails when a vault declared in `defineSecretManager()` has the same name as the vault the SDK creates for one of the application's IdP clients (`idp-<namespace>-<client>`), because the two would share one vault and the built-in IdP configuration in Auth could read a secret that was overwritten by the declared value. If the application already manages a vault with that name, renaming it and removing the declaration both delete the old vault and its secrets on the next deploy, including the secret of an IdP client that already exists, and the error says so.
+
+- [#2788](https://github.com/tailor-platform/sdk/pull/2788) [`eabbd2e`](https://github.com/tailor-platform/sdk/commit/eabbd2e6f36e6743118c150c6fa4e893334adb0f) Thanks [@toiroakr](https://github.com/toiroakr)! - `tailor deploy` now warns when a vault declared in `defineSecretManager()` has a name that starts with `tailor--` (two hyphens, so that names such as `tailor-reports` stay free). The prefix is reserved in advance for the platform and has no use today. The warning does not stop the deploy, and these names will be rejected in v3.
+
+- [#2782](https://github.com/tailor-platform/sdk/pull/2782) [`b09cb46`](https://github.com/tailor-platform/sdk/commit/b09cb4687d255d6373e88d2dcd278f97540322b1) Thanks [@dqn](https://github.com/dqn)! - Fix `tailor` commands that run at the same time breaking each other's login. When several commands found the stored token expired, each refreshed it, and all but one failed with `AUTH_TOKEN_REFRESH_FAILED`; sometimes the stored refresh token was left unusable, and every later command failed until you ran `tailor login` again. Commands now refresh one at a time and use the token another command already stored. `tailor logout` also waits for a refresh in progress, so the refresh no longer restores the user it removed.
+  
+  The CLI now refreshes a token that expires within five minutes, so a command no longer starts with a token that is about to expire. Until the current token expires, the CLI keeps using it if that early refresh fails or another command is already refreshing. `loadAccessToken` from `@tailor-platform/sdk/cli` follows the same rules. The config file is now replaced in one step, so a command reading it while another writes it no longer fails to parse it.
+
+- [#2576](https://github.com/tailor-platform/sdk/pull/2576) [`07611f5`](https://github.com/tailor-platform/sdk/commit/07611f5a28210bcb50b2234b34fee6faaaa1d304) Thanks [@toiroakr](https://github.com/toiroakr)! - `tailor setup ci preview` takes `--require <ready|label>` instead of `--require-preview-label`. By default every pull request now gets a preview, draft pull requests included, which the generated workflow used to skip. `--require ready` skips draft pull requests and also triggers on `ready_for_review`, so a draft that is marked ready for review gets its preview right away instead of waiting for the next push. `--require label` deploys only pull requests labeled `tailor:preview`, as `--require-preview-label` did, and now also for a labeled draft. The requirement is recorded in `.github/tailor.lock` as `require`, so `tailor setup update` regenerates the same workflow.
+  
+  `--require-preview-label` is removed: use `--require label`. `setup` remains a beta command, so this ships as an immediate change rather than going through a deprecation cycle. A preview target recorded before this change is read by `tailor setup update` as `--require ready`, or as `--require label` if it required the label: the first keeps skipping drafts and gains the `ready_for_review` trigger, and the second now also deploys a labeled draft. To deploy drafts as well, run `tailor setup ci preview` again without `--require`.
+
+- [#2779](https://github.com/tailor-platform/sdk/pull/2779) [`5461ed7`](https://github.com/tailor-platform/sdk/commit/5461ed7e2d96e0559360910afa735de3e4e0736c) Thanks [@dqn](https://github.com/dqn)! - Fix inline sourcemaps embedding the source text of files under `node_modules` that belong to no package, such as a generated client in `node_modules/.prisma`, when `buildOptions.inlineSourcemapDependencySources` is `false` or a package list. Such files are now embedded only when the option is `true`, and `tailor function run` and `tailor function logs` read their code snippets from your local files.
+
+## 2.33.0
+
+### Minor Changes
+
+- [#2742](https://github.com/tailor-platform/sdk/pull/2742) [`4f3f30c`](https://github.com/tailor-platform/sdk/commit/4f3f30c4b7a305d654a1b8ad9cb709f7effe75ec) Thanks [@mocchira](https://github.com/mocchira)! - `customDomains` entries can now name a destination, moving a domain to another static website — in the same workspace or a different one — without downtime, a new certificate, or a DNS change:
+  
+  ```typescript
+  defineStaticWebSite("my-website", {
+    customDomains: [{ domain: "app.example.com", transferTo: { workspaceId: "..." } }],
+  });
+  ```
+  
+  Deploying opens the offer; the receiving side accepts it by listing the domain normally and deploying. `tailor deploy` reports an open offer and says when the domain has moved and the entry can be deleted.
+  
+  While an offer is open, `tailor deploy` and `tailor remove` refuse to remove the domain or the static website holding it, at plan time and before anything is applied. A plan also fails, rather than quietly doing nothing, when an entry names a domain the site does not hold and no transfer from this workspace accounts for it, or when the domain is still being removed.
+  
+  `tailor deploy` also now takes ownership of a custom domain that already exists but carries no SDK labels, instead of trying to add it again — the recovery path when a previous deploy lost the response, or when the domain was added through the API or console.
+
+- [#2591](https://github.com/tailor-platform/sdk/pull/2591) [`59fcb9a`](https://github.com/tailor-platform/sdk/commit/59fcb9a356455494bdbc0068d59ae4daa4de1582) Thanks [@toiroakr](https://github.com/toiroakr)! - Let a TailorDB migration script that exports `steps` roll back instead of staying in progress when a step fails. Export `onFailure = "rollback"` next to `steps` and `tailor deploy` restores the pre-migration schema, clears the in-progress record, and takes the tables out of maintenance mode. The deploy then fails with the step's error under the code `MIGRATION_ROLLED_BACK`, and the next deploy runs every step again from the beginning. Nothing is rolled back while the run may still be executing, or when the in-progress record cannot be cleared. If some tables cannot be rolled back, the deploy warns which tables need manual repair. Without `onFailure`, or with `"resume"`, a failed run stays in progress as before
+
+- [#2700](https://github.com/tailor-platform/sdk/pull/2700) [`6eb2033`](https://github.com/tailor-platform/sdk/commit/6eb203365aa0aedf6619b63f192aac948e2e0876) Thanks [@toiroakr](https://github.com/toiroakr)! - The `db.pglite.ts` that `tailor tailordb migration generate` writes now enforces relations: a row pointing at a parent that does not exist is rejected, as on the platform. Migration tests that stage a row whose parent is missing must create the parent first or stage the row with `prepareFixtures`. A relation the pre-migration schema cannot satisfy is left unenforced: one whose pending type change leaves the field a different type from its target, or one the migration retargets.
+  
+  `prepareFixtures` from `@tailor-platform/sdk/vitest` writes a test's starting records with relations unchecked, so a migration test can stage rows that predate a relation, and checks them again before the script runs. The migration PGlite test scaffold uses it.
+
+### Patch Changes
+
+- [#2741](https://github.com/tailor-platform/sdk/pull/2741) [`6f6ca9f`](https://github.com/tailor-platform/sdk/commit/6f6ca9fb72255f4124c04933af012ef6d7170380) Thanks [@mocchira](https://github.com/mocchira)! - `tailor staticwebsite domain list` and `domain get` now report a domain being removed as `removing` instead of `unknown`, and `tailor api` can inspect and call the custom domain transfer endpoints (`RequestCustomDomainTransfer`, `CancelCustomDomainTransfer`, `AcceptCustomDomainTransfer`, `GetCustomDomainTransfer`, `ListCustomDomainTransfers`).
+
+- [#2736](https://github.com/tailor-platform/sdk/pull/2736) [`8595d14`](https://github.com/tailor-platform/sdk/commit/8595d14c76d8ce364448f321ad430c01582d910f) Thanks [@toiroakr](https://github.com/toiroakr)! - `tailor login` now shows an HTML page in the browser after authentication instead of raw JSON, telling you to close the tab and return to the terminal. The page follows the system light/dark theme. A failed login shows the reason in the page as well, and `tailor authconnection authorize` shows the same pages on success and failure.
+
+- [#2740](https://github.com/tailor-platform/sdk/pull/2740) [`ef844ff`](https://github.com/tailor-platform/sdk/commit/ef844ffc39a84a39e02818eec9f6a08188ce2ccb) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency @​napi-rs/keyring to v2.1.2
+
+- [#2760](https://github.com/tailor-platform/sdk/pull/2760) [`a7d1cb8`](https://github.com/tailor-platform/sdk/commit/a7d1cb8ce6dbc324f57ff2704f5ffe92af5bf963) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update @​inquirer
+
+- [#2766](https://github.com/tailor-platform/sdk/pull/2766) [`15b6f4a`](https://github.com/tailor-platform/sdk/commit/15b6f4a7a9b6c0c2dd6514c6a5a7ca73a4870000) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency pkg-types to v2.4.0
+
+- [#2718](https://github.com/tailor-platform/sdk/pull/2718) [`8927563`](https://github.com/tailor-platform/sdk/commit/89275638f7732fd69015e4b70ad8101b55b22649) Thanks [@toiroakr](https://github.com/toiroakr)! - The `tailor query` REPL now highlights SQL block comments (`/* ... */`) and GraphQL block strings (`"""..."""`) that span multiple lines, and also colours SQL `--` comments and trailing GraphQL `#` comments.
+
+- [#2731](https://github.com/tailor-platform/sdk/pull/2731) [`bbfb9b1`](https://github.com/tailor-platform/sdk/commit/bbfb9b1e9918cb59fdbc6865c6eb81bc3136aecd) Thanks [@dqn](https://github.com/dqn)! - Fix plugin-generated resolvers being silently ignored. Resolver output from table and namespace hooks is now loaded, bundled, and deployed to the resolver namespace with the same name as the hook's TailorDB namespace. The two are separate namespaces that only share the name; the resolver namespace is created automatically when it is not configured, and its settings apply when it is. Resolvers that your existing plugins already return are deployed on the next `deploy`; without `defaultPermission` on their resolver namespace, anonymous callers can reach them.
+
+- [#2747](https://github.com/tailor-platform/sdk/pull/2747) [`d52ec40`](https://github.com/tailor-platform/sdk/commit/d52ec402c9cc295eb94e69ee45b6f87e888badfa) Thanks [@dqn](https://github.com/dqn)! - Internal refactoring: remove the unused asynchronous variants of the SDK's internal TypeScript loader hooks. Loading `.ts` config and resource files is unchanged.
+
+- [#2744](https://github.com/tailor-platform/sdk/pull/2744) [`559d442`](https://github.com/tailor-platform/sdk/commit/559d442b7ab19d900ccfd5b84694b88490ae62e2) Thanks [@dqn](https://github.com/dqn)! - Reject duplicate generated enum constant names instead of silently overwriting definitions. Duplicates with identical values, which previously generated successfully, now fail too. Rename conflicting tables or fields to give their enum constants unique names.
+
 ## 2.32.0
 
 ### Minor Changes

package/dist/ai/index.d.mts

@@ -1,4 +1,3 @@
-//#region src/ai/index.d.ts
 /**
  * Client for semantic decisions through Tailor AI Gateway.
  *
@@ -108,5 +107,4 @@ export interface SystemOneClient {
  * @param options - AI Gateway connection options
  * @returns A semantic decision client
  */
-export declare function createSystemOne(options: CreateSystemOneOptions): SystemOneClient;
-//#endregion
+export declare function createSystemOne(options: CreateSystemOneOptions): SystemOneClient;

package/dist/application-CwpOIOTt.mjs

@@ -0,0 +1 @@
+export{t as defineApplication,r as generatePluginFilesIfNeeded}from"./application-Nce5z46R.mjs";