When a GitHub release is published, generates clean, categorized release notes from the merged pull requests since the previous release and writes them into the release body. Skips drafts and releases that already have substantial human-written notes (it won't clobber them).
- Identifier
release-notes- Version
- 1.0.0
- Steps
- 2
- Triggers
- 1
- release
- notes
- documentation
- automated
When it runs
release.published- Settle delay
- 10s after the event
Only when all hold
- release.draft not equals true
- actor.username not contains [bot]
The pipeline
The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.
- 01Release Published
triggerThe event that starts the run.
- 02Generate & Write Release Notes
agent.runOne agent works the task with its toolkit.
The agent
Release Notes Writer
- Base type
- Tech Writer
- Temperature
- 0.3
- Max iterations
- 15
- Tools
- 3
Git provider · 2
generate_release_notesGenerate Release Notes · readupdate_releaseUpdate Release · write
Status · 1
update_statusUpdate Status · write
Related playbooks
Changelog Generator
Classifies each merge to the default branch and adds a changelog entry.
Release PR Description
Writes user-facing, categorized release notes into the body of every release/* pull request.
Auto Docs Update on Merge
Watches merged PRs and opens follow-up PRs when code changes affect existing docs.