Loading page
About this tool
Split a release into features, fixes and breaking changes, set a deprecation date and build the announcement prompt.
A release notes prompt builder sorts a flat list of shipped changes into breaking changes, security fixes, deprecations, features, improvements, bug fixes and known issues, then writes an announcement prompt in that order — because a reader has to meet what breaks them before what delights them. It sizes the note against the channel it will be published on, from a 60-word in-app notice to a 900-word blog post, and calculates the exact date a deprecation stops working from your release date and notice period.
Open Release Notes Prompt Builder on AltFTool — it loads instantly in your browser.
Paste your code or data sample into the workspace.
Pick the format, conversion, or analysis you need.
Copy the polished result straight back into your project.
Breaking changes and security fixes are placed above new features automatically, not left to whoever writes the draft.
Each channel carries its own word ceiling, so the in-app note does not arrive as a wall of text.
The removal date is calculated from the release date and notice period, including month and year rollovers.
A changelog is the complete, chronological record of every change, written for people who want the detail. Release notes are the announcement for one release, written for people who just want to know what changed for them. The changelog is generated from commits; the release notes are edited by a human from that list.
Long enough for your slowest customer to migrate — commonly 90 to 180 days for a public API, and longer where enterprise contracts specify a notice period. The number matters less than announcing a specific calendar date up front and not moving it. Check your own terms of service before committing.
Anything that requires the reader to act: breaking changes, security fixes and deprecation deadlines. New features come after. Readers skim, and a migration step buried under three feature paragraphs is a support ticket waiting to happen.
Match the channel. An in-app notice works at around 60 words, a customer email at 250, a blog or docs page up to about 900. At roughly 238 words per minute of adult silent reading, 900 words is already a four-minute commitment — link out rather than keep going.