-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
chore: @npmcli/[email protected] #6807
Conversation
5e47b9f
to
66399f0
Compare
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? |
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
This should now be rebased. It includes two breaking changes for updating the engines on |
There should be no more expected CI failures in this PR. If any runs fail they should be examined and fixed. |
c3541cb
to
826f3f0
Compare
This align all private workspaces to the same engines as the CLI and all public workspaces to ^16.14.0 || >=18.0.0
826f3f0
to
69342ff
Compare
No description provided.