Lint report — redis

C

68/100 — Needs work. 100 entries checked against 9 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. 100 entries parsed ("## heading" style) — capped at 100. Guide: The Keep a Changelog format, explained
WARN
Entries have dates. 3 of 100 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
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. 5 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
WARN
Titles are unique. 1 title repeats (e.g. “Fixes for issues in previous releases of Redis 7.2” ×3). Repeated titles are ambiguous to link to. Guide: How to write a changelog (with examples)

Specific entries to fix

  • Fixes for issues in previous releases of Redis 7.2 — No date in the release heading.
  • Fixes for issues in previous releases of Redis 7.2 — No date in the release heading.
  • Fixes for issues in previous releases of Redis 7.2 — No date in the release heading.
  • v8.4.2 — Security fix with no affected-versions or action guidance.
  • v8.2.5 — Security fix with no affected-versions or action guidance.
  • v8.0.6 — Security fix with no affected-versions or action guidance.

Put the grade in your README changelog grade C 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%2Fredis%2Fredis)](https://wakelog.wakelog.workers.dev/lint?url=https%3A%2F%2Fgithub.com%2Fredis%2Fredis)

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.