Two new workflows wire up notifications without standing up a single line of SMTP.
Source repo — push notifications. notify-collaborators.yml comments every push to main on a pinned tracking issue. Subscribers get pinged by GitHub directly. No secrets, no infra, one issue to pin.
Mirror repo — release announcements. release-announce.yml ships into keithceh/Coeus-plugin on every tag and posts each new release as a GitHub Discussion under Announcements. Users opt in once — Watch → Releases, or Subscribe to the category — and GitHub delivers the email. Their address, their unsubscribe button, zero subscriber storage on our side.
Why not a literal email form? GitHub already owns the verified address and the unsubscribe path. Rebuilding that means a subscriber file on a persistent branch, SMTP secrets, bounce handling, GDPR overhead — to land in the same inbox GitHub would have hit for free. Lazy wins.
Plus a tidy-up. Stripped every DUG_Malampaya_Prime_2022 reference from user-facing docs (provenance stays in commit history where it belongs), removed an orphaned duplicate
Full Changelog: keithceh/Coeus@v3.9.1...v3.10.1
Mirror of keithceh/Coeus@v3.10.1. Built and synced by release.yml on every tagged release of the source repo.