-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
build: Upgrade to Node 20 #35342
build: Upgrade to Node 20 #35342
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BilalQamar95 we should not merge this until after this deadline: #35015
2U should be able to move to node 20 today as we're already testing with that so if there are issues with that, those should be raised separately.
@BilalQamar95 has 2U moved to Node 20 for their deployment of edx-platform? |
I don't think they have |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The deadline for this update has arrived, this is good to merge now.
839418c
to
85a891a
Compare
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
2U Release Notice: This PR has been deployed to the edX production environment. |
1 similar comment
2U Release Notice: This PR has been deployed to the edX production environment. |
2U Release Notice: This PR has been rolled back from the edX production environment. |
1 similar comment
2U Release Notice: This PR has been rolled back from the edX production environment. |
2U Release Notice: This PR has been deployed to the edX production environment. |
1 similar comment
2U Release Notice: This PR has been deployed to the edX production environment. |
Description
Part of openedx/public-engineering#230
package-lock.json
with nodev20
and NPM10
..nvmrc
tov20
lockfile
version check workflow