Release - main

[tailor-platform-pr-trigger]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@tailor-platform/sdk@2.28.0

Minor Changes

• #2589 4bf9fd5 Thanks @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.

• #2583 23b3b36 Thanks @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 eab2d88 Thanks @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.

Patch Changes

• #2588 3de270f Thanks @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 b57a21f Thanks @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.

@tailor-platform/sdk-plugin-setup@0.10.0

Minor Changes

• #2572 610a2ca Thanks @dqn! - tailor setup ci branch, tag, and preview accept --package-manager (pnpm, npm, yarn, or bun) to choose the package manager the generated workflow uses, for example to generate the workflow before the lockfile exists. .github/tailor.lock records the choice, and tailor setup update keeps it.

  Without the flag, the package manager is still detected from the lockfile at the repository root (now including npm-shrinkwrap.json), and otherwise from the packageManager or devEngines.packageManager field of the root package.json. When neither names one, setup ci and setup update stop with an error instead of silently choosing npm, which produced a workflow that failed in CI without a lockfile at the repository root. setup remains a beta command, so this ships as an immediate change rather than going through a deprecation cycle.

Patch Changes

• #2588 3de270f Thanks @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.
• Updated dependencies [4bf9fd5, 3de270f, b57a21f, 23b3b36, eab2d88]:
  • @tailor-platform/sdk@2.28.0

@tailor-platform/create-sdk@2.28.0

Patch Changes

• #2597 cb76a09 Thanks @toiroakr! - Accept the project name as --name again in npm create @tailor-platform/sdk -- --name my-app. After the @politty/zod 0.4 update the option was ignored with an Unknown option warning and the command asked for the name interactively, which stalled non-interactive scripts. Passing the name positionally, as in my-app, is unchanged.

• #2588 3de270f Thanks @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.

@tailor-platform/sdk-codemod@0.9.2

Patch Changes

• #2588 3de270f Thanks @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.

@tailor-platform/sdk-plugin-seed@0.3.8

Patch Changes

• #2588 3de270f Thanks @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.
• Updated dependencies [4bf9fd5, 3de270f, b57a21f, 23b3b36, eab2d88]:
  • @tailor-platform/sdk@2.28.0

@tailor-platform/sdk-plugin-tailordb-erd@0.2.9

Patch Changes

• #2588 3de270f Thanks @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.
• Updated dependencies [4bf9fd5, 3de270f, b57a21f, 23b3b36, eab2d88]:
  • @tailor-platform/sdk@2.28.0

[pkg-pr-new]

Open in StackBlitz

@tailor-platform/create-sdk

pnpm add https://pkg.pr.new/tailor-platform/sdk/@tailor-platform/create-sdk@7521b5c

@tailor-platform/eslint-plugin-sdk

pnpm add https://pkg.pr.new/tailor-platform/sdk/@tailor-platform/eslint-plugin-sdk@7521b5c

@tailor-platform/sdk

pnpm add https://pkg.pr.new/tailor-platform/sdk/@tailor-platform/sdk@7521b5c

@tailor-platform/sdk-plugin-frontend

pnpm add https://pkg.pr.new/tailor-platform/sdk/@tailor-platform/sdk-plugin-frontend@7521b5c

@tailor-platform/sdk-plugin-seed

pnpm add https://pkg.pr.new/tailor-platform/sdk/@tailor-platform/sdk-plugin-seed@7521b5c

@tailor-platform/sdk-plugin-setup

pnpm add https://pkg.pr.new/tailor-platform/sdk/@tailor-platform/sdk-plugin-setup@7521b5c

@tailor-platform/sdk-plugin-tailordb-erd

pnpm add https://pkg.pr.new/tailor-platform/sdk/@tailor-platform/sdk-plugin-tailordb-erd@7521b5c

commit: 7521b5c

[github-actions]

🗺️ ERD preview

Self-contained ERD viewer HTML built for this run. Each viewer can switch between the current schema and a diff against base branch main.

• analyticsdb: view
• tailordb: view

[github-actions]

Code Metrics Report (packages/sdk)

	main (ad65aa6)	#2596 (b7a1600)	+/-
Coverage	87.1%	87.1%	0.0%
Code to Test Ratio	1:0.5	1:0.5	0.0

Details

  |                    | main (ad65aa6) | #2596 (b7a1600) | +/-  |
  |--------------------|----------------|-----------------|------|
  | Coverage           |          87.1% |           87.1% | 0.0% |
  |   Files            |            547 |             547 |    0 |
  |   Lines            |          23577 |           23577 |    0 |
  |   Covered          |          20539 |           20539 |    0 |
  | Code to Test Ratio |          1:0.5 |           1:0.5 |  0.0 |
  |   Code             |         191586 |          191586 |    0 |
  |   Test             |         106355 |          106355 |    0 |

SDK Configure Bundle Size

	main (ad65aa6)	#2596 (b7a1600)	+/-
configure-index-size	13.82KB	13.82KB	0KB
dependency-chunks-size	25.81KB	25.81KB	0KB
total-bundle-size	39.63KB	39.63KB	0KB

Runtime Performance

	main (ad65aa6)	#2596 (b7a1600)	+/-
Generate Median	1,884ms	1,896ms	+12ms
Generate Max	1,905ms	1,907ms	+2ms
Apply Build Median	2,066ms	2,079ms	+13ms
Apply Build Max	2,089ms	2,108ms	+19ms

Type Performance (instantiations)

	main (ad65aa6)	#2596 (b7a1600)	+/-
tailordb-basic	48,202	48,202	0
tailordb-optional	4,777	4,777	0
tailordb-relation	4,849	4,849	0
tailordb-validate	703	703	0
tailordb-hooks	5,842	5,842	0
tailordb-object	13,771	13,771	0
tailordb-enum	1,628	1,628	0
resolver-basic	12,618	12,618	0
resolver-nested	35,917	35,917	0
resolver-array	24,554	24,554	0
executor-schedule	4,489	4,489	0
executor-webhook	1,130	1,130	0
executor-record	5,452	5,452	0
executor-resolver	6,306	6,306	0
executor-operation-function	1,118	1,118	0
executor-operation-gql	1,126	1,126	0
executor-operation-webhook	1,137	1,137	0
executor-operation-workflow	1,931	1,931	0

---

Reported by octocov