# 13-Mar-2026 — Workflows and Deploy: 2 CI updates

## [build 523](https://github.com/nbarrett/ngx-ramblers/actions/runs/23072354808) — [commit dbbdd11](https://github.com/nbarrett/ngx-ramblers/commit/dbbdd11f9cd59430753f5ec48f75ee2908aaeb34)

_____

## What changed
- Added npm fetch retry settings to root and server dependency installs in the test and deploy jobs.
- Increased retry backoff for package download failures seen on GitHub runners.
## Why
- Recent runs failed with transient `ECONNRESET` errors during `npm ci`.
- The workflow was otherwise healthy, with lint and test stages passing when installs completed.
## Behaviour
- This does not change build, test, or deployment logic.
- It only makes GitHub Actions installs more resilient to temporary network issues.

### **deploy**: make full deploy explicit after successful build

## What changed
- Removed commit-message-driven all-environments deployment.
- Updated the push helper to wait for the main build workflow for the pushed commit.
- Triggered the all-environments deploy workflow only after that build succeeds.
- Passed the successful build run number as the deploy image tag for traceability.
## How to use
- Use a normal commit message with no deployment marker.
- For staging only, push normally.
- 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.
- The follow-up deploy uses the exact successful build run number as `image_tag`.
## Behaviour
- Staging still deploys first through the main build workflow.
- All-environments deploy now requires an explicit action instead of hidden commit-message behaviour.