fix: match CHANGELOG headers with date suffix in release workflow

[abtreece]

Summary

• Fix awk extraction in release.yml that failed to match CHANGELOG headers with date suffixes (e.g. ### v0.41.1 (2026-04-22))
• Use index() for exact string prefix matching with space boundary — avoids regex metachar issues and version prefix collisions
• Revert redundant goreleaser before hook and release.header since the release workflow already handles extraction via gh release edit

Root cause

The release workflow used $0 == "### " tag which requires an exact line match, but CHANGELOG headers include a date suffix. This is why v0.41.1 published with empty release notes.

Test plan

• Verified awk extraction matches ### v0.41.1 (2026-04-22) correctly
• Verified v0.41.10 does not false-match against v0.41.1
• Verified regex metachar in dots (v0X41X1) no longer false-matches
• goreleaser check validates config

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.06%. Comparing base (a5fc549) to head (09db851).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #590   +/-   ##
=======================================
  Coverage   67.06%   67.06%           
=======================================
  Files          53       53           
  Lines        7035     7035           
=======================================
  Hits         4718     4718           
  Misses       2090     2090           
  Partials      227      227           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull request overview

Updates the release automation so GitHub release notes can be populated from the curated CHANGELOG content during GoReleaser runs.

Changes:

• Add a GoReleaser before.hooks step that extracts the current tag’s CHANGELOG section into a temp markdown file.
• Configure GoReleaser release.header to use the extracted content as the release header.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The awk match ^### v{{ .Version }} is a prefix regex, so version 0.41.1 would also match a ### v0.41.10 ... section (and . is treated as “any char”). Consider matching the exact section header (e.g., compare the full line or enforce a boundary like ([[:space:]]|$) after the version) to avoid extracting the wrong release notes.

Suggested change

	- bash -c 'awk "/^### v{{ .Version }}/{found=1; next} /^### v/{if(found) exit} found" CHANGELOG > /tmp/release_header.md'
	- bash -c "awk -v ver='{{ .Version }}' '\$0 == \"### v\" ver {found=1; next} /^### v/{if(found) exit} found' CHANGELOG > /tmp/release_header.md"

[abtreece]

Valid point. Reverted the goreleaser hook entirely — the release workflow already handles extraction. Fixed the workflow's awk to use index() for exact string prefix matching with boundary check, avoiding both the regex metachar issue and prefix collision.

[Copilot]

This hook will succeed even if no matching CHANGELOG section is found (producing an empty /tmp/release_header.md), which can lead to publishing a release with blank notes. Consider making the extraction fail the build when the section is missing/empty (e.g., have awk exit non-zero if found was never set, and/or check the output file is non-empty).

Suggested change

	- bash -c 'awk "/^### v{{ .Version }}/{found=1; next} /^### v/{if(found) exit} found" CHANGELOG > /tmp/release_header.md'
	- bash -c 'awk '"'"'/^### v{{ .Version }}/{found=1; next} /^### v/{if(found) exit} found {print; printed=1} END {if(!found || !printed) exit 1}'"'"' CHANGELOG > /tmp/release_header.md && test -s /tmp/release_header.md'

[abtreece]

Reverted the goreleaser hook. The existing release workflow already warns on empty extraction (line 80-82) which is sufficient — a missing CHANGELOG section shouldn't block artifact publishing.

[Copilot]

This release.header change likely won’t achieve the PR goal in CI because the current GitHub Actions release workflow already extracts notes into /tmp/release_notes.md and then overwrites the GitHub release body via gh release edit --notes-file ... after GoReleaser runs. To actually populate release notes via GoReleaser, the workflow should be updated to remove/align that post-step (or it will continue to override whatever GoReleaser generates).

[abtreece]

Good catch. Reverted the goreleaser changes and fixed the actual bug in the workflow instead — the awk was using exact line match ($0 == "### " tag) but CHANGELOG headers include a date suffix (e.g. ### v0.41.1 (2026-04-22)). Now uses index() for exact string prefix matching with a space boundary.