CHANGELOG.md Validator
Questions
That the file follows the Keep a Changelog convention: a title, one "## [version] - date" heading per release, dates written as YYYY-MM-DD and real, releases newest first, no version twice, no empty releases, changes grouped under Added, Changed, Deprecated, Removed, Fixed or Security, and link references for versions written as links.
An error is something the convention requires and a parser will trip on, such as a release with no date. A warning is a departure that still reads, such as a change type the convention does not name. A note is advice the convention gives that a file may reasonably ignore, such as using semantic versions.
No. It is read, checked and discarded within the request. Nothing is saved, logged or cached, and no account is needed.
No. It is a convention, not a standard, and plenty of good changelogs depart from it. It is worth following because tools can read it: release automation, and importers like the one in Relnotely, which turns each release heading into a dated entry.
Guides that go with this
The other free tools
Your changelog, on your own domain
One plan at $19 a month: your domain, the widget, subscriber emails, no watermark and no trackers on your readers. Writing is free — a card starts the 7-day trial when you publish.