{"id":"6ab2f5d4f28941ca4baaf0f8","title":"2026 09 22 Issue 20 2","path":"how-to/committee/release-notes/2026-09-22-issue-20-2","contentMarkdown":"# 22-Sep-2026 — keep one note per commit, published after deploy [ref #20](https://github.com/nbarrett/ngx-ramblers/issues/20)\n\n## [build 963](https://github.com/nbarrett/ngx-ramblers/actions/runs/35786462562) — [commit f166cae](https://github.com/nbarrett/ngx-ramblers/commit/f166cae1f023af70ed12d02731c15a11939c549c)\n\n_____\n\n## What's new\n\nEach commit keeps its own release note, with its own What's new, At a glance and Technical changes headings. Notes are published after the site deploy has succeeded, and a push only covers the commits in that push.\n\n## At a glance\n\n- A release note keeps the headings written for that commit.\n- Notes are not published before the deploy.\n- A push does not republish the history of the project.","contentHtml":"<h1>22-Sep-2026 — keep one note per commit, published after deploy <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/20\">ref #20</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/35786462562\">build 963</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/f166cae1f023af70ed12d02731c15a11939c549c\">commit f166cae</a></h2>\n<hr>\n<h2>What&#39;s new</h2>\n<p>Each commit keeps its own release note, with its own What&#39;s new, At a glance and Technical changes headings. Notes are published after the site deploy has succeeded, and a push only covers the commits in that push.</p>\n<h2>At a glance</h2>\n<ul>\n<li>A release note keeps the headings written for that commit.</li>\n<li>Notes are not published before the deploy.</li>\n<li>A push does not republish the history of the project.</li>\n</ul>\n"}