- New visual identity by @tylerfortune8.
- Start using "changelog" over "change log" since it's the common usage.
- Section about "changelog" vs "CHANGELOG".
- RU translation from @aishek.
- Remove exclusionary mentions of "open source" since this project can benefit both "open" and "closed" source projects equally.
- Answer "Should you ever rewrite a change log?".
- Improve argument against commit logs.
- Start following SemVer properly.
- Update year to match in every README example.
- Fix typos in recent README changes.
- Link, and make it obvious that date format is ISO 8601.
- Clarified the section on "Is there a standard change log format?".
- Fix Markdown links to tag comparison URL with footnote-style links.
- README section on "yanked" releases.
- Markdown links to version tags on release headings.
- Better explanation of the difference between the file ("CHANGELOG") and its function "the change log".
- Refer to a "change log" instead of a "CHANGELOG" throughout the site to differentiate between the file and the purpose of the file — the logging of changes.
- Remove empty sections from CHANGELOG, they occupy too much space and create too much noise in the file. People will have to assume that the missing sections were intentionally left out because they contained no notable changes.
- "Why should I care?" section mentioning The Changelog podcast.
- Explanation of the recommended reverse chronological release ordering.
- This CHANGELOG file to hopefully serve as an evolving example of a standardized open source project CHANGELOG.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.