build: Upgrade to Node 20 #35342
Open
build: Upgrade to Node 20 #35342
+47
−90
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
feanil
requested changes
Sep 26, 2024
There was a problem hiding this comment.
@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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Part of openedx/public-engineering#230
package-lock.jsonwith nodev20and NPM10..nvmrctov20lockfileversion check workflow