Uh oh!
There was an error while loading. Please reload this page.
Change how renovate handles node versions - #689
Merged
Conversation
1 task
This was referenced Aug 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This PR is created with the hopes that merging it will prevent renovate from making PR's like this: #685 and this: #680 (for the node version)
The
enginesfield is how we specify which node versions we allow our package consumers to use. If that version is pinned, then that means that we are telling our package consumers that they must use node 14.2.0 only, but node releases new versions really frequently so that would be really annoying.I don't know if these configuration changes will do what we want, but we can't really test it until we merge this. It was my best-guess of what would work based on these documentation pages: