New visual identity by @tylerfortune8.

Version navigation.

Links to latest released version in previous versions.

"Why keep a changelog?" section.

"Who needs a changelog?" section.

"How do I make a changelog?" section.

"Frequently Asked Questions" section.

New "Guiding Principles" sub-section to "How do I make a changelog?".

Simplified and Traditional Chinese translations from @tianshuo.

German translation from @mpbzh & @Art4.

Italian translation from @azkidenz.

Swedish translation from @magol.

Turkish translation from @karalamalar.

French translation from @zapashcanon.

Brazilian Portugese translation from @Webysther.

Polish translation from @amielucha & @m-aciek.

Russian translation from @aishek.

Czech translation from @h4vry.

Slovak translation from @jkostolansky.

Korean translation from @pierceh89.

Croatian translation from @porx.

Persian translation from @Hameds.

Ukrainian translation from @osadchyi-s.

Section about "changelog" vs "CHANGELOG".

Start using "changelog" over "change log" since it's the common usage.

Start versioning based on the current English version at 0.3.0 to help translation authors keep things up-to-date.

Rewrite "What makes unicorns cry?" section.

Rewrite "Ignoring Deprecations" sub-section to clarify the ideal scenario.

Improve "Commit log diffs" sub-section to further argument against them.

Merge "Why can’t people just use a git log diff?" with "Commit log diffs"

Fix typos in Simplified Chinese and Traditional Chinese translations.

Fix typos in Brazilian Portuguese translation.

Fix typos in Turkish translation.

Fix typos in Czech translation.

Fix typos in Swedish translation.

Improve phrasing in French translation.

Fix phrasing and spelling in German translation.

RU translation from @aishek.

pt-BR translation from @tallesl.

es-ES translation from @ZeliosAriex.

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.

Reluctantly stop making fun of Brits only, since most of the world writes dates in a strange way.

Fix typos in recent README changes.

Update outdated unreleased diff link.

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.

Unreleased section to gather unreleased changes and encourage note keeping prior to releases.

Better explanation of the difference between the file ("CHANGELOG") and its function "the change log".

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.

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.

"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.

CNAME file to enable GitHub Pages custom domain

README now contains answers to common questions about CHANGELOGs

Good examples and basic guidelines, including proper date formatting.

Counter-examples: "What makes unicorns cry?"