gezel Gezel Handboek

Changelog Cut

Cut a new versioned section into a Keep a Changelog / CHANGELOG.md style file for a release — moving entries out of the Unreleased section into a dated, semver-stamped version block under the standard Added / Changed / Deprecated / Removed / Fixed / Security headings, with a fresh empty Unreleased section left behind. A developer gathers the unreleased entries and reconciles them against actual merged changes before a copywriter normalizes them into terse, consistent changelog lines and stamps the version block. Use this whenever you 'cut a release', 'update the changelog', or roll the Unreleased section into a tagged version while keeping the file append-only and machine-comparable.

How it runs

#StepWho runs itWhat happens
1Gather unreleased entriesDeveloperreconcile the Unreleased section against actual merged changes
2Cut the version blockCopywriternormalize entries and stamp the dated version section
3EvaluateReviewerGrade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.
4FinishDeveloperAll acceptance criteria met. Stamp a short summary and report DONE.

Say something like "cut a changelog" or "update CHANGELOG.md" or "roll unreleased into a version" or "stamp the changelog for v1.4" or "keep a changelog release" in chat to start it.

Watch this article as a slideshow