A composite GitHub Action (pure shell) that generates abbreviated release notes from Conventional Commits — the user-facing changes since the last release, for deciding whether to upgrade.
The notes contain the repository title, the release version, and the changes since the last release, collated as:
- BREAKING CHANGES (bold, first)
- Features
- Fixes
Non-user-facing commits (docs, chore, refactor, ci, …) are excluded. No
Node/Docker — just bash, git, sed, grep.
- uses: lite-actions/git-checkout@v1with:
fetch-depth: 0fetch-tags: true # "since last release" is resolved from vX.Y.Z tags
- uses: lite-actions/release-notes@v1with:
title: "My Project"# optional; defaults to the repo name
- run: cat RELEASE_NOTES.md| Input | Default | Description |
|---|---|---|
title | repository name | Heading title for the notes. |
from | latest vX.Y.Z tag | Base ref/commit for the range. |
to | HEAD | Head ref/commit for the range. |
version | computed | Explicit version; otherwise bumped from the commit types. |
output-file | RELEASE_NOTES.md | File to write. |
| Output | Description |
|---|---|
version | The release version used in the notes. |
file | The path the notes were written to. |
changed | true if there were any BREAKING / feat / fix commits. |
When version is not given, it is computed from the commits since the last
vX.Y.Z tag: a BREAKING change → major, a feat → minor, otherwise patch.
# My Project## v2.0.0**⚠ BREAKING CHANGES**- node 18 is now required
### Features- add sso login
### Fixes- handle empty payload