Changelog / Release Notes
Release notes for our quarterly major release, headlined by a new workflow automation engine and a mobile app rewrite with offline support
No card required
What this brief specifies
This release, by the numbers
A B2B project management platform's Q3 release: two major features, eight improvements, twelve bug fixes, one breaking API change.
One document, two readers
Published as a single changelog for both end-users and the developers building integrations against the API.
The breaking change itself
The /api/v1/tasks endpoint is deprecated for /api/v2/tasks with a new response schema, on a 6-month deprecation window.
What makes this hard
The problem here is that one document has to carry two different priority orders for two different readers, from the same 22 release items: 2 features, 8 improvements, 12 fixes, 1 breaking change. An end-user cares about the new automation engine and the mobile app's offline support, and would tune out at the first mention of a deprecated endpoint. A developer needs that one breaking change, the exact endpoint retired, the new response schema, and the 6-month deprecation window, surfaced clearly enough that it doesn't get lost among 12 bug fixes. A generic release-notes template treats every entry as equally weighted; this one has to make the single item with a real deadline impossible to miss for the audience it matters to, without burying the feature news the other audience came for.
Related use cases
See how Flaibo works for Founder.
Frequently asked questions
Carrying forward the actual release breakdown, the fact that one document serves two different readers, and the specific breaking change and its deadline means the notes an AI assistant helps draft can weight the same items differently for each audience instead of listing them flat. The next release that bundles a real breaking change into a broader feature update gets written with that deadline surfaced instead of buried in the list.