-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Create Block: Match specified engines with Gutenberg and Core #61430
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: 0 B Total Size: 1.74 MB ℹ️ View Unchanged
|
Flaky tests detected in 6ef8a0a. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/8981259018
|
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.
Thank you for the follow-up.
It doesn't differ that much from the requirements I see in other JS projects:
Node v20.9.0 comes with npm v10.1.0, so that should also be a minimum version used.
I guess, it's fine to use the same version everywhere.
Thanks for the review, @gziolo! |
@fabiankaegy, an entry in the changelog is always useful 👍 Do you think the requirements should be lifted to Node 18 (still long term support version) like for all other WP packages? |
@gziolo I'm fine with node 20 :) My main comment was that usually updating the minimum required node version constitutes a breaking change update of the package. So In this case this should have meant changing the version of the package to |
Yes, that sounds right. It's also too late for major version upgrade now, but at least we could add the CHANGELOG to the minor version that was impacted. |
Opened #62791 to address the issue mentioned by @fabiankaegy. |
What?
This is a follow-up to #60962.
PR updates engines specified in the
package.json
file to match Gutenberg and WP Core.CI checks should be green.
Why?
The
npm install
might fail when using node version managers due to a version mismatch.Testing Instructions for Keyboard
Same.