chore: upgrade to Node 24 LTS (ENG-231)

[Copilot]

Pull Request

Checklist

• Have you read Digital Catapult's Code of Conduct?
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard to understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.

PR Type

• Chore
• Documentation Update

Linked tickets

ENG-231

High level description

Upgrade to Node 24 LTS and align npm to version 11.

Detailed description

Version bump

• Bumped package version from 3.0.58 to 3.1.0

Runtime upgrades

• Updated Node engine from ^22.x.x to 24.x
• Updated npm engine from ^10.x.x to 11.x
• Regenerated package-lock.json via npm install

No workflow changes required

• All GitHub Actions workflows use shared workflows via uses: - no local setup-node actions to update

Describe alternatives you have considered

N/A

Operational impact

Standard platform uplift. Pipelines and images will rebuild normally.

Additional context

N/A

Original prompt

Prompt: One commit upgrade to Node 24 LTS

Objective
Upgrade this repository to Node 24 LTS. Align npm to 11. Bump the package.json version by one minor version. Update any references accordingly, including developer guidance materials. Create a PR referencing ENG-231. Perform all work in one single commit.

⸻

Branching

1. Pull the latest default branch.
2. Create branch: chore/upgrade-node-24.
3. All work must be contained in one commit.

⸻

Scope to update

GitHub Actions workflows
• Only update workflows that are not calling shared workflows via uses: //.github/workflows/...@....
• For local workflows:

• uses: actions/setup-node@v6
  with:
  node-version: '24.x'
  cache: 'npm'

package.json
• Update engines to:

"engines": { "node": "24.x", "npm": "11.x" }

• Increase the version by one minor version. Reset patch to .0 if needed.

package-lock.json
• After editing package.json:

npm install

Dockerfiles
• Update base images to explicit Node 24 variants (for example node:24-bookworm or node:24-alpine).
• If the Dockerfile previously installed npm or node globally (for example via rpm or curl installers), remove those steps because Node 24 images include npm 11 already.
• Do not add debugging or version print commands.

Docker Compose
• Update Node-based images or build contexts if present.

Version files
Set to 24 if present:
• .nvmrc
• .node-version (nodenv)
• .tool-versions (asdf)
• Volta config if used

Devcontainers
• Update .devcontainer/* to use Node 24 if present.

Testcontainers
• If testcontainers code references explicit Node images, update them to Node 24 equivalents.

Documentation
• Replace references to Node 22 with Node 24.

copilot-instructions.md
• If present and it references Node versions or workflow instructions, update them to reflect Node 24 and npm 11.

⸻

Commit Message

Commit message must reflect the actual work done. Example:

chore: upgrade to Node 24 LTS and bump minor version (ENG-231)

⸻

Pull Request

Title

chore: upgrade to Node 24 LTS (ENG-231)

Body

Pull Request

Checklist

• Have you read Digital Catapult's Code of Conduct?
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard to understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.

PR Type

• Chore
• Documentation Update

Linked tickets

ENG-231

High level description

Upgrade this repository to Node 24 LTS and bump the package version.

Detailed description

Describe alternatives you have considered

N/A

Operational impact

Standard platform uplift. Pipelines and images will rebuild normally.

Additional context

N/A

⸻

Enforcement Notes (for the agent)
• Before commit: collect changed files and use them to write the PR detailed description section.
• Do not describe or mention items that were not changed.
• Do not add debug commands to Dockerfiles.
• Remove any manual npm or node installation steps that are now redundant.
• Ensure copilot-instructions.md is updated if it mentions Node versioning or developer environment guidance.
• Exactly one commit.
• Push and open PR.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.