Skip to content

fix(changelog): merge the duplicated Unreleased "Changed" section - #134

Merged
sbaerlocher merged 1 commit into
mainfrom
fix/changelog-md024
Aug 10, 2026
Merged

fix(changelog): merge the duplicated Unreleased "Changed" section#134
sbaerlocher merged 1 commit into
mainfrom
fix/changelog-md024

Conversation

@sbaerlocher

Copy link
Copy Markdown
Member

Summary

Test plan

  • npx --yes -- markdownlint-cli2 $(git ls-files '*.md')0 issues in 0 files (was 1 issue in 1 file)
  • npx --yes -- prettier --check CHANGELOG.md — passes
  • lefthook pre-commit ran clean on the commit itself
  • CI green

`[Unreleased]` gained a second `### Changed` heading, so `markdownlint`
reported MD024 on a pristine tree and the lefthook `pre-commit` hook blocked
every commit staging `CHANGELOG.md` again. The `ansible_facts` entry moves
into the existing section; no wording changed.

Signed-off-by: Simon Bärlocher <s.baerlocher@sbaerlocher.ch>

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found.

The change correctly resolves the MD024 duplicate-heading violation by removing the second ### Changed heading in [Unreleased] and folding the ansible_facts entry into the existing ### Changed section. Verified:

  • The moved entry is byte-identical (indentation and wording unchanged), so no documentation regression.
  • After the move, every version section ([Unreleased], [1.2.0], [1.1.0], [1.0.3], etc.) has exactly one of each sibling ### heading, satisfying MD024.siblings_only.
  • Placement is sensible: the non-breaking entry sits after the BREAKING entries and before the Renovate entry, with clean surrounding blank lines.

Documentation-only, no functional impact.

@sbaerlocher
sbaerlocher enabled auto-merge (squash) August 10, 2026 22:28
@sbaerlocher
sbaerlocher merged commit f4af06f into main Aug 10, 2026
29 checks passed
@sbaerlocher
sbaerlocher deleted the fix/changelog-md024 branch August 10, 2026 22:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant