Logan Johnson 3f81a0f573 Stop requiring the 0032 roster trigger at startup ...

The relay refused to boot unless migration 0032's roster-fence trigger
was present and behaved, and it rechecked the trigger catalog after
migrating. Since #8316 every roster writer runs the same check in Rust
(validate_channel_roster_snapshot), so the trigger is only a backstop.

Remove the startup probe and the post-migration catalog check so a
later migration can drop the trigger. Under the docs/database.md
retirement sequence this release must be fully deployed before that
drop ships.

Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Logan Johnson <loganj@squareup.com>

2026-10-26 16:03:11 -04:00

..

charts

Stop requiring the 0032 roster trigger at startup

2026-10-26 16:03:11 -04:00

compose

Use Silo for bundled object storage (#8023)

2026-10-07 18:02:27 -04:00

local

Relay mesh: cross-pod tunnel + huddle transport (buzz-relay-mesh) (#1670)

2026-07-14 16:56:48 -04:00