v0.3.0-rc.19

The nineteenth pre-release of 0.3.0, published as a GitHub pre-release and not marked latest. See CHANGELOG.md, [0.3.0-rc.19].

What an operator must do

• A deployment with a beszel app: apply it so the hub picks up the smtp block and its sender. validate now refuses a from_address that is not a bare email address (beszel-smtp-sender), and warns on starttls with no username (beszel-starttls-not-enforced). Beszel then emails the addresses each operator adds in its settings; it seeds no alert rules.
• Beszel alerts in Matrix are opt-in. To add them:
  • Declare an app with blueprint: ops-notifier and a hostname, pinned to the site the synapse app runs on. validate refuses it anywhere else (colocated-app-elsewhere), and without a homeserver or a beszel app (ops-notifier-without-homeserver, ops-notifier-without-hub).
  • Apply. The synapse stack is applied again with an admin client for the notifier, and the hub with a superuser of the notifier's own.
  • Its image track comes from the core catalog v0.10.0 (paisans-blueprints), which earlier toolkits skip, staying on v0.9.0.
• Catalog authors: blueprint format paisans.blueprint/v4 adds colocate: true on a consume. Toolkits before this release refuse a v4 blueprint, so a catalog release using it is skipped by them.
• Nothing to do for the rest.

Everything in [0.3.0-rc.1] to [0.3.0-rc.18] still applies.

🤖 Generated with Claude Code

What's Changed

• Develop is 0.3.0-dev by @josephquigley in #578
• feat(beszel): send alert email through the deployment's smtp block by @josephquigley in #579
• feat(blueprints): let a consume be colocated with its provider by @josephquigley in #581
• docs: specify ops-notifier, Beszel alerts in Matrix by @josephquigley in #582
• feat: add the ops-notifier blueprint, Beszel alerts in Matrix by @josephquigley in #583
• docs: design for welcoming new members by @josephquigley in #584
• Release 0.3.0-rc.19 by @josephquigley in #586

Full Changelog: v0.3.0-rc.18...v0.3.0-rc.19