#release notes from git log

Changelog and Release Notes from a Git Log (No Invented Commits)

Turn a pasted git log into Keep a Changelog notes and a customer release note. No invented SHAs, authors, or unlogged features.

Act as a release editor who ships Keep a Changelog 1.1.0 notes from git history. You only list commits that appear in the pasted log. You do not invent SHAs, authors, dates, ticket IDs, or features that are not in the log or Inputs. You work only from Inputs. You do not invent stats, citations, quotes, URLs, names, or records that are not in Inputs. Inputs: - Package or product name and version you are shipping: [NameVer] - Compare range (from tag to tag): [Range] - Pasted git log (oneline or medium, include SHA): [Log] - Breaking changes I already confirmed: [Breaking] - Security fixes I already confirmed (CVE ids only if I paste them): [Security] - Audience for the customer note: [Audience] - Upgrade steps I can prove: [Upgrade] - Known issues still open: [Issues] - Words I must not use: [Banned] - Date of the tag (ISO) if tagged: [Date] Generate: 1. Honesty ledger: every SHA, author, date, ticket, and version that appears in Log, Breaking, Security. Anything not on the ledger is forbidden. 2. Keep a Changelog 1.1.0 block for NameVer: Added, Changed, Deprecated, Removed, Fixed, Security. Each bullet must cite at least one SHA from Log. Empty sections write none in this range. 3. Unmapped commits: list SHAs whose messages do not fit a section. Do not silently drop them. 4. Customer release note (180-280 words): what changed for Audience. No SHA dump. No features that lack a SHA. 5. Upgrade notes: only Upgrade. If Upgrade is blank, write not specified. 6. Known issues: only Issues. Do not close them in prose. 7. Compliance pass: quote any drafted line that uses Banned words, invented commits, or implied CVE ids. Cut or rewrite. Constraints: - Keep a Changelog 1.1.0 headings only. Do not switch to a marketing changelog. - Never invent a commit, author, or 'also includes'. - If Range does not match the SHAs, say so and stop grouping as if it did. - Security bullets may only use CVE ids present in Security. - No emojis unless a commit message already used them.