For GitHub-hosted projects there's a particular simple release autoupdate scheme. Just provide at least one link to your github-repo as primary Autoupdate URL, Homepage, Download or Other URL.

• A projects tags.atom will be polled daily for version number updates.

• http://github.com/$user/$project/releases is the preferred way to retrieve a changelog. The first bulleted task-list will be presumed to be individual change notes.

  

  This is what GitHub itself recommends for publishing releases. Albeit only major projects are utilizing it, e.g. /atom/atom.

• As fallback $repo/compare/0.9.9...1.0.0 will be used for condensing commit logs into a summary.

  This is obviously not often a user-friendly changelog. Therefore it's rate limited. Which might incur delayed bugfix release announcements.

  For projects where this fallback repeatedly only generates developer/commit changelogs, it'll probably be moderated and disabled.

Version number prefixes like "v" will generally be stripped from tags. Some basic filter (removing "merged pull request xyz" entries) is generally applied.

State: functional, testing