Closed
Conversation
flootr
force-pushed
the
node-20-update
branch
from
4b3b011 to
b2dbe14
Compare
|
Flaky tests detected in b2dbe14. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7105925950
|
Member
|
Looks like 20.x was just installed on the .org build server. 🎉 Since #56331 has more context and discussion, I'm going to close this out in favor of that one. |
Member
Author
|
sounds good! edit: clicked the wrong button 😆 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What?
The current LTS version of Node is now 20. This PR checks how easy it'd be to update, following #53426. This includes npm version 10.
Why?
Node 16 and 18 are no longer LTS.
How?
Testing Instructions
nvm install