Lint report — sample changelog

B

84/100 — Good. 3 entries checked against 8 practices from the Wakelog guides.

Nothing was saved. Lint another · how the big projects score · preview it as a hosted page

Checks

PASS
Recognizable release entries. 3 entries parsed ("## heading" style). Guide: The Keep a Changelog format, explained
WARN
Entries have dates. 1 of 3 entries have no date in their heading. Guide: The Keep a Changelog format, explained
PASS
Newest release first. Entries run newest to oldest. Guide: Changelog page design: layout and UI patterns that work
PASS
Titles say what changed. No “bug fixes and improvements”-style filler titles found. Guide: How to write a changelog (with examples)
PASS
Entries have content. No empty version-only entries. Guide: Release notes templates: copy-paste formats for every kind of change
PASS
Written for readers, not a commit dump. Entries read like notes for humans, not raw git log. Guide: Generate a changelog from git commits (without publishing garbage)
WARN
Bullets say what changed. 2 of 4 bullets carry no information (“wip”, “fix stuff”, “merged PR”). Say what changed and why a reader cares — or cut the line. Guide: How to write a changelog (with examples)
NOTE
Breaking changes stand out. No breaking changes mentioned. When one ships, flag it loudly — “Breaking:” first, migration steps included. Guide: How to announce breaking changes (without losing users)

Specific entries to fix

  • v3.2.0 — No date in the release heading.
  • v3.2.0 — “misc fixes” says nothing — name the change or drop the bullet.
  • v3.0.0 — “merged PR” says nothing — name the change or drop the bullet.

Want a changelog that passes by construction? Host it on Wakelog — free, 30-second signup, no email. Import this exact file in one paste (dates preserved), get a public page with permalinks, RSS, a widget and an API. Not convinced? See how it would look first.