Update changelog

And it would be nice to have a common approach for Level.

I see the changelog as an upgrade guide for humans. GitHub and git already provide the information in detail; summarizing that is the gap to fill. A commit list in the changelog is redundant, unless you’re working offline. Still, online or offline, it often contains too much noise to answer the question “what changed for me”?

One thing the commit list does provide is authorship, or maybe attribution is a better word. If people care about that (and it being available offline), we can opt to have both an upgrade guide and commit list.

I suggest:

• No commit list (but keep old releases as-is)
• Describe breaking changes, with code examples where needed
• For headers, use <version> YYYY-MM-DD for parsability
• Include changelog in npm package (already true, here at least)
• On release, copy section to GitHub release

WDYT @ralphtheninja?

[vweevers]

It’s almost like the Keep a Changelog convention. Might as well go all the way. So not “5.0.0 - unreleased” but simply “Unreleased”.

[vweevers]

We can (strive to) update the changelog whenever we make breaking changes or add features. Then on release, we merely have to replace “unreleased” with the date.