coding · GPT-4o · free
Turn this git log into a user facing CHANGELOG entry. Range: [v1.2.0..HEAD OR PASTED COMMITS] Git log: Audience: [END USERS / API CONSUMERS / INTERNAL DEVS] Release version: [X.Y.Z] Release date: [YYYY MM DD] Format as Keep a Changelog: [X.Y.Z] — YYYY MM DD Added — new capabilities, phrased as user facing outcomes not "added Foo class" Changed — behavior that changed; note migration if any Deprecated — with the removal version Removed — with the replacement Fixed — the bug in one line + user impact Security — CVEs / vuln fixes, credit reporters Rules: Drop internal refactors, chores, CI tweaks, dep bumps unless behavior changed Merge duplicate topic commits into one line No commit hashes; link to PRs ( 123) BREAKING label on any breaking change with a migration snippet
#changelog #documentation #release