Stop Copy-Pasting Commits: Generating Release Notes Entirely in Your Browser
I spent forty-five minutes last Tuesday staring at a git log, manually filtering out "fix typo" and "update deps" to write a changelog for a minor patch. It’s a task we all hate: it’s low-signal, high-friction, and it eats into the time we actually want to spend building features. We tend to accept this friction as the tax of shipping software, but it doesn’t have to be. The core problem isn’t…
In a recent experience, the author spent forty-five minutes manually filtering through a git log to write a changelog for a minor software patch. Manually crafting release notes is a task many developers find tedious, time-consuming, and adds unnecessary friction to the development process. While accepting this friction may seem inevitable in software shipping, the author believed there must be a better way.
The core issue, according to the author, is not just the tediousness of writing release notes, but the complexity most tools introduce to the process. Developers often have to use command-line scripts, pay for cloud API calls, or rely on SaaS platforms to generate release notes. This approach raises privacy concerns for teams handling sensitive codebases, as sending raw commit data to third-party servers is a no-go for many.
To address these pain points, the author developed ChangelogPro, a tool that generates release notes entirely in the user's browser. The key innovation lies in processing the commit messages locally on the user's machine, without any server-side involvement. This ensures that the commit messages never leave the user's browser, offering a privacy-first workflow.
The tool leverages a private on-device AI model that runs via WebGPU. Unlike most browser-based AI tools that rely on sending data to remote APIs, ChangelogPro runs inference locally, eliminating latency, cost, and privacy concerns. This approach also makes the tool offline-first, allowing users to generate release notes even in areas with spotty internet connectivity.
To use ChangelogPro, users paste their git log output or a raw markdown list of changes into the tool, and click "Generate." The on-device model synthesizes the commit messages into a polished release notes document, categorizing the changes into new features, improvements, fixes, and documentation updates. The model understands the nuances of technical commit messages, distinguishing between user-facing features and internal housekeeping tasks.
ChangelogPro is a paid tool, but it comes with a 7-day trial, allowing users to test the workflow with their actual project history before committing. The author believes that automating the drafting phase of release notes enables developers to focus on crafting the narrative of the release rather than extracting data from commit messages.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
