# 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)

## [build 780](https://github.com/nbarrett/ngx-ramblers/actions/runs/29680933358) — [commit cb5f19c](https://github.com/nbarrett/ngx-ramblers/commit/cb5f19c66c91912f201e7aec525e390eaf79422a)

_____

The 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>)`.

Also in this change:

- 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.
- `Technical changes` sections are dropped from commit bodies, keeping the notes aimed at committee readers rather than developers.
- Body bullet lines are no longer split on dash segments, which was breaking a single bullet into several.
- 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.

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.