screentinker 243fc6688c Release notes: publish the changelog entry, not the commit subjects (#273) ... Cutting 1.9.34 produced a release page reading: ### Changes - chore(release): v1.9.34 - Changelog: one 1.9.34 entry, and credit where it was missing while the entry describing single sign-on, the removal of the last native image dependency, three update failures and every outside contributor sat in CHANGELOG.md and was never published. The notes on the release page are what most people actually read; they should be the written ones. The workflow now takes the section for the version being released and uses it as the body. Commit subjects remain the fallback for a version with no entry, so a release never publishes with no notes at all — scripts/bump-version.sh already warns about a missing heading, and this is the same gap showing up downstream. awk rather than sed for the extraction: the body contains regex metacharacters and markdown that a sed range would mangle. Verified against the real file: 1.9.34 extracts 269 lines and stops at the next heading with all 13 contributor credits intact, 1.9.33 and 1.9.29 extract cleanly, and a version with no entry yields nothing and takes the fallback. v1.9.34's notes were corrected by hand after release; this is so the next one does not need that.		2026-08-13 22:31:32 -05:00
..
workflows	Release notes: publish the changelog entry, not the commit subjects (#273)	2026-08-13 22:31:32 -05:00