13-Mar-2026 — Runtime, Workflows and 1 more areas: 1 build change and 2 CI updates #185

build 524 — commit d6a230d

Runtime baseline

Upgrade the repository baseline from Node 22.19.0 / npm 10.9.3 to Node 24.14.0 / npm 11.9.0.

Tooling and infrastructure

Align .nvmrc, package engine declarations, Docker, and GitHub Actions workflow runtime settings with the Node 24 baseline. Opt workflow JavaScript actions into Node 24 and keep the deploy matrix at max-parallel 6 with npm fetch retries in deploy installs.

Compatibility updates

Upgrade Serenity, WebdriverIO, and npm-failsafe dependencies so local install, build, and test flows run on Node 24 without unsupported engine warnings.

Documentation

Update README, AGENTS guidance, release-notes docs, and codebase-evolution-stats.html so the documented platform baseline matches the actual runtime target.

Ramblers export fix

Use the configured public group URL for Ramblers CSV website links so local development exports do not publish localhost URLs into Walks Manager.

Verification

Validated locally on Node 24 with lint, frontend tests, server tests, targeted URL service coverage, and production build.

Follow-on

Leave Angular 21 as separate follow-on work under issue #185 so framework changes are isolated from the runtime uplift.

workflows: add npm fetch retries to GitHub installs

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.