-
Notifications
You must be signed in to change notification settings - Fork 2.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
CircleCI runs Windows tests under unsupported Node.js 14 - renovate fails #721
Comments
I don't have the experience with CircleCI to confidently attempt this change, so I need to leave it to somebody else with the right skills. I noticed also that an older version of Windows Server is being used. Would it be a good time to upgrade this as well?
|
Hi @MikeMcC399 , yeah it looks like we need to upgrade the image as you suggested. Thanks for opening this issue so we can track this work and hopefully find some time to do this. |
Could you perhaps look at this issue also as part of your updating work for Node.js |
@MikeMcC399 #739 should get us to Node 20 |
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Issue
Windows tests in CircleCI specified through .circleci/config.yml use the image
windows-server-2019-vs2019:stable
with the now unsupported Node.js14.17.5
version.npm ERR! Cannot read property 'npm-run-all' of undefined
. This PR is attempting to bump thelockfileVersion
in package-lock.json from2
to3
. npmlockfileVersion
3
is used by npm v9, however it is only backwards compatible to npm v7. Node.js14.17.5
is configured with the earlier version npm6.14.14
thus causing a compatibility issue.14
entered end-of-life on April 30, 2023.18
as the required version for this repo.Suggestion
Update .circleci/config.yml to run under Node.js
18
(currently the LTS version) for the Windows tests.The text was updated successfully, but these errors were encountered: