[renovate]

This PR contains the following updates:

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

---

Release Notes

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

v2.33.0

Compare Source

Minor Changes

• #​2742 4f3f30c Thanks @​mocchira! - customDomains entries can now name a destination, moving a domain to another static website — in the same workspace or a different one — without downtime, a new certificate, or a DNS change:

  defineStaticWebSite("my-website", {
    customDomains: [{ domain: "app.example.com", transferTo: { workspaceId: "..." } }],
  });

  Deploying opens the offer; the receiving side accepts it by listing the domain normally and deploying. tailor deploy reports an open offer and says when the domain has moved and the entry can be deleted.

  While an offer is open, tailor deploy and tailor remove refuse to remove the domain or the static website holding it, at plan time and before anything is applied. A plan also fails, rather than quietly doing nothing, when an entry names a domain the site does not hold and no transfer from this workspace accounts for it, or when the domain is still being removed.

  tailor deploy also now takes ownership of a custom domain that already exists but carries no SDK labels, instead of trying to add it again — the recovery path when a previous deploy lost the response, or when the domain was added through the API or console.

• #​2591 59fcb9a Thanks @​toiroakr! - Let a TailorDB migration script that exports steps roll back instead of staying in progress when a step fails. Export onFailure = "rollback" next to steps and tailor deploy restores the pre-migration schema, clears the in-progress record, and takes the tables out of maintenance mode. The deploy then fails with the step's error under the code MIGRATION_ROLLED_BACK, and the next deploy runs every step again from the beginning. Nothing is rolled back while the run may still be executing, or when the in-progress record cannot be cleared. If some tables cannot be rolled back, the deploy warns which tables need manual repair. Without onFailure, or with "resume", a failed run stays in progress as before

• #​2700 6eb2033 Thanks @​toiroakr! - The db.pglite.ts that tailor tailordb migration generate writes now enforces relations: a row pointing at a parent that does not exist is rejected, as on the platform. Migration tests that stage a row whose parent is missing must create the parent first or stage the row with prepareFixtures. A relation the pre-migration schema cannot satisfy is left unenforced: one whose pending type change leaves the field a different type from its target, or one the migration retargets.

  prepareFixtures from @tailor-platform/sdk/vitest writes a test's starting records with relations unchecked, so a migration test can stage rows that predate a relation, and checks them again before the script runs. The migration PGlite test scaffold uses it.

Patch Changes

• #​2741 6f6ca9f Thanks @​mocchira! - tailor staticwebsite domain list and domain get now report a domain being removed as removing instead of unknown, and tailor api can inspect and call the custom domain transfer endpoints (RequestCustomDomainTransfer, CancelCustomDomainTransfer, AcceptCustomDomainTransfer, GetCustomDomainTransfer, ListCustomDomainTransfers).

• #​2736 8595d14 Thanks @​toiroakr! - tailor login now shows an HTML page in the browser after authentication instead of raw JSON, telling you to close the tab and return to the terminal. The page follows the system light/dark theme. A failed login shows the reason in the page as well, and tailor authconnection authorize shows the same pages on success and failure.

• #​2740 ef844ff Thanks @​renovate! - fix(deps): update dependency @​​napi-rs/keyring to v2.1.2

• #​2760 a7d1cb8 Thanks @​renovate! - fix(deps): update @​​inquirer

• #​2766 15b6f4a Thanks @​renovate! - fix(deps): update dependency pkg-types to v2.4.0

• #​2718 8927563 Thanks @​toiroakr! - The tailor query REPL now highlights SQL block comments (/* ... */) and GraphQL block strings ("""...""") that span multiple lines, and also colours SQL -- comments and trailing GraphQL # comments.

• #​2731 bbfb9b1 Thanks @​dqn! - Fix plugin-generated resolvers being silently ignored. Resolver output from table and namespace hooks is now loaded, bundled, and deployed to the resolver namespace with the same name as the hook's TailorDB namespace. The two are separate namespaces that only share the name; the resolver namespace is created automatically when it is not configured, and its settings apply when it is. Resolvers that your existing plugins already return are deployed on the next deploy; without defaultPermission on their resolver namespace, anonymous callers can reach them.

• #​2747 d52ec40 Thanks @​dqn! - Internal refactoring: remove the unused asynchronous variants of the SDK's internal TypeScript loader hooks. Loading .ts config and resource files is unchanged.

• #​2744 559d442 Thanks @​dqn! - Reject duplicate generated enum constant names instead of silently overwriting definitions. Duplicates with identical values, which previously generated successfully, now fail too. Rename conflicting tables or fields to give their enum constants unique names.

---

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.

[anukiransolur]

@tailor-platform/sdk 2.32.0 → 2.33.0 (minor). New opt-in features (customDomains transferTo, migration onFailure rollback) plus fixes. Behavior changes checked against the tutorial steps, none apply: duplicate enum constant names now fail generate (Project/Task status constants are distinct); plugin-generated resolvers are now deployed (kyselyTypePlugin generates types only); db.pglite.ts relation enforcement (no migration tests here). CI passes on all steps, and generate + tsc also pass on 2.33.0 for the code in #137. Only package.json/package-lock.json change, so no overlap with #137. Safe to merge.