[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.36.0

Minor Changes

• #2829 6cbf20b Thanks @dqn! - Breaking change (beta): A query issued on a createKyselyPGlite instance while one of its transactions is open now waits for the transaction to finish. Before, the query ran inside the transaction, and when it failed, the commit silently discarded the transaction's writes. A query on the outer instance from inside the transaction now never finishes and the test times out; run it on trx instead.

• #2847 55e9a94 Thanks @jackchuka! - Breaking change: workspace create, workspace creation during deploy, and the programmatic createWorkspace() now require an organization. Pass --organization-id (or set TAILOR_PLATFORM_ORGANIZATION_ID), or set a default organization with tailor user update --default-organization-id (not read while TAILOR_PLATFORM_TOKEN or TAILOR_TOKEN is set). Without one, interactive deploy asks which organization to create the workspace in; workspace create, createWorkspace(), and non-interactive deploy fail instead of creating a workspace outside any organization.

Patch Changes

• #2833 e3e3bac Thanks @dqn! - Adding a relation to an existing field is now a breaking change in tailor tailordb migration generate, and the migration needs a script. It was recorded as non-breaking, so values that point at no record stayed stored, and after deploy the platform rejected any later update of those rows, even one that changes another field. The generated migrate.ts finds those values and asks for their new reference with TODO, or leaves the elements of an array field to a single TODO. The foreign key is applied after the script runs, so the script and the other steps of the migration can update those rows. A relation added to a field inside db.object() stays non-breaking. The script generated for a relation retargeted to another table now also works when the relation points at its own table or at a key other than id.

• #2831 2d6217b Thanks @dqn! - .unique() and .index() on a db.object() field itself now fail type checking, and tailor generate and tailor deploy stop with an error naming the field. Before, such a table field failed to deploy with an internal platform error, and such a member of another db.object() was deployed without the setting, so in a namespace with migration.directory every later deploy stopped with MIGRATION_REMOTE_DRIFT. Remove the modifier; for such a member in a namespace with migration.directory, then run tailor tailordb migration generate and tailor deploy --no-schema-check once.

• #2811 e229992 Thanks @toiroakr! - TailorDB namespaces that set the same migration.directory now fail with MIGRATION_DIRECTORY_CONFLICT, naming the namespaces and the shared directory, before any migration command or tailor deploy reads or writes migration files. Before, migration generate failed with a misleading "Possible rename(s) detected" error, and migration generate --init rebuilt the history of every namespace sharing the directory. Give each namespace its own migration.directory.

• #2828 eab9a23 Thanks @dqn! - Keep existing migration files when tailordb migration generate --init fails to load tables. Previously the migrations were deleted before the tables loaded, so an error such as a syntax error in a table file left the namespace with no migration history. The deletion confirmation now appears after the tables load.

• #2776 beacc64 Thanks @toiroakr! - tailor tailordb migration status now reports an error for a namespace whose remote checkpoint is ahead of the latest local migration, for example 0009 on the workspace while the local history ends at 0002. It used to show that namespace as up to date with no pending migrations. With maintenanceMode on, tailor deploy also records the maintenance mode with every migration checkpoint of a namespace instead of only the last one, so a deploy that stops after the first of several migrations leaves the record that tailor tailordb migration resolve and the next deploy use to lift the maintenance mode.

• #2835 0d4cd79 Thanks @dqn! - tailor remove now deletes every resource it lists. Before, when the only remaining resources were sub-resources such as TailorDB types, resolvers, IdP clients, auth configs, or auth connections, it listed them without deleting them. It now also lists workflow job functions; before, they were deleted without being listed, and when nothing else remained they were not deleted at all. Deploy plans, including the Plan: summary counts and --dry-run --json changes, now list each workflow job function deletion as its own jobFunction entry, so removing a workflow shows and counts its job functions on separate lines.

• #2822 b433a27 Thanks @renovate! - fix(deps): update dependency @​politty/zod to v0.6.3

• #2823 8712ec6 Thanks @renovate! - fix(deps): update dependency execa to v10.2.1

• #2824 5bf7e69 Thanks @renovate! - fix(deps): update @​opentelemetry

• #2826 2a0e726 Thanks @renovate! - fix(deps): update @​opentelemetry to v3

• #2842 8d3d70c Thanks @renovate! - fix(deps): update dependency es-toolkit to v1.53.0

• #2836 95ba73c Thanks @toiroakr! - The Stripe example in the incoming webhook docs now shows where to verify the stripe-signature header against rawBody, and links to Stripe's verification steps. The docs and the rawBody type of IncomingWebhookArgs now say that rawBody is delivered base64-encoded and has to be decoded to the original bytes before computing a signature.

• #2832 2c6242a Thanks @dqn! - When a .ts or .mts file the CLI loads cannot be parsed, report a SYNTAX_INVALID error naming the file, the line, and the syntax error. For a TailorDB type, resolver, executor, workflow, HTTP adapter, or function run file, or a file one of them imports, this replaces [object Object]. For a config, or a file it imports, it replaces UNEXPECTED_ERROR, and the GitHub Actions annotation is titled SYNTAX_INVALID instead of SyntaxError.

@tailor-platform/sdk-codemod@0.10.5

Patch Changes

• #2822 b433a27 Thanks @renovate! - fix(deps): update dependency @​politty/zod to v0.6.3

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

Patch Changes

• #2822 b433a27 Thanks @renovate! - fix(deps): update dependency @​politty/zod to v0.6.3
• Updated dependencies [e3e3bac, 6cbf20b, 2d6217b, e229992, eab9a23, beacc64, 0d4cd79, b433a27, 8712ec6, 5bf7e69, 2a0e726, 8d3d70c, 95ba73c, 2c6242a, 55e9a94]:
  • @tailor-platform/sdk@2.36.0

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

Patch Changes

• #2822 b433a27 Thanks @renovate! - fix(deps): update dependency @​politty/zod to v0.6.3
• Updated dependencies [e3e3bac, 6cbf20b, 2d6217b, e229992, eab9a23, beacc64, 0d4cd79, b433a27, 8712ec6, 5bf7e69, 2a0e726, 8d3d70c, 95ba73c, 2c6242a, 55e9a94]:
  • @tailor-platform/sdk@2.36.0

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

Patch Changes

• #2822 b433a27 Thanks @renovate! - fix(deps): update dependency @​politty/zod to v0.6.3
• Updated dependencies [e3e3bac, 6cbf20b, 2d6217b, e229992, eab9a23, beacc64, 0d4cd79, b433a27, 8712ec6, 5bf7e69, 2a0e726, 8d3d70c, 95ba73c, 2c6242a, 55e9a94]:
  • @tailor-platform/sdk@2.36.0

@tailor-platform/create-sdk@2.36.0

No changes in this release.

[pkg-pr-new]

Open in StackBlitz

@tailor-platform/create-sdk

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

@tailor-platform/eslint-plugin-sdk

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

@tailor-platform/sdk

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

@tailor-platform/sdk-plugin-frontend

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

@tailor-platform/sdk-plugin-seed

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

@tailor-platform/sdk-plugin-setup

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

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

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

commit: 2312069

[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 (0b684e4)	#2825 (5c60378)	+/-
Coverage	88.6%	88.6%	0.0%
Code to Test Ratio	1:0.5	1:0.5	0.0

Details

  |                    | main (0b684e4) | #2825 (5c60378) | +/-  |
  |--------------------|----------------|-----------------|------|
  | Coverage           |          88.6% |           88.6% | 0.0% |
  |   Files            |            578 |             578 |    0 |
  |   Lines            |          25557 |           25557 |    0 |
  |   Covered          |          22661 |           22661 |    0 |
  | Code to Test Ratio |          1:0.5 |           1:0.5 |  0.0 |
  |   Code             |         207779 |          207779 |    0 |
  |   Test             |         116987 |          116987 |    0 |

SDK Configure Bundle Size

	main (0b684e4)	#2825 (5c60378)	+/-
configure-index-size	13.82KB	13.82KB	0KB
dependency-chunks-size	25.76KB	25.76KB	0KB
total-bundle-size	39.58KB	39.58KB	0KB

Runtime Performance

	main (0b684e4)	#2825 (5c60378)	+/-
Generate Median	1,902ms	1,493ms	-409ms
Generate Max	2,278ms	1,560ms	-718ms
Apply Build Median	2,056ms	1,627ms	-429ms
Apply Build Max	2,470ms	2,186ms	-284ms

Type Performance (instantiations)

	main (0b684e4)	#2825 (5c60378)	+/-
tailordb-baseline	955	955	0
resolver-baseline	4,641	4,641	0
executor-baseline	848	848	0
tailordb-basic	2,385	2,385	0
tailordb-optional	1,167	1,167	0
tailordb-relation	3,808	3,808	0
tailordb-validate	186	186	0
tailordb-hooks	999	999	0
tailordb-object	1,892	1,892	0
tailordb-enum	574	574	0
resolver-basic	1,022	1,022	0
resolver-nested	3,405	3,405	0
resolver-array	1,954	1,954	0
executor-schedule	1,388	1,388	0
executor-webhook	47	47	0
executor-record-created	3,219	3,219	0
executor-record-updated	3,219	3,219	0
executor-record-deleted	3,219	3,219	0
executor-resolver	463	463	0
executor-operation-function	30	30	0
executor-operation-gql	43	43	0
executor-operation-webhook	50	50	0
executor-operation-workflow	211	211	0

---

Reported by octocov