@tailor-platform/sdk 2.34.0 → 2.35.0

package/CHANGELOG.md

@@ -1,5 +1,31 @@
 # @tailor-platform/sdk
 
+## 2.35.0
+
+### Minor Changes
+
+- [#2810](https://github.com/tailor-platform/sdk/pull/2810) [`41bf7ea`](https://github.com/tailor-platform/sdk/commit/41bf7ea9046e42b5c134b768d74772ea44e82c92) Thanks [@toiroakr](https://github.com/toiroakr)! - `tailor tailordb migration generate --init` now accepts `--namespace <name>` to reset only that namespace's `migrations/` directory and recreate its `0000`. Other namespaces' migration files are left untouched, and the confirmation lists only the target namespace. Without `--namespace`, `--init` still deletes the migrations of every namespace that has migrations configured.
+
+- [#2713](https://github.com/tailor-platform/sdk/pull/2713) [`545cf4f`](https://github.com/tailor-platform/sdk/commit/545cf4f0ef433a70ccb87b64d975430da60260b9) Thanks [@toiroakr](https://github.com/toiroakr)! - The PGlite schema from `kyselyTypePlugin` and the `db.pglite.ts` written for a migration now reject deleting a parent, or changing the key a row points at, while a row still points at it through an array field or a field inside a nested object, as the platform does. A test that deletes a parent before the rows pointing at it now fails with `violates foreign key constraint`; delete the child rows first.
+
+### Patch Changes
+
+- [#2795](https://github.com/tailor-platform/sdk/pull/2795) [`30281c1`](https://github.com/tailor-platform/sdk/commit/30281c1236f8da04e09752a218e8a8f3a9d8ac15) Thanks [@dqn](https://github.com/dqn)! - Fix bundling of a `.start()` call on a local variable that shares its name with an imported workflow or job when the variable is declared in a `switch` case, a named class expression, a namespace, or a static block. The bundler rewrote the call or failed instead of leaving it as written.
+
+- [#2817](https://github.com/tailor-platform/sdk/pull/2817) [`9ff6bcf`](https://github.com/tailor-platform/sdk/commit/9ff6bcf721bbd534cfb2e5c9ebe3ba604e74dc69) Thanks [@toiroakr](https://github.com/toiroakr)! - `tailor deploy` no longer fails when it cannot restore the secret vault of an IdP client whose name the platform rejects when reading the client, such as a name shorter than three characters. It prints a warning for that client and continues.
+
+- [#2815](https://github.com/tailor-platform/sdk/pull/2815) [`1ee6cc5`](https://github.com/tailor-platform/sdk/commit/1ee6cc5386c8b135630780ca220f860506c0b934) Thanks [@dqn](https://github.com/dqn)! - `tailor tailordb migration generate` no longer writes a `10000` migration directory, which no command reads, after a namespace reaches migration 9999. Before writing, it now checks that every namespace has enough migration numbers left, including with `--data-only` and for a field type conversion, which needs two. If any namespace does not, it fails with `MIGRATION_NUMBER_EXHAUSTED` without writing a migration in any namespace, and the error names the `tailor tailordb migration rebaseline` command to run.
+
+- [#2794](https://github.com/tailor-platform/sdk/pull/2794) [`45e5b65`](https://github.com/tailor-platform/sdk/commit/45e5b6540a91a7e622643dff5d29938022225dfd) Thanks [@dqn](https://github.com/dqn)! - Remove `@__PURE__` and `@__NO_SIDE_EFFECTS__` comments from bundled resolvers, executors, workflow jobs, auth hooks, HTTP adapters, and `tailor function run` scripts, and minify the scripts `tailor query` runs, to make them smaller.
+
+- [#2793](https://github.com/tailor-platform/sdk/pull/2793) [`ca193b9`](https://github.com/tailor-platform/sdk/commit/ca193b9a87a92bd0c67b5dd397b3ce2ff653de8a) Thanks [@dqn](https://github.com/dqn)! - `tailor deploy` no longer runs a migration's `main` script again after it could not confirm whether an earlier run of it succeeded (`MIGRATION_OUTCOME_UNKNOWN`), including with `--no-schema-check`, in a namespace without a migration checkpoint, and after the deploy process stopped while the script ran. The migration now stays recorded as in progress while its script runs, and until you settle a run the deploy could not confirm, `tailor deploy` stops before changing anything with `MIGRATION_OUTCOME_UNSETTLED`, which reports how the run stands.
+  
+  Settle such a run with `tailor tailordb migration resolve`: `--complete` when it succeeded, `--rollback` when it failed, was canceled, or did not start. `resolve` now reads how the run ended, shows it (`runStatus` under `--json`), and warns when the option you passed does not fit. The earlier advice to run `tailor tailordb migration sync` no longer applies to these runs: `sync` refuses to run while the migration is recorded. `tailor tailordb migration status` reports the run as in progress, with `inProgressMigrationRun: "main"` under `--json`. Earlier SDK versions cannot read this record and refuse to deploy until the migration is settled.
+
+- [#2795](https://github.com/tailor-platform/sdk/pull/2795) [`30281c1`](https://github.com/tailor-platform/sdk/commit/30281c1236f8da04e09752a218e8a8f3a9d8ac15) Thanks [@dqn](https://github.com/dqn)! - Field and table definitions written with `db` and `t` in your own code no longer keep an otherwise unused call in bundled resolvers, executors, workflow jobs, auth hooks, and `tailor function run` scripts, which makes bundles that import shared schema modules smaller.
+
+- [#2729](https://github.com/tailor-platform/sdk/pull/2729) [`bfe410f`](https://github.com/tailor-platform/sdk/commit/bfe410fbf6b9f9f9b560e79a0326f78a76011f11) Thanks [@toiroakr](https://github.com/toiroakr)! - `.unique()` and `.index()` on a field inside `db.object()` are now applied to the deployed schema. Before, they were recorded in the migration snapshot but sent to the platform as off, so duplicate values were stored, and the next `tailor deploy` of a project with such a field stopped with `MIGRATION_REMOTE_DRIFT`, and `tailor tailordb migration validate` failed the same way. The PGlite schema that `kyselyTypePlugin` and the migration `db.pglite.ts` generate now enforces `.unique()` on such a field too, so local tests reject the duplicates the platform rejects. After upgrading, run `tailor deploy --no-schema-check` once to apply the setting; later deploys need no flag. `.unique()` and `.index()` on a field inside an array of objects (`db.object(..., { array: true })`) now fail with an error, because the platform does not reject duplicate values there. If stored rows already hold duplicate values for a field that gains `.unique()`, that deploy fails with a unique index error and the schema stays unchanged until the duplicates are resolved.
+
 ## 2.34.0
 
 ### Minor Changes

package/dist/{application-CwpOIOTt.mjs → application-Bj2MtL-d.mjs}

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