Release notes that write themselves from commits
Reads conventional commits, groups them by scope, links every pull request and opens a draft.

README.md · CASE STUDY
Reads conventional commits, groups them by scope, links every pull request and opens a draft.
Reads conventional commits, groups them by scope, links every pull request and opens a draft.
Release notes were the last chore of every release, so they were late or missing. The information was already in the commit history.
How it works
wren parses conventional commits, puts breaking changes first, groups the rest by scope and links each line to its pull request. It never publishes. It opens a draft for a person to approve.
Adoption
It runs as a CI action in 320 public repositories. 98% of drafts ship without edits, which is the number I watch most.
More projects.
Every project opens the same way: problem, fix, numbers.
Notes from the work.
Short write-ups of things that broke and how they got fixed. Plain language, real numbers.