@tailor-platform/sdk 2.37.0 → 2.38.0

package/CHANGELOG.md

@@ -1,5 +1,65 @@
 # @tailor-platform/sdk
 
+## 2.38.0
+
+### Minor Changes
+
+- [#2921](https://github.com/tailor-platform/sdk/pull/2921) [`e1b9d5f`](https://github.com/tailor-platform/sdk/commit/e1b9d5fa974b0f770728c7f04b03706896211bf7) Thanks [@dqn](https://github.com/dqn)! - `tailor tailordb migration validate` now fails, with the error code `tailor deploy` reports, when a migration an earlier deploy left in progress would stop the next deploy, and accepts `--migration-skip-steps` to check the steps to skip the way `tailor deploy` does
+
+- [#2869](https://github.com/tailor-platform/sdk/pull/2869) [`8c8ae7d`](https://github.com/tailor-platform/sdk/commit/8c8ae7df02f8c4394988e21d5bda0acc657f1e97) Thanks [@mocchira](https://github.com/mocchira)! - After a command finishes in an interactive terminal, `tailor` now lists your unread WARNING and CRITICAL platform notifications briefly on stderr, with pointers to `tailor notification list` and `tailor notification read <id>`. A CRITICAL notification is listed ahead of newer WARNINGs. It is best effort: the lookup runs alongside the command, and if it has not answered when the command ends, `tailor` waits at most 150 ms more before dropping it. It never changes a command's exit code, and it marks nothing read. It keeps appearing after each command until you read the notifications with `tailor notification read` or dismiss them. After a failed lookup it pauses for 5 minutes, so a platform outage does not cost a request per command. It is never shown in CI, under `--json`, in a pipe, or after help output. It is also skipped after `login`, `logout`, `auth`, `api`, `query` and the `notification` commands themselves, and after commands that only work locally: `init`, `generate`, `show`, `plugin`, `skills`, `completion`, `crashreport`, `upgrade`, `profile`, `open`, and `user` other than `user pat`. Set `TAILOR_NOTIFICATION_BANNER=off` to turn it off.
+
+- [#2868](https://github.com/tailor-platform/sdk/pull/2868) [`8369949`](https://github.com/tailor-platform/sdk/commit/8369949dc63974b0174b71cafe85ebe74b1eddb2) Thanks [@mocchira](https://github.com/mocchira)! - New `tailor notification` commands read the platform notifications sent to you (alerts, incidents, maintenance notices and announcements), the same inbox the Console shows:
+  
+  - `tailor notification list` lists your inbox, with `--category`, `--severity`, `--unread`, `--scope-workspace` and `--scope-organization` filters and shows the 50 newest by default (`--limit N` to change it, `--limit 0` for all).
+  - `tailor notification read <id...>` prints a notification (title, metadata, body, and action links, with Console paths given as full Console URLs) and marks it read; `--no-mark-read` only displays it. IDs that are not found are reported after the others are shown, and a read-only login shows notifications without marking them read.
+  - `tailor notification dismiss <id>` removes a notification from your inbox. This cannot be undone, so it is refused on a read-only profile.
+  
+  All three support `--json`.
+
+- [#2895](https://github.com/tailor-platform/sdk/pull/2895) [`0c15750`](https://github.com/tailor-platform/sdk/commit/0c1575093b5aba8dc47296a66513f1c500f72cfb) Thanks [@dqn](https://github.com/dqn)! - The CLI now loads `--env-file` and `--env-file-if-exists` before it reads its options, so values from an env file fill every option backed by an environment variable, the same as shell variables: for example `--config` from `TAILOR_CONFIG_PATH`, `--organization-id` from `TAILOR_PLATFORM_ORGANIZATION_ID` in `organization` commands, and the client ID and secret of `login --machine-user`. Previously these options kept their defaults or failed validation. A repeated `--env-file` now loads every file instead of only the last one; `createCommonArgs()` parses both options as string arrays. CLI plugins can load env files the same way by calling the new `loadEnvFilesFromArgv` export of `@tailor-platform/sdk/cli` from their `setup` hook, passing it the options they give `createCommonArgs()`. `deploy`, `workspace create`, and `tailordb migration test` now also ignore an empty `TAILOR_PLATFORM_ORGANIZATION_ID` or `TAILOR_PLATFORM_FOLDER_ID` set in the shell, as they already did for one loaded from an env file; an organization or folder ID that is not a UUID now fails `tailordb migration test` with `OPTIONS_INVALID` instead of `INVALID_ARGUMENTS`. When a CLI plugin is given an env file, `tailor` also loads it before dispatching, so a `TAILOR_CONFIG_PATH` in the file reaches the plugin instead of the config file found from the current directory.
+
+- [#2911](https://github.com/tailor-platform/sdk/pull/2911) [`91311ea`](https://github.com/tailor-platform/sdk/commit/91311ea1b25ca0832bda901e65fcb554d0bc52b1) Thanks [@dqn](https://github.com/dqn)! - **Breaking change (beta)**: Remove `tailor tailordb migration set`. It moved a namespace's migration checkpoint without changing its tables, so the checkpoint could stop matching the tables and the next deploy stopped with `MIGRATION_REMOTE_DRIFT`. Use `tailor tailordb migration sync <N>` instead: when the tables already match migration `<N>`, only the checkpoint changes, and `--force` replaces another migration history ID as `set --force` did. To re-run a failed migration in a development workspace, run `tailor tailordb migration sync <previous>`, which also removes the fields the failed migration added and deletes the tables it added together with their data. Settle a migration that an earlier deploy left in progress with `tailor tailordb migration resolve --complete` or `--rollback`. Errors and documentation that suggested `set` now suggest `sync`.
+
+### Patch Changes
+
+- [#2897](https://github.com/tailor-platform/sdk/pull/2897) [`5cb6958`](https://github.com/tailor-platform/sdk/commit/5cb695867cdcd6359c7c0fce2434906af60335f7) Thanks [@dqn](https://github.com/dqn)! - `tailor setup ci preview` now deletes the preview workspace of a pull request closed with merge conflicts, which GitHub never ran the preview workflow's cleanup for. Cleanup moves into a separate workflow, `tailor-<name>-preview-cleanup.yml`, which starts on `pull_request_target` and runs only the default branch's code. Run `tailor setup update` to regenerate existing preview workflows: the `tailor-preview-cleanup` job moves into the new workflow together with the steps and settings you added to it, and `setup update` stops if a job of yours `needs` it. A job of yours in the preview workflow that runs when the pull request is closed no longer runs; `setup` warns about each one whose `if` contains an `== 'closed'` comparison, so you can move it into the cleanup workflow. Commit the new workflow to the default branch, since GitHub runs it from there, and allow the default branch in the target's GitHub Environment if it restricts which branches can deploy.
+
+- [#2942](https://github.com/tailor-platform/sdk/pull/2942) [`734bf30`](https://github.com/tailor-platform/sdk/commit/734bf3090744eaaacc9a07872190534a67ed845e) Thanks [@dqn](https://github.com/dqn)! - The CLI now retries a Platform request, such as creating a workspace or applying a resource during `tailor deploy`, when the connection closes before a secure connection is established, instead of failing with `Client network socket disconnected before secure TLS connection was established`
+
+- [#2843](https://github.com/tailor-platform/sdk/pull/2843) [`748a0d6`](https://github.com/tailor-platform/sdk/commit/748a0d686bc3863fd3796aa3b984823e1065a7f9) Thanks [@toiroakr](https://github.com/toiroakr)! - Improve SQL and GraphQL syntax highlighting in the `query` REPL and make the REPL start faster.
+
+- [#2843](https://github.com/tailor-platform/sdk/pull/2843) [`345da01`](https://github.com/tailor-platform/sdk/commit/345da01d5918578e265013c96d1d7e6e9a4fba74) Thanks [@toiroakr](https://github.com/toiroakr)! - An executor whose GraphQL operation passes a `DocumentNode`, such as the result of `parse()` from `graphql` or a `gql` tagged template, to `query` now deploys it as the printed GraphQL query. It was deployed as the text `[object Object]`, which is not a valid GraphQL query. Passing the query as a string is unchanged.
+
+- [#2843](https://github.com/tailor-platform/sdk/pull/2843) [`aca6f28`](https://github.com/tailor-platform/sdk/commit/aca6f28f73294b88549fe1815230435d042b0f01) Thanks [@toiroakr](https://github.com/toiroakr)! - The SDK no longer installs `graphql`, `@urql/core`, or `wonka` as dependencies. The `DocumentNode` type that HTTP adapter `input` handlers and the executor `query` option accept is now included in the SDK's type declarations, so a project without `graphql` still gets `query` type-checked, and documents typed with `graphql` 16 or 17, including `TypedDocumentNode`, keep type-checking. If your project imports `graphql`, `@urql/core`, or `wonka` without declaring it, which only works when your package manager hoists it, add it to your own dependencies. If you use `graphql` 15 with `skipLibCheck: true`, passing a `parse()` result to the executor `query` option is now a type error, as it already was for HTTP adapters.
+
+- [#2914](https://github.com/tailor-platform/sdk/pull/2914) [`53c8474`](https://github.com/tailor-platform/sdk/commit/53c84745fcb2b65a1171900c6ec628819364324e) Thanks [@dqn](https://github.com/dqn)! - `tailor deploy` no longer stops with `MIGRATION_REMOTE_DRIFT` when an earlier deploy left a migration's pre-migration schema changes or maintenance mode in place without recording the migration as in progress, for example because it stopped right after those changes or could not roll them back. It runs that migration again from the start. `tailor tailordb migration resolve --rollback` returns such a namespace to its checkpoint without deploying, and `tailor tailordb migration validate` reports it as valid.
+
+- [#2925](https://github.com/tailor-platform/sdk/pull/2925) [`77c7bed`](https://github.com/tailor-platform/sdk/commit/77c7bedde797fb49c1633aa0601765b7f51e0d2b) Thanks [@dqn](https://github.com/dqn)! - `tailor tailordb migration validate` now also fails, with the error code `tailor deploy` reports, when a pending migration script has no machine user to run it or cannot be bundled
+
+- [#2932](https://github.com/tailor-platform/sdk/pull/2932) [`58eec18`](https://github.com/tailor-platform/sdk/commit/58eec1816ed7483d0d4fec484e0dddd3ff033272) Thanks [@dqn](https://github.com/dqn)! - `errorToJson` from `@tailor-platform/sdk/cli` now returns the envelope that `serializeError` writes, so its result can be embedded in JSON output: string values come without colors and with registered secrets redacted, and a context that cannot be written as JSON is left out along with the stack
+
+- [#2940](https://github.com/tailor-platform/sdk/pull/2940) [`70d504e`](https://github.com/tailor-platform/sdk/commit/70d504ec8e05e83bb9ebf0788510c4fbf6279578) Thanks [@dqn](https://github.com/dqn)! - `.serial()` formats with an octal `%o` specifier or a literal `%%` now reproduce in the PGlite schema: `tailor generate` with `kyselyTypePlugin({ pgliteSchemaPath })` no longer fails on them, `tailor tailordb migration generate` writes `db.pglite.ts`, and `tailor tailordb migration script --with-test` also writes `migrate.pglite.test.ts`.
+
+- [#2916](https://github.com/tailor-platform/sdk/pull/2916) [`b1f5a4b`](https://github.com/tailor-platform/sdk/commit/b1f5a4b19392bcdd14f7e4cb695a1b6d4d124c7d) Thanks [@dqn](https://github.com/dqn)! - `tailor deploy` now finishes deleting the tables a migration removed when an earlier deploy committed that migration but failed or was interrupted before deleting them, instead of stopping with remote schema drift until you delete them by hand. The deploy lists those tables among its deletions and deletes them with their data after confirmation, and `tailor tailordb migration validate` reports them as tables the next deploy deletes.
+
+- [#2882](https://github.com/tailor-platform/sdk/pull/2882) [`9bf90bb`](https://github.com/tailor-platform/sdk/commit/9bf90bb9d1bf818ac3a294b3fe9ed68301b7eb2f) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency amaro to v1.3.0
+
+- [#2905](https://github.com/tailor-platform/sdk/pull/2905) [`bc3dd45`](https://github.com/tailor-platform/sdk/commit/bc3dd45ccbb67641f9c7636594a4fdcda963dd4e) Thanks [@renovate](https://github.com/apps/renovate)! - chore(deps): update dependency @​types/node to v26.6.6
+
+- [#2910](https://github.com/tailor-platform/sdk/pull/2910) [`dd0cd4f`](https://github.com/tailor-platform/sdk/commit/dd0cd4fd422909ee99921dbc4b22aed863c901f8) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency confbox to v0.3.2
+
+- [#2929](https://github.com/tailor-platform/sdk/pull/2929) [`173d9d2`](https://github.com/tailor-platform/sdk/commit/173d9d2f3830fff04e90d64600f71fa16d3dd221) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency es-toolkit to v1.53.1
+
+- [#2924](https://github.com/tailor-platform/sdk/pull/2924) [`0c7fed1`](https://github.com/tailor-platform/sdk/commit/0c7fed120e25fdfea9c71f2035c74870b92fc7b2) Thanks [@dqn](https://github.com/dqn)! - Apply local TailorDB table definitions that the pending migrations do not include in the same `tailor deploy --no-schema-check` run, once the migrations complete, instead of leaving them to the next deploy. The deploy lists those tables, and fails with `MIGRATION_LOCAL_DEFINITIONS_FAILED` after the migrations are applied when one of them cannot be applied.
+
+- [#2913](https://github.com/tailor-platform/sdk/pull/2913) [`b7ffa31`](https://github.com/tailor-platform/sdk/commit/b7ffa31245abac1fb97dbfc51768bc55a2ce2dfa) Thanks [@dqn](https://github.com/dqn)! - The `tailor tailordb migration generate` and `tailor deploy` commands that `tailor tailordb migration rebaseline` suggests now pass `--config` the way its other suggested commands do: relative to the current directory, and omitted for the default config. They passed the config file's absolute path before.
+
+- [#2920](https://github.com/tailor-platform/sdk/pull/2920) [`a84ad7e`](https://github.com/tailor-platform/sdk/commit/a84ad7eb033dc5d687c1cea8a8fcd9238ebad27a) Thanks [@dqn](https://github.com/dqn)! - Fix `.start()` calls in a workflow, resolver, or executor file that declares its own `tailor` (for example, a workflow job exported as `tailor`), which failed at runtime after deploy.
+
+- [#2915](https://github.com/tailor-platform/sdk/pull/2915) [`d385bbb`](https://github.com/tailor-platform/sdk/commit/d385bbbb122eafbdef90f00d8464fc04ee6f58cd) Thanks [@dqn](https://github.com/dqn)! - `tailor deploy` now resumes a multi-step migration whose earlier deploy stopped during or after the post-migration schema changes but before recording the checkpoint, for example because the process was killed or the checkpoint write failed. It used to stop with `MIGRATION_REMOTE_DRIFT` on the tables that already had the post-migration schema, until `tailor tailordb migration resolve --complete` settled the migration or a deploy ran with `--no-schema-check`. Each table may now have either the pre-migration or the post-migration schema of that migration, and `tailor tailordb migration validate` accepts the same. The warning for a checkpoint write that could not be confirmed now says to deploy again for such a migration instead of to repair the checkpoint.
+
+- [#2919](https://github.com/tailor-platform/sdk/pull/2919) [`287925a`](https://github.com/tailor-platform/sdk/commit/287925ab6dd1d222ba55ee327bb196d6f761115e) Thanks [@dqn](https://github.com/dqn)! - `.unique()` on a field with a `keyOnly` relation is now kept. Before, the relation silently dropped it, so the field was deployed without a unique constraint, and a relation that used the field as its `toward.key` failed with `which must be unique`. The PGlite schema that `kyselyTypePlugin` and the migration `db.pglite.ts` generate, and the seed schema that `seedPlugin` generates, now declare the constraint too. After upgrading, a deployed table with such a field gains the unique constraint on its next `tailor deploy`; if stored rows hold duplicate values for the field, that deploy fails until the duplicate rows are updated to distinct values or deleted. In a namespace with `migration.directory`, `tailor deploy` stops with `MIGRATION_SCHEMA_CHECK_FAILED` until `tailor tailordb migration generate` creates the migration, and until the `TODO()` in its `migrate.ts`, which sets a new value on each duplicate row, is replaced. The new value must also be a key that exists in the referenced table.
+
 ## 2.37.0
 
 ### Minor Changes

package/dist/{application-83WVdH85.mjs → application-Bz80INH4.mjs}

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