Skip to content
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

Update to node 12.19.1 #47866

Merged
merged 2 commits into from Dec 1, 2020
Merged

Update to node 12.19.1 #47866

merged 2 commits into from Dec 1, 2020

Conversation

scinos
Copy link
Contributor

@scinos scinos commented Nov 30, 2020

Changes proposed in this Pull Request

Update Node to 12.19.1

Testing instructions

  • N/A

@scinos scinos requested a review from a team as a code owner November 30, 2020 13:36
@matticbot
Copy link
Contributor

@matticbot matticbot added the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Nov 30, 2020
@scinos scinos requested a review from a team November 30, 2020 13:43
@matticbot
Copy link
Contributor

This PR does not affect the size of JS and CSS bundles shipped to the user's browser.

Generated by performance advisor bot at iscalypsofastyet.com.

Copy link
Member

@tyxla tyxla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Builds well and smoke tests well for me. 👍

@noahtallen
Copy link
Member

@scinos I pushed a small change to the toolkit plugin readme to trigger its CI tests. There was a wp-env problem related to one of the node versions (see #47489), and I want to make sure we don't re-introduce that problem.

@matticbot
Copy link
Contributor

Caution: This PR affects files in the Editing Toolkit Plugin on WordPress.com
Please ensure your changes work on WordPress.com before merging.

D53528-code has been created so you can easily test it on your sandbox. See this FieldGuide page about developing the Editing Toolkit Plugin for more info: PCYsg-ly5-p2

Copy link
Member

@noahtallen noahtallen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The phpunit failure observed here is a different problem than the one I described (and we are already tracking it elsewhere). It looks like wp-env is able to startup correctly with this new node version, which is all i wanted to verify 👍

@scinos scinos merged commit 1392a0e into trunk Dec 1, 2020
@scinos scinos deleted the update/node-12.19.1 branch December 1, 2020 08:23
@matticbot matticbot removed the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Dec 1, 2020
jeherve added a commit to Automattic/jetpack that referenced this pull request Dec 3, 2020
Calypso was updated earlier, in Automattic/wp-calypso#47866

Let's follow suit so when you develop in both environments, you don't have to constantly switch.
kraftbj pushed a commit to Automattic/jetpack that referenced this pull request Dec 7, 2020
Calypso was updated earlier, in Automattic/wp-calypso#47866

Let's follow suit so when you develop in both environments, you don't have to constantly switch.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants