Skip to content

Change how renovate handles node versions - #689

Merged
calebeby merged 1 commit into
v-nextfrom
renovate-node-version
May 7, 2020
Merged

Change how renovate handles node versions#689
calebeby merged 1 commit into
v-nextfrom
renovate-node-version

Conversation

@calebeby

Copy link
Copy Markdown
Contributor

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 engines field 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:

@calebeby
calebeby requested review from a team and tylerstickaMay 7, 2020 23:19

@tylerstickatylersticka left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM AFAICT ¯\_(ツ)_/¯

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@calebeby@tylersticka