{"@context": "https://schema.org", "@type": "Dataset", "name": "ChangelogForge release-debt worked example (2026)", "description": "Method data: raw commit input, classified changelog output (Features, Fixes, Breaking Changes) with a reason per item. Synthetic example commits are marked as example data.", "license": "https://creativecommons.org/licenses/by/4.0/", "creator": {"@type": "Organization", "name": "ChangelogForge"}}

← Back to press resources

The release debt: why unclassified commits cost your team trust every single deploy

Published 2026-10-23 · ChangelogForge Research · Method free for editorial use. Credit: "ChangelogForge (changelogforge.app)".

Every push ships changes — almost nobody ships the story. A worked example: from raw commits to a classified changelog (Features, Fixes, Breaking Changes) with verifiable reasons, published to GitHub Releases in minutes.

The gap

Every dev team ships code daily. Almost none ships a changelog anyone reads. The gap is release debt: hundreds of unclassified commits piling up between releases, until "what changed?" becomes a Slack archaeology project the evening before launch. ChangelogForge's worked example shows the payoff: connect a GitHub repository in one click, ship code as usual, and get a classified draft changelog — Features, Fixes and Breaking Changes detected automatically, each with a short reason you can verify — ready to review and publish to GitHub Releases.

Quota and pricing (measured)

1 generation = 1 generated release draft — triggered on your release branch, tag, or on demand, so routine feature-branch commits never burn your monthly quota. Free covers 3 drafts a month on 1 public repo; Pro ($19) covers 50; Team ($49) covers 200 plus the approval gate.

Break-even

At a conservative $80/hour engineering cost, Pro ($19/month, $228/year) breaks even by saving just 2.85 hours per year ($80/h) — only 14.3 minutes per month of manual release-note archaeology (Team $49/mo breaks even at 36.7 minutes/month). Public repos start on the $0 Free plan.

No black box

Every classification ships with a reason, so you always see why an item landed under Features or Fixes. The example changelog is visible right on our homepage — no account needed. Free plan for public repos, no credit card to start. And unlike a CI script, we do not need commit-message religion: real-world commits get classified even when someone forgets feat: or fix:.

Security note

Built for Engineering Security: ChangelogForge uses official GitHub App least-privilege permissions, reads commit metadata and diffs only to classify your release draft, and never stores, redistributes, or trains AI models on your proprietary source code. No credit card to start. Operated by Universal Global Services Ltd (London, Companies House No 17423506).

Method

Comparison: why not Release Please or semantic-release?

AspectConventional-commit CI scriptsChangelogForge
Commit-message disciplineRequires feat:/fix: prefixes from every developerClassifies real-world commit messages
Reason per itemDerived from the prefix onlyShort verifiable reason stored per item
Review before publishManual (script pushes on merge)Draft first; Team plan adds approval workflow
SetupCI YAML per repositoryOne-click GitHub App install

Material

Worked example changelog (0-click homepage demo: raw git log vs classified Release + sample PDF) + method page: https://changelogforge.app/press/github-release-automation-2026/ — Credit: "ChangelogForge (changelogforge.app)".

About ChangelogForge

ChangelogForge (changelogforge.app, a product of Universal Global Services Ltd) turns commits into polished changelogs and release notes: connect GitHub in one click, review auto-classified drafts, publish to GitHub Releases. Start free. Contact: [email protected].