Updating Node.js

Node.js is a build-time dependency for Uyuni's frontend. Node should be kept up-to-date with a stable version that's in long-term support (LTS), please see Node's lifecycle.

Node follows a release cycle where even-numbered releases are stable and odd numbered releases are unstable or experimental.

Shortly, DO update to Node 10.x, 12.x, 14.x etc. Do NOT update to 11.x, 13.x, 15.x etc.

Here's the checklist to update Node:

• Confirm that nodejs-default (available in nodejs-common) includes at least the version you want to update to (should be no-op since nodejs-default tracks the LTS lifecycle)
• Update engines.node in susemanager-frontend/package.json
• Update node-version in all workflows in .github/workflows that require it
• Update Almalinux project config in the project configuration in systemsmanagement:Uyuni:Master to use the desired module stream for nodejs.
• Backport the changes where necessary
• Check that the right nodejs package is in the systemsmanagement:Uyuni:Master:Docker/uyuni-push-to-obs container. If not, change the Dockerfile to force the installation of the right package.
• Same thing for Devel:Galaxy:Manager:4.2:Docker/suma-push-to-obs and any newer versions if applicable.
• Same thing for Manager-4.1/susemanager-utils/testing/docker/4.1/uyuni-push-to-obs*

*As of now, 4.1 is fixed to use nodejs 14. Unless v14 goes EOL during 4.1's lifecycle, we don't plan to upgrade nodejs on this version.