Skip to content

Support just one node version for from-source install

Lukas 'ai-pi' Eipert requested to merge 29479-leipert-support-only-one-node-version-for-from-source-install into master

What does this MR do and why?

We currently still claim support of node@14 for installing from source. It has been a long outstanding issue to just support one node version from source install. Generally supporting more versions isn't expensive, until it is. Before we move to node@18, it probably makes sense to support just the current node version we use, node@16. The other LTS versions of node likely work, we just stop checking whether they do.

This generally aligns with the amount of golang and ruby versions we support.

Furthermore it enables us to remove a few QA jobs from our pipelines, that only ever checked that webpack compiled successfully in the node LTS versions. We also had one job that checked future versions, but it was allowed to fail and therefore didn't have much value.

See also: #29479 (closed)

Screenshots or screen recordings

N/A

How to set up and validate locally

N/A

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #29479 (closed)

Edited by Lukas 'ai-pi' Eipert

Merge request reports