-
Notifications
You must be signed in to change notification settings - Fork 882
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 for node v18 #20839
Merged
Merged
Upgrade for node v18 #20839
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
d3b59fd
to
b9cacc5
Compare
The UI library tests are failing with node 20
Pull Request Test Coverage Report for Build 1c577ba9c975592063e97de03292c00eea9e6c73
💛 - Coveralls |
… and use it in CI and release prosessing
Using the 2 spaces as specified in editorconfig Rewording the comments a bit
b938de6
to
47d3396
Compare
This is never going to get a nice doc comment. And I would like to trigger the yoastseo tests on the CI :)
it seems to be happening already on |
enricobattocchi
approved these changes
Jan 19, 2024
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.
Ok for me
…upgrade-for-node # Conflicts: # yarn.lock
By doing the same trick again as in #21055 Without this, the UI library build can not find `@babel/helper-create-regexp-features-plugin`
d-claassen
approved these changes
Jan 22, 2024
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.
Looks good to me too! ✅
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
changelog: non-user-facing
Needs to be included in the 'Non-userfacing' category in the changelog
Shopify
This PR impacts Shopify.
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.
Context
Node LTS compatibility is the goal.
Not only that, but also adding some structure to have the code as source of truth for future version changes. The idea is that this will make it easier to test and thus upgrade further.
Added bonus is us streamlining the version we use locally to also be used in our CI and releasing.
Summary
This PR can be summarized in the following changelog entry:
@wordpress/scripts
and@wordpress/dependency-extraction-webpack-plugin
, for their compatibility with Node v18.MiniCssExtractPlugin
usage in our Webpack configuration, not being removed from default config and updating to passing a relative path. This was needed after the upgrade of WP scripts..nvmrc
, and use that in our GH-actions.VERSIONS.json
file that holds information about our used versions for Composer, Node, PHP and Yarn. Though Composer and PHP are the only ones currently read from. Node and Yarn are specified in.nvmrc
and.yarnrc
, respectively.Relevant technical choices:
.nvmrc
as source of truth for the Node version as that syncs up with development..yarnrc
as source of truth for the Yarn version, because that is how Yarn enforces it (it turns out the brief Yarn upgrade did not work in the first place).VERSIONS.json
is an implementation from our Devops that was used in our platform already. It is currently implemented on a test branch of our CI. And currently has a test path in there to pull in this branch, for testing purposes.Test instructions
Test instructions for the acceptance test before the PR gets merged
This PR can be acceptance tested by following these steps:
Locally [devs only]
PR build
RC/Release
Arnoud made a branch on our CI that pulls in this branch and reads from
VERSIONS.json
. This makes it so we can run the PRE/test versions of our RC and release scripts on this branch.UI library Storybook [devs only]
yarn workspace @yoast/ui-library storybook
)Relevant test scenarios
Test instructions for QA when the code is in the RC
QA can test this PR by following these steps:
Impact check
This PR affects the following parts of the plugin, which may require extra testing:
UI changes
Other environments
[shopify-seo]
, added test instructions for Shopify and attached theShopify
label to this PR.Documentation
Quality assurance
Innovation
innovation
label.Fixes #19565