**The commit messages are the changelog** (owner, 1 November 2026: every commit between two releases, the whole
message, in every place a release is shown). The action takes the commits since the previous tag of the same kind
(`prefix`: `v`, `app-v`, `server-v`; the previous one is the highest lower version among those tags), leaves out merges
and the `Co-Authored-By`, `Signed-off-by` and Claude attribution lines, and writes, into `output`:
| File | For |
|---|---|
| `notes.md` | "What's new in <name> <version>": each commit's subject as a heading, its body below; the Releases tab, a page |
| `notes.txt` | the same as plain text: Velopack's `--releaseNotes`, an update dialog, F-Droid |
| `CHANGELOG.md` | the last `history` releases, newest first |
| `changelog.yml` | the same releases for nfpm's `changelog:` (chglog), so the deb carries `changelog.Debian.gz` and the rpm its `%changelog`; bodies become one line per paragraph |
| `notes.json` | everything above as data |
| `store/en-US.txt` | the subjects, cut to 500 characters, for the `notes` folder of `play` and `apple` |
With `release: 'true'` it also writes the notes onto this tag's release on the Releases tab: it creates the release
when there is none, and otherwise replaces only what sits between `<!-- changelog -->` and `<!-- /changelog -->`
(adding that block at the end the first time), so a release text written by the project itself stays. Give the job
packager:Scuola di lingua Cinese di Varese <info@scuolacinese.org>
output:release-notes
release:'true'
- run:echo "the notes are in ${{ steps.notes.outputs.dir }}, the previous release was ${{ steps.notes.outputs.previous }}"
```
| Input | | |
|---|---|---|
| `prefix` | `v` | the tags of this kind of release |
| `tag` | the tag that started the run | the release being made; empty on a branch, which writes everything since the newest tag as `unreleased` |
| `name` | the repository's name | the product's name in headings |
| `strip` | | a regular expression removed from the start of each subject (me-web? removes its `“me-web?” 0.15.4: `) |
| `packager` | `Arasaka di Hvozdikov Yevheniy <packages@arasaka.software>` | `Name <address>` for the deb and rpm changelogs: the package's own maintainer |
| `history` | `20` | how many releases `CHANGELOG.md` and the package changelog carry |
| `output` | `release-notes` | the folder |
| `release` | `false` | `true` writes the notes onto the Releases tab |
| `token` | the job token | only with `release` |
A shallow checkout is fetched in full, with its tags, before anything is read. A first release lists its newest 100
commits. The same file reads the history from Gitea's API instead of a checkout (`--gitea URL --repository
owner/name`, token in `READ_TOKEN`); that is how `thepra/packages.arasaka.software` writes the notes for every app it
publishes, so the two can never tell a release differently.