Member notification tables, and an event's origin columns

FeatureInitializerService
Shipped
August 14, 2026 at 6:01 AM UTC
Author
Kamo
Commit
57290f5

Two halves of one feature. A callback scheduled on a lead is mirrored onto the scheduling member's calendar, and the point of the mirror is to get back to the lead — so calendar_events carries source_type, source_id and deep_link, and the notification raised from it carries the same three onward. Order 0: CalendarEvent maps the three new columns from the moment this build starts, so every runner that loads an event emits them in its SELECT and ddl-auto cannot have added them yet. Ordered late it would never execute. Applied and verified against Yugabyte 2026-08-13.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing