E2E workflows do not run due to incompatible Node.js version

Summary

The e2e-full and e2e-perf GitHub Actions workflows are currently failing during npm ci, before the test suites are started.

The failing runs are based on commit:

8782f884ed3b31d853fe655ee07ed89fd27f7eef

At that commit, package.json reports Open MCT version 4.3.1 and requires:

"node": ">=24.14.1"

The latest published GitHub release is still v4.1.0, so 4.3.1 here refers to the repository/package version at the analyzed commit, not the latest release.

The affected workflows still use:

- uses: actions/setup-node@v4
  with:
    node-version: 'lts/hydrogen'

This resolves to Node.js 18.20.8, which is below the minimum version required by the project.

As a result, npm ci fails with EBADENGINE and the E2E tests never start.

Expected vs Current Behavior

Expected

The workflows should use a Node.js version compatible with the version declared in package.json, install dependencies successfully, and continue to the E2E/performance test steps.

Current

The workflow fails at:

npm ci --no-audit --progress=false

with:

npm error code EBADENGINE
npm error engine Unsupported engine
npm error notsup Not compatible with your version of node/npm: [email protected]
npm error notsup Required: {"node":">=24.14.1"}
npm error notsup Actual:   {"npm":"10.8.2","node":"v18.20.8"}

Steps to Reproduce

1. Run e2e-full or e2e-perf on master.
2. actions/setup-node@v4 configures lts/hydrogen.
3. The runner uses Node.js 18.20.8.
4. npm ci --no-audit --progress=false fails with EBADENGINE.

Environment

• Open MCT Version: 4.3.1
• Commit: 8782f884ed3b31d853fe655ee07ed89fd27f7eef
• Latest published GitHub release: v4.1.0
• Deployment Type: GitHub Actions
• OS: Ubuntu 24.04 (ubuntu-latest)
• Node.js: 18.20.8
• Required Node.js: >=24.14.1
• Browser: N/A — the workflow fails before browser-based tests start

Impact Check List

• Data loss or misrepresented data?
• Regression? Did this used to work or has it always been broken?
• Is there a workaround available?
• Does this impact a critical component?
• Is this just a visual bug with no functional impact?
• Does this block the execution of e2e tests?
• Does this have an impact on Performance?

Additional Information

Affected workflows include at least:

• .github/workflows/e2e-full.yml
• .github/workflows/e2e-perf.yml

Example failing runs:

• e2e-full #409 https://github.com/nasa/openmct/actions/runs/33283886868

• e2e-perf #3851 https://github.com/nasa/openmct/actions/runs/33282922424

The most direct fix would be to update the Node.js version used by these workflows to match the project requirement, for example:

- uses: actions/setup-node@v4
  with:
    node-version: '24.14.1'

It may also be worth moving the Node.js version to a shared repository-level version file and referencing it from the workflows to avoid this kind of version drift in the future.