{"id":"6a5c96caef317779435d46d3","title":"2026 07 19 Issue 320","path":"how-to/committee/release-notes/2026-07-19-issue-320","contentMarkdown":"# 19-Jul-2026 — Release Note build headings read as issue references, and generator defects in titles and bullets [#320](https://github.com/nbarrett/ngx-ramblers/issues/320)\n\n## [build 780](https://github.com/nbarrett/ngx-ramblers/actions/runs/29680933358) — [commit cb5f19c](https://github.com/nbarrett/ngx-ramblers/commit/cb5f19c66c91912f201e7aec525e390eaf79422a)\n\n_____\n\nThe build heading rendered the workflow run number as `GitHub #779`, which reads as a reference to issue 779. No such issue exists, so the number misled anyone scanning the page even though the link itself resolved to the correct run. Headings now read `[build 779](https://ngx-ramblers.org.uk/<run url>)`.\n\nAlso in this change:\n\n- Compound conventional-commit types and scopes such as `fix+refactor(inbox+server):` are now parsed, so the raw prefix no longer leaks into the release-note title.\n- `Technical changes` sections are dropped from commit bodies, keeping the notes aimed at committee readers rather than developers.\n- Body bullet lines are no longer split on dash segments, which was breaking a single bullet into several.\n- Existing pages are recognised whether they carry the old `GitHub #N` / `Build #N` headings or the new `build N` form, so refreshes and same-day updates keep working.\n\nThe 13 historic notes whose links pointed at a run number instead of a run id have been repaired separately, in place on the site.","contentHtml":"<h1>19-Jul-2026 — Release Note build headings read as issue references, and generator defects in titles and bullets <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/320\">#320</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/29680933358\">build 780</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/cb5f19c66c91912f201e7aec525e390eaf79422a\">commit cb5f19c</a></h2>\n<hr>\n<p>The build heading rendered the workflow run number as <code>GitHub #779</code>, which reads as a reference to issue 779. No such issue exists, so the number misled anyone scanning the page even though the link itself resolved to the correct run. Headings now read <code>[build 779](https://ngx-ramblers.org.uk/&lt;run url&gt;)</code>.</p>\n<p>Also in this change:</p>\n<ul>\n<li>Compound conventional-commit types and scopes such as <code>fix+refactor(inbox+server):</code> are now parsed, so the raw prefix no longer leaks into the release-note title.</li>\n<li><code>Technical changes</code> sections are dropped from commit bodies, keeping the notes aimed at committee readers rather than developers.</li>\n<li>Body bullet lines are no longer split on dash segments, which was breaking a single bullet into several.</li>\n<li>Existing pages are recognised whether they carry the old <code>GitHub #N</code> / <code>Build #N</code> headings or the new <code>build N</code> form, so refreshes and same-day updates keep working.</li>\n</ul>\n<p>The 13 historic notes whose links pointed at a run number instead of a run id have been repaired separately, in place on the site.</p>\n"}