Why our release notes have an ‘oops’ section
A changelog should tell the whole story, including the odd bug that taught us something.
A good release note says what changed. A better one says what surprised us. Our ‘oops’ section includes a button that was too persuasive, a tooltip that quoted the wrong century, and a dark mode toggle that briefly made the footer invisible.
None of these mistakes became features. Each became a test, an explanation, and one more reason to read the preview before declaring victory.