Uh oh!
There was an error while loading. Please reload this page.
chore: @npmcli/template-oss@4.19.0 - #6807
Conversation
5e47b9f to
66399f0Comparelukekarrys
commented
Sep 15, 2023
We should land this because it doesn't make the CI failures worse, but it also doesn't fix the issue with running It seems easiest to bump all workspace engines to `^16.14 || >= 18'. @wraithgar what do you think? |
wraithgar
commented
Sep 15, 2023
I think the npm workspaces are going to have to come along with npm in their engines declarations. |
BREAKING CHANGE: @npmcli/config now supports node ^16.14.0 || >=18.0.0
BREAKING CHANGE: libnpmfund now supports node ^16.14.0 || >=18.0.0
lukekarrys
commented
Sep 15, 2023
This should now be rebased. It includes two breaking changes for updating the engines on |
lukekarrys
commented
Sep 15, 2023
There should be no more expected CI failures in this PR. If any runs fail they should be examined and fixed. |
c3541cb to
826f3f0CompareThis align all private workspaces to the same engines as the CLI and all public workspaces to ^16.14.0 || >=18.0.0
826f3f0 to
69342ffCompare
No description provided.