The release-content engine starts with GitHub: tagged releases land in an internal pipeline where we can summarize changes, draft a changelog blurb, and tee up a longer blog post without copy-pasting commit messages by hand.
AI assists with the first pass, but humans approve before anything ships to the marketing site or email. That keeps tone accurate and prevents a broken screenshot or misread feature from becoming the official story.
Public GitHub Releases remain the source of truth for version markers. Until a release is published on GitHub, the public “signal” feed may be empty—that is expected for repositories that have not cut a formal release yet.