[boeboe]

DS-REL reports a newest ## vX.Y.Z section that is still untagged a day after it was committed. The date came from the oldest commit that ever changed the heading's count (git log -S, last line). For a heading that was added, folded into another section and later written again, that oldest commit is the first addition. go-iec61850's ## v1.21.0 was added in #67 and folded away in #72 on 2026-11-11, so the pull request that writes it again for the real v1.21.0 is reported as "release notes since 2026-11-11" before it is merged.

Added now takes the newest commit that changed the heading's count, and only when the file still holds the heading at that commit:

• A heading written again dates from that commit.
• A heading that is back in the work tree but not committed has no date, as a heading never committed has none. A local make check on an uncommitted section behaves as before.

Tests

• TestAdded (internal/gitinfo) builds a nested-module history: added, folded, back uncommitted, added again, reworded. On v0.3.1 it fails at "back but not committed" (it returned the first addition).
• TestGitChecks is unchanged and passes.
• make check passes, coverage 89.4%.
• The fixed build reports nothing on go-iec61850's feat/policy-1.6-minor tree (library, sclparse, sclgen), where v0.3.1 reports the finding.

Patch release v0.3.2. Consumers move when they bump docsync-version.

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!