-
Notifications
You must be signed in to change notification settings - Fork 38
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
release 2.5.1 Node >18 incompatibility #337
Comments
I guess you might be using yarn, pnpm and npm does not enable engine-strict by default.
Or if you have other locked versions of pnpm and node that renovate uses, you can tell me. |
Indeed I do use yarn, in my case, using the ignore-engines option worked, when is it planned to upgrade to pnpm V9 ? I can add the option in a .yarnrc to apply it by default for my project, but would rather keep this check in my dev environement. |
## [2.5.2](v2.5.1...v2.5.2) (2024-06-24) ### Bug Fixes * yarn install error ([5beafa0](5beafa0)), closes [#337](#337)
🎉 This issue has been resolved in version 2.5.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I was on the 2.4.3 release and could use the package with no problems, when I upgraded to the latest release (2.5.1), I get the following error during installation.
I saw that the engine in package.json was changed:
Release 2.4.3
Release 2.5.1
Is there a particular reason for this change ?
The text was updated successfully, but these errors were encountered: