What is missing
A v0.1.4 git tag exists in this repo but the CHANGELOG has no corresponding entry. Running git tag confirms the tag; the CHANGELOG jumps from [0.0.1] to [0.2.0] with no [0.1.4] section.
What to do
Add a ## [0.1.4] section to CHANGELOG.md documenting what changed in that release. If the release was minor or a patch, a brief summary is fine. Follow the existing Keep a Changelog format already used in the file.
Why it matters
The CHANGELOG is the primary human-readable record of what changed between releases. A tagged release with no CHANGELOG entry leaves users and contributors without context for what v0.1.4 contained.
Detected by
quaid-scanner OSS health scan — technical pillar, SemVer & Changelog Consistency check.
What is missing
A
v0.1.4git tag exists in this repo but the CHANGELOG has no corresponding entry. Runninggit tagconfirms the tag; the CHANGELOG jumps from[0.0.1]to[0.2.0]with no[0.1.4]section.What to do
Add a
## [0.1.4]section to CHANGELOG.md documenting what changed in that release. If the release was minor or a patch, a brief summary is fine. Follow the existing Keep a Changelog format already used in the file.Why it matters
The CHANGELOG is the primary human-readable record of what changed between releases. A tagged release with no CHANGELOG entry leaves users and contributors without context for what
v0.1.4contained.Detected by
quaid-scanner OSS health scan — technical pillar, SemVer & Changelog Consistency check.