All Posts
February 12, 20260.1.22Jugg.ai

v0.1.22 — feat: add clientBranches and clientBranchSyncs tables to schema

Release v0.1.22: Client Branch Management Schema

February 12, 2026

What changed

  • Added clientBranches table — stores per-client branch configs including customizations (JSONB), sync status, auto-sync/auto-resolve settings, and branch lifecycle status (active/paused/archived)
  • Added clientBranchSyncs table — tracks individual sync operations per release, including merge strategy, conflict files, test results, and PR URLs
  • SQL migration 0007_client_branches.sql with foreign keys to projects and client_branches, plus composite indexes on (projectId, status) and (clientBranchId, status)
  • Exported ClientBranch and ClientBranchSync inferred TypeScript types

Why it matters

These tables are the data foundation for white-label client branch management. They enable upcoming work on the Branch Sync Agent and the /dashboard/branches UI.

Technical notes

  • Migration index: 0007
  • Both tables use text primary keys with crypto.randomUUID() defaults
  • customizations and testResults fields use jsonb for flexible structured data
  • conflictFiles uses a Postgres text[] array column

Release Notes

Successfully merged PR #62 and published release v0.1.22.

PR #62 — "feat: add clientBranches and clientBranchSyncs tables to schema"

  • Merged via squash merge (SHA: ac25966d056236bfcd866a63d26bb3fddfe8c51f)

Release v0.1.22 — "Client Branch Management Schema"

What was released:

  • Two new database tables (clientBranches and clientBranchSyncs) added to src/db/schema.ts
  • SQL migration 0007_client_branches.sql with foreign keys and indexes
  • Updated migration journal
  • Exported ClientBranch and ClientBranchSync TypeScript types

These tables are the foundation for the white-label client branch management feature, enabling the Branch Sync Agent and the /dashboard/branches UI.