{"id":"6ab1c262e712ab239bfc5531","title":"2026 09 22 Issue 20 Ci Publish Release Notes Only After The Deploy Succeeds","path":"how-to/committee/release-notes/2026-09-22-issue-20-ci-publish-release-notes-only-after-the-deploy-succeeds","contentMarkdown":"# 22-Sep-2026 — ci: publish release notes only after the deploy succeeds [#20](https://github.com/nbarrett/ngx-ramblers/issues/20)\n\n## [build 959](https://github.com/nbarrett/ngx-ramblers/actions/runs/35668027577) — [commit b79d471](https://github.com/nbarrett/ngx-ramblers/commit/b79d471cf90734b956360832cdda3ce7ba1b2790)\n\n_____\n\n## What's new\n\nRelease notes were being published as soon as a push started, at the same time as the tests and the deploy. They now wait until the staging deploy has succeeded. A failed deploy does not publish notes.\n\n## At a glance\n\n- Release notes are no longer published before the site deploy.\n- A deploy that fails leaves the notes unpublished.\n\n## What's new\n\nThe release notes for a push to main are published by their own job, separately from the site deploy. That job stopped immediately because it had not installed the application dependencies the note generator needs. It now installs them first, so a push can publish its notes.\n\n## At a glance\n\n- A failed site deploy can still publish the release notes for that push.\n- The note job no longer stops on a missing application dependency.","contentHtml":"<h1>22-Sep-2026 — ci: publish release notes only after the deploy succeeds <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/20\">#20</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/35668027577\">build 959</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/b79d471cf90734b956360832cdda3ce7ba1b2790\">commit b79d471</a></h2>\n<hr>\n<h2>What&#39;s new</h2>\n<p>Release notes were being published as soon as a push started, at the same time as the tests and the deploy. They now wait until the staging deploy has succeeded. A failed deploy does not publish notes.</p>\n<h2>At a glance</h2>\n<ul>\n<li>Release notes are no longer published before the site deploy.</li>\n<li>A deploy that fails leaves the notes unpublished.</li>\n</ul>\n<h2>What&#39;s new</h2>\n<p>The release notes for a push to main are published by their own job, separately from the site deploy. That job stopped immediately because it had not installed the application dependencies the note generator needs. It now installs them first, so a push can publish its notes.</p>\n<h2>At a glance</h2>\n<ul>\n<li>A failed site deploy can still publish the release notes for that push.</li>\n<li>The note job no longer stops on a missing application dependency.</li>\n</ul>\n"}