-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Node: Dependabot only runs with Node 16/NPM 8, but breaks if engines in any package require Node 18/NPM 9 #6654
Comments
Did you read my response to a similar issue? I'm going to leave open as a reminder to double-check whether we should bump to Node 18 / NPM 9 for the Dependabot service that runs on GitHub... |
Given those versions are LTS, would make sense to me (and aligned with the spirit of Dependabot re: getting to supported versions) |
I am facing the same issue due to the use of NodeJS I just wanted to leave here a link to the NodeJS release schedule, so that it may be easier to keep track when to update to node So, transitioning to NodeJS Hope this helps to keep track of the necessary information related to NodeJS |
I think there is an open PR which should address this issue: #7348 |
Any updates here? |
Yarn 4.0.0-rc.47 just started requiring Node 18 instead of Node 16, causing failures like so:
https://github.com/eve-val/eve-roster/network/updates/690503991 |
Thanks for the fix, @jurre and @christianvuerings. #7348 is merged. (and I confirm it works for me) |
there are later tickets for Node 20/NPM 10, but I can confirm my original question here for Node 18/NPM 9 is working, so closing this out as the ticket is a year+ old |
Is there an existing issue for this?
Package ecosystem
npm
Package manager version
npm 9
Language version
node 18
Manifest location and content before the Dependabot update
No response
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
We don't have an engines file in our app, though we do use Volta to ensure we run with Node 18/NPM 9
One of our dependencies does have an engine config set.
But dependably fails/complains in this scenario with this error
Is there a way to tell dependably what version to run as?
Native package manager behavior
no issues, as we ensure our app is run using that version listed.
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response
The text was updated successfully, but these errors were encountered: