Release Thread

1. Create an issue comment that starts with /release on the first line.
2. Second (non-empty) line will be used as a release title/name.
3. All following lines will be interpreted as a release description/body.
4. Description (even if empty) will always be appended with a comparison link to the previous release, unless there is no previous release.

**How to**
Add a comment with one of the following to push a release:
- **_For a standard release:_**
- given latest release v1.0,0 will create a release v1.0.1 (increases patch)
- /release
- PUT THE TITLE HERE (This is title of v1.0.1)

- **_For a New Book / Big FAQ initial releases (game-wide updates):_**
- given latest release v1.0,0 will create a release v1.1.0 (increases minor, resets patch)
- /release bump=minor
- PUT THE TITLE HERE (This is title of v1.1.0)

[Above text copied from Horus Heresy Maintainers; many thanks for the training and aid they've provided over the years]

No files, tests, or entry points are named. Start by reviewing the repository structure and existing release automation, then compare it with the /release comment format described here; done means the documented standard and minor-release commands produce the specified title, version bump, description, and comparison link.

Written by the indexing model from the issue text.