chore: upgrade to Node.js 24

[hopehadfield]

• Updated repository Node baseline in versions.json to 24.14.0
• Updated CI workflow Node setup to 24
• Updated all workspace e2e test package.json files to require engines.node: ">=24"

[gashcrumb]

@subhashkhileri is there a way to kick off e2e tests across workspaces that have them? This kind of change might be a good use-case for a pr-level command to do this.

[subhashkhileri]

@subhashkhileri is there a way to kick off e2e tests across workspaces that have them? This kind of change might be a good use-case for a pr-level command to do this.

@gashcrumb yes we can run the nightly job that runs all of the tests
using / test e2e-ocp-helm-nightly

[subhashkhileri]

/test ?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[hopehadfield]

/test e2e-ocp-helm-nightly

[christoph-jerolimov]

/retest

E2e

[openshift-ci]

@hopehadfield: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-ocp-helm-nightly	be955e2	link	false	/test e2e-ocp-helm-nightly

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.