[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@tailor-platform/sdk (source)	2.33.0 → 2.35.0

---

Release Notes

tailor-platform/sdk (@​tailor-platform/sdk)

v2.35.0

Compare Source

Minor Changes

• #​2810 41bf7ea Thanks @​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 545cf4f Thanks @​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 30281c1 Thanks @​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 9ff6bcf Thanks @​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 1ee6cc5 Thanks @​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 45e5b65 Thanks @​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 ca193b9 Thanks @​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 30281c1 Thanks @​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 bfe410f Thanks @​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.

v2.34.0

Compare Source

Minor Changes

• #​2669 f59f06e Thanks @​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 bc16821 Thanks @​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 9ddec31 Thanks @​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 c9bc40b Thanks @​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 4c42666 Thanks @​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 468bd4b Thanks @​dqn! - Internal refactor of the ownership checks tailor deploy and tailor remove run on existing resources. No observable behavior change.

• #​2752 b09d3c9 Thanks @​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 039f6f5 Thanks @​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 8000beb Thanks @​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 66c8c85 Thanks @​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 0628ad3 Thanks @​dqn! - Build resolver, executor, workflow job, and auth hook bundles through one shared step. Bundled output is unchanged.

• #​2748 35ce933 Thanks @​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 deeb82f Thanks @​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 30b9fa8 Thanks @​renovate! - fix(deps): update oxc

• #​2765 eb01ec6 Thanks @​renovate! - fix(deps): update dependency @​​politty/zod to v0.6.0

• #​2797 f202845 Thanks @​renovate! - chore(deps): lock file maintenance

• #​2804 8c20b0b Thanks @​renovate! - fix(deps): update dependency amaro to v1.2.2

• #​2805 c0641d2 Thanks @​renovate! - fix(deps): update dependency rolldown to v1.2.15

• #​2709 6eb202f Thanks @​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 eabbd2e Thanks @​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 b09cb46 Thanks @​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 07611f5 Thanks @​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 5461ed7 Thanks @​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.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.