-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Node.js to version 22 #9647
Labels
enhancement
New feature or request
Comments
Note: this should not be ported to 4.3 and 5.0. |
And if I get your comment correctly, I think this is the unique SR needed, right? |
digging a bit more... Node has been bumped to version 22 only for Uyuni and 5.1/Head, on 5.0 we are not doing thing correctly anymore. tasks
|
Regarding the last comment, tasks done (everything should be fine now, otherwise please let me know):
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you update this checklist, please be sure to update the checklist template too.
node --version
rm -rf web/html/src/node_modules/
yarn all
nodejs-default
(available innodejs-common
) includes at least the version you want to update to (should be no-op sincenodejs-default
tracks the LTS lifecycle)engines.node
insusemanager-frontend/package.json
node-version
in all workflows in.github/workflows
that require itsystemsmanagement:Uyuni:Master
to use the desired module stream for nodejs.npm
package in thesystemsmanagement:Uyuni:Master:Docker/uyuni-push-to-obs
Dockerfilenpm
package in thesystemsmanagement:Uyuni:Master:Docker/uyuni-master-nodejs
Dockerfilenpm
package in theDevel:Galaxy:Manager:4.3:Docker/suma-push-to-obs
Dockerfile and make sure we do NOT use nodejs22. See also prjconfignpm
package in theDevel:Galaxy:Manager:4.3:Docker/suma-4.3-nodejs
Dockerfile and make sure we do NOT use nodejs22. See also prjconfigThe text was updated successfully, but these errors were encountered: