For projects there's a particular simple release [autoupdate](wiki/Autoupdate) scheme. Just provide at least one link to your github-repo (as primary Autoupdate URL, Homepage, Download or in Other URLs).

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

  *  Version number prefixes like `"v"` and `projname-` prefixes will be stripped from tags.
  * Only the `1.2.3*` style version number will be retained from tags.
  * Release titles are generally ignored.

Three different methods are tried to extract release news then:

  1. is the preferred way to retrieve a changelog. The first bulleted task-list will be presumed to be individual change notes.

    <img width=600 height=300>

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

  2. Alternatively a `*` bulleted list from `tags.atom` `<content>` will be used.

    So you can have your commit message for a tag contain a changelog-style summary.


  3. As fallback 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.

Some basic filtering (removing "merged pull request xyz" entries) is applied.


State: *functional, testing*