{"id":"69b48d93c83decbc8ed519c8","title":"2026 03 13 Other","path":"how-to/committee/release-notes/2026-03-13-other","contentMarkdown":"# 13-Mar-2026 — Workflows and Deploy: 2 CI updates\n\n## [build 523](https://github.com/nbarrett/ngx-ramblers/actions/runs/23072354808) — [commit dbbdd11](https://github.com/nbarrett/ngx-ramblers/commit/dbbdd11f9cd59430753f5ec48f75ee2908aaeb34)\n\n_____\n\n## What changed\n- Added npm fetch retry settings to root and server dependency installs in the test and deploy jobs.\n- Increased retry backoff for package download failures seen on GitHub runners.\n## Why\n- Recent runs failed with transient `ECONNRESET` errors during `npm ci`.\n- The workflow was otherwise healthy, with lint and test stages passing when installs completed.\n## Behaviour\n- This does not change build, test, or deployment logic.\n- It only makes GitHub Actions installs more resilient to temporary network issues.\n\n### **deploy**: make full deploy explicit after successful build\n\n## What changed\n- Removed commit-message-driven all-environments deployment.\n- Updated the push helper to wait for the main build workflow for the pushed commit.\n- Triggered the all-environments deploy workflow only after that build succeeds.\n- Passed the successful build run number as the deploy image tag for traceability.\n## How to use\n- Use a normal commit message with no deployment marker.\n- For staging only, push normally.\n- For a full deploy, run the explicit push flow so the agent or terminal waits for the build and then dispatches the all-environments workflow.\n- The follow-up deploy uses the exact successful build run number as `image_tag`.\n## Behaviour\n- Staging still deploys first through the main build workflow.\n- All-environments deploy now requires an explicit action instead of hidden commit-message behaviour.","contentHtml":"<h1>13-Mar-2026 — Workflows and Deploy: 2 CI updates</h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/23072354808\">build 523</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/dbbdd11f9cd59430753f5ec48f75ee2908aaeb34\">commit dbbdd11</a></h2>\n<hr>\n<h2>What changed</h2>\n<ul>\n<li>Added npm fetch retry settings to root and server dependency installs in the test and deploy jobs.</li>\n<li>Increased retry backoff for package download failures seen on GitHub runners.</li>\n</ul>\n<h2>Why</h2>\n<ul>\n<li>Recent runs failed with transient <code>ECONNRESET</code> errors during <code>npm ci</code>.</li>\n<li>The workflow was otherwise healthy, with lint and test stages passing when installs completed.</li>\n</ul>\n<h2>Behaviour</h2>\n<ul>\n<li>This does not change build, test, or deployment logic.</li>\n<li>It only makes GitHub Actions installs more resilient to temporary network issues.</li>\n</ul>\n<h3><strong>deploy</strong>: make full deploy explicit after successful build</h3>\n<h2>What changed</h2>\n<ul>\n<li>Removed commit-message-driven all-environments deployment.</li>\n<li>Updated the push helper to wait for the main build workflow for the pushed commit.</li>\n<li>Triggered the all-environments deploy workflow only after that build succeeds.</li>\n<li>Passed the successful build run number as the deploy image tag for traceability.</li>\n</ul>\n<h2>How to use</h2>\n<ul>\n<li>Use a normal commit message with no deployment marker.</li>\n<li>For staging only, push normally.</li>\n<li>For a full deploy, run the explicit push flow so the agent or terminal waits for the build and then dispatches the all-environments workflow.</li>\n<li>The follow-up deploy uses the exact successful build run number as <code>image_tag</code>.</li>\n</ul>\n<h2>Behaviour</h2>\n<ul>\n<li>Staging still deploys first through the main build workflow.</li>\n<li>All-environments deploy now requires an explicit action instead of hidden commit-message behaviour.</li>\n</ul>\n"}