When you maintain a plugin for a big project, every new release of that project can break your code. For my two @homeassistant integrations, that’s every month.
The catch is that GitHub can’t start a workflow when someone else publishes a release. So you do what everybody does: a cron that checks every six hours. And GitHub’s own docs say those scheduled runs can be delayed, or even dropped under heavy load.
So I flipped it around with Angelia. You declare what you want to watch (PyPI, npm, crates.io, GitHub releases…), and it tells your CI when a new version is out.
A real example from Monday evening: Home Assistant 2026.11.2 was detected 3 seconds after it was published, and tested in my integration’s CI an hour later. I picked that hour myself, to give the package time to land on PyPI.
I also re-ran the benchmarks on my laptop for the post: 10,000 watches fit in a container with 1 vCPU and 256 MB.
Everything is in the post, with the config, the admin UI and what’s under the hood:
https://blog.mornati.net/angelia-stop-polling-for-releases-let-them-push-to-your-ci/
The project is open source: https://github.com/angelia-dev/angelia
#HomeAssistant #GitHubActions #OpenSource #DevOps #SelfHosted