Product changes, in chronological order. Focus on impact and action.
Added: new features and new capabilities.
Improved: performance, UX, quality, limits, coverage.
Fixed: bugs and regressions.
Breaking change (if any): what broke + how to migrate.
A good release note answers: what changed, for whom, what impact, what to do now.
{% update date="YYYY-MM-DD" %} # YYYY-MM-DD — Short release title ## Added - _(what was added + for whom)_ ## Improved - _(what improved + measurable impact, if any)_ ## Fixed - _(what was fixed + context of the problem)_ ## Breaking changes (if any) - _(what changed)_ - **How to migrate:** _(short steps)_ - **Who is affected:** _(e.g.: production projects / only new ones)_ {% endupdate %}
(fill in)
If there is a change that affects production, put it at the top and include “How to migrate”.
Last updated 2 days ago
Was this helpful?
