CHANGELOG.md validator
Paste your changelog and see where it differs from the Keep a Changelog format. Free, no sign-in, and it runs in your browser.
Paste the whole file. The sample has a few mistakes on purpose.
- ErrorLine 5The date "19/11/2026" should be written YYYY-MM-DD.
- WarningLine 10"Bug Fixes" is not one of the six change types (Added, Changed, Deprecated, Removed, Fixed, Security).
- ErrorLine 13Version 1.0.0 has no date. Add " - YYYY-MM-DD".
- Tip3 of 3 versions have no comparison link. Add lines such as [1.2.0]: https://github.com/you/app/compare/v1.1.0...v1.2.0 at the bottom.
This tool runs in your browser. What you paste is not sent anywhere.
Keep it correct without checking by hand
ReleaseTale writes each entry for you in the Keep a Changelog format, from the commits and pull requests of a release, so the headings, dates and groups are right from the start.
What the validator checks
The checks follow the Keep a Changelog 1.1.0 convention and the numbering of Semantic Versioning. Errors are things that break the format. Warnings are likely mistakes. Tips are suggestions you can ignore.
| Check | What it looks for |
|---|---|
| Version headings | Each release is written as ## [1.2.0] - 2026-11-19, with the version in square brackets and a date. |
| Dates | The date is in ISO form (YYYY-MM-DD) and is a real calendar date. |
| Order | Versions are listed newest first, and none appears twice. |
| Change types | Entries are grouped under Added, Changed, Deprecated, Removed, Fixed or Security. |
| Empty sections | A heading with no entries, or a release with no changes, is flagged. |
| Title and Unreleased | A # Changelog title and an Unreleased section at the top are suggested when missing. |
| Comparison links | Each version should have a link at the bottom that shows the diff, such as [1.2.0]: https://github.com/you/app/compare/v1.1.0...v1.2.0. |
After the format is right
A valid file is not yet a good changelog. Read each entry as a customer would, and see the guide on how to write a changelog. If you are starting from scratch, copy the Keep a Changelog template, or turn a list of commits into an entry with the free changelog generator. To choose the next version number, use the version bump calculator.
Frequently asked questions
What does a CHANGELOG.md validator check?
It checks the conventions of the Keep a Changelog format: a heading with the version and an ISO date for each release, newest first, the six change type headings, no empty sections, and comparison links at the bottom.
Is there an official Keep a Changelog validator?
Keep a Changelog is a convention described on keepachangelog.com, not a standard with an official checker. This tool reports where a file differs from that convention, and some findings are tips rather than rules.
Is my changelog sent to a server?
No. The check runs in your browser, so what you paste never leaves your machine.
Does the file have to follow Keep a Changelog?
No. It is a widely used convention, not a requirement. If your project uses another format on purpose, treat the findings as suggestions.