Lint report — prometheus

B

76/100 — Good. 100 entries checked against 9 practices from the Wakelog guides.

Graded from: GitHub Releases API (100 releases). Repo-URL grades reflect whichever releases are visible right now and can vary between runs — lint the raw CHANGELOG.md URL for a stable grade.

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

Checks

PASS
Recognizable release entries. 100 entries parsed ("## heading" style) — capped at 100. Guide: The Keep a Changelog format, explained
PASS
Every entry has a date. All entries carry a date — readers can tell when things shipped. Guide: The Keep a Changelog format, explained
WARN
Newest release first. 3 entries are out of date order. 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)
PASS
Bullets say what changed. No zero-information bullets (“wip”, “fix stuff”) found. Guide: How to write a changelog (with examples)
WARN
Breaking changes stand out. Breaking changes are mentioned mid-text but not flagged — lead with “Breaking:” or a heading so skimmers can’t miss them. Guide: How to announce breaking changes (without losing users)
WARN
Security fixes are actionable. 2 security-related entries with no affected versions or upgrade guidance. Say who’s affected and what to do — vagueness reads as cover-up. Guide: Security advisories vs changelog: how to publish a security fix

Specific entries to fix

  • v2.45.6 / - 2024-06-21 — Security fix with no affected-versions or action guidance.
  • v2.45.3 / - 2024-01-24 — Security fix with no affected-versions or action guidance.

Put the grade in your README changelog grade B badge

A live badge that re-grades this URL daily and links back to the full report:

[![changelog grade](https://wakelog.wakelog.workers.dev/lint/badge.svg?url=https%3A%2F%2Fgithub.com%2Fprometheus%2Fprometheus)](https://wakelog.wakelog.workers.dev/lint?url=https%3A%2F%2Fgithub.com%2Fprometheus%2Fprometheus)

Different label? Tune it in the badge playground.

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.