-
Notifications
You must be signed in to change notification settings - Fork 221
Conversation
Size Change: +6.92 kB (0%) Total Size: 1.13 MB
ℹ️ View Unchanged
|
It seems we also need to force our actions to use npm 7 cc @nerrad do you have a pointer for this? |
For node we just have to remove this action in our workflows: For npm 7, since it's not lts, we'll probably just have to install it directly by adding the following to any workflows running npm install as a step: npm install -g npm@7 |
I updated that section to node 14. If we remove it, won't break our workflow? why did it add at first? |
I added it because github actions by default now install node 14 (because it's now LTS) and we weren't ready to update to node 14 yet :) |
You can make changes to the workflows in this pull only. |
This PR has been marked as If deemed still relevant, the pr can be kept active by ensuring it's up to date with the main branch and removing the stale label - otherwise it will automatically be closed after 10 days. |
This PR updates npm to 7 so we can use workspaces.
I also updated a couple of dependencies to bypass some errors.
I can't run e2e locally due to
nodegit
not being available, so I'm testing here.Will add more testing instruction once I get e2e to work.
What works
npm install
.npm run build
.npm start
.npm run test
.npm run test:e2e
.npm run wp-env
.