{"id":"69d95290ac88dac0e52b6ef9","title":"2026 04 10 Build 582","path":"how-to/committee/release-notes/2026-04-10-build-582","contentMarkdown":"# 10-Apr-2026 — use push-event base SHA so previously-released commits never re-appear [#223](https://github.com/nbarrett/ngx-ramblers/issues/223)\n\n## [build 582](https://github.com/nbarrett/ngx-ramblers/actions/runs/24260454785) — [commit f6236b4](https://github.com/nbarrett/ngx-ramblers/commit/f6236b45b3caa899006d95d7108f293ded738649)\n\n_____\n\n- Workflow now passes the GitHub push event's `before` SHA to the script\nvia `--since`, so each release notes run only considers commits added\nin this push. Falls back to `--latest` if the SHA is unavailable\n(e.g. first push to a branch). The previous `--latest` path was\nunsafe because amended commits inherit the new committer date and\nlegitimate body references like \"see the #223 release\" cause cross\n-release grouping via the issue fallback cascade.\n- Improve the section-heading dedup so the redundant `### **scope**: subject`\nline is collapsed when its subject is already conveyed by the H1.\nStrip the `**scope**:` / `scope:` prefix and use a \"starts with\" match\nso multi-commit groupings whose first subject is in the title also\ncollapse cleanly. Body content is always preserved.\n- Tested via dry-run with `--since HEAD~1`, `--since <sha>`, and\n`--since HEAD~2` to confirm single, specific, and multi-commit cases\nall behave correctly.","contentHtml":"<h1>10-Apr-2026 — use push-event base SHA so previously-released commits never re-appear <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/223\">#223</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/24260454785\">build 582</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/f6236b45b3caa899006d95d7108f293ded738649\">commit f6236b4</a></h2>\n<hr>\n<ul>\n<li>Workflow now passes the GitHub push event&#39;s <code>before</code> SHA to the script\nvia <code>--since</code>, so each release notes run only considers commits added\nin this push. Falls back to <code>--latest</code> if the SHA is unavailable\n(e.g. first push to a branch). The previous <code>--latest</code> path was\nunsafe because amended commits inherit the new committer date and\nlegitimate body references like &quot;see the #223 release&quot; cause cross\n-release grouping via the issue fallback cascade.</li>\n<li>Improve the section-heading dedup so the redundant <code>### **scope**: subject</code>\nline is collapsed when its subject is already conveyed by the H1.\nStrip the <code>**scope**:</code> / <code>scope:</code> prefix and use a &quot;starts with&quot; match\nso multi-commit groupings whose first subject is in the title also\ncollapse cleanly. Body content is always preserved.</li>\n<li>Tested via dry-run with <code>--since HEAD~1</code>, <code>--since &lt;sha&gt;</code>, and\n<code>--since HEAD~2</code> to confirm single, specific, and multi-commit cases\nall behave correctly.</li>\n</ul>\n"}