Skip to content

CHANGELOG has two ## [Unreleased] sections — release tooling will silently drop one #3395

Description

@houko

Location

  • CHANGELOG.md lines 431 and 626

Gap
Two distinct ## [Unreleased] headings exist in the file (line 431 between 2026.4.19 and 2026.4.18; line 626 between earlier versions). The second is buried mid-history and will be invisible to anyone scrolling the latest changes; release tooling that greps for the first [Unreleased] block will silently drop everything in the second.

The bottom of the file also still has [0.1.0]: https://... reference link with no other link defs, suggesting reference-style links were abandoned.

Fix
Resolve both [Unreleased] sections — either fold them into the next dated release or rename the older one to its actual version. Add a CI check (grep -c "^## \[Unreleased\]" must equal 1) so this can't recur.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/ciCI/CD and build toolingarea/docsDocumentation and guidesdifficulty/easy1-3 hours, minimal context neededdocumentationImprovements or additions to documentationhas-prA pull request has been linked to this issueneeds-triageAuto-applied when the issue title/body matched no area label — needs maintainer reviewseverity/highSignificant functional, security, or performance impact

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions