Tendkit

Search documentation

Find a docs page

Get Started

Upgrading

Take upstream fixes into code you've copied and changed.

Copied code doesn't update itself. That's the point: you choose what to take, and when.

See what changed

Terminal
npx shadcn@latest add @tendkit/support --diff
npx shadcn@latest add @tendkit/channel-resend --diff

Apply the parts you want. The GitHub history explains why each change was made.

Keep diffs small

  • Keep the engine files (service.ts, text.ts, channels/*) as they are. Product logic belongs in your directory, notifier, storage and API.
  • Wrap the screens instead of editing them where you can: your provider, pages and customer panel.
  • When you do change a shared file, a short comment marking why makes the next diff easy to read.

Schema changes

When an update changes the support schema, regenerate your migration with Drizzle and review it like any other. Tendkit never migrates your database for you.