v1.6.9
v1.6.9 — CI patch (release body fix)
This is a maintenance release. No code changes; no user-visible behaviour change. Stay on v1.6.8 if you have no reason to update.
What changed
The release workflow now explicitly fetches the annotated tag object after checkout. The default actions/checkout@v4 fetch is --no-tags +<commit-sha>:refs/tags/<name> — the local ref is created pointing at the commit and the annotated tag OBJECT is never downloaded. git for-each-ref %(contents) on that lightweight ref returns the commit message, not the tag annotation.
The first attempt at this fix used fetch-tags: true on the checkout step, but that caused a refspec conflict (Cannot fetch both). The surgical fix is an explicit git fetch +refs/tags/X:refs/tags/X step after checkout.
How it was discovered
v1.6.8's commit subject was a one-liner; its tag annotation was a structured multi-paragraph body. The release page on GitHub published the one-liner. v1.6.7 had looked fine only because its commit message and tag annotation were nearly identical content — the bug was hidden by coincidence.
Verifying this release
This release annotation itself is the test. If the body you're reading on the GitHub Releases page contains the section headers above, the fix worked.
220 tools, unchanged.