Node Version #8130
Replies: 2 comments 6 replies
-
We disabled major updating for node because Renovate would in some cases otherwise dumbly propose an update from a stable to unstable (e.g. from v14 to v15). I think though now we've merged #7157 we should be able to lift this. The relevant code is here: renovate/lib/config/definitions.ts Lines 1560 to 1562 in 326c000 @viceice wdyt? |
Beta Was this translation helpful? Give feedback.
-
I was seeing the same issue as @travi where I wasn't getting node updates. Adding After making both those changes I got a merge request updating the node version in In the renovate logs I can see node appearing under both |
Beta Was this translation helpful? Give feedback.
-
I've had the
lts_latest
policy set in one of my shareable configs for several months. I'd noticed that I hadn't been getting update PRs for node version as a result, but hadn't taken the time to investigate yet.A couple nights ago, I looked through the renovate logs for one of the projects using that config and confirmed that it was recognizing that there was an update that could be applied. I looked through old config-help threads before opening a new thread and found this one. Adding the suggestion from renovatebot/config-help#667 (comment) to my config did produce PRs to a few of my projects. I got the impression from renovatebot/config-help#667 (comment) that a fix was applied to make it unnecessary since that thread was closed. Did that end up getting applied, or do I have something else wrong with my config that prevents it from working as expected?
I also had a couple of those PRs fail to auto merge, like this one because
engines
was not updated in thepackage.json
to match the update in the.nvmrc
(and I lint to ensure that the current execution environment is within the range defined inengines
). Am I wrong in my understanding that this should have been updated to match?Beta Was this translation helpful? Give feedback.
All reactions