Renovate bumps to unstable version #8018
Replies: 3 comments
-
Because 5.x was temporarily tagged as |
Beta Was this translation helpful? Give feedback.
-
It looks like you have automerge enabled even for that major update - I recommend you don't do that. |
Beta Was this translation helpful? Give feedback.
-
@rarkins thanks for the explanation, I missed that! And thanks for the advice, our decision was intentional as we want to limit the maintenance required on that project. I mitigated the possibility of similar issues in the future by introducing stabilityDays in the config. Thanks again for your support. |
Beta Was this translation helpful? Give feedback.
-
Here's my Renovate config, which has not changed for the past month or so.
I understand that the configuration should not bump to versions which are not the latest (respectLatest is true by default and I don't see anything in the config setting it to false), plus the base config sets ignoreUnstable to true, too.
Yet, renovate bumped dependency Husky to an unstable version having the
next
tag in this PR nearform/titus#640.Husky's latest is 4.x, next is 5.x.
Why did Renovate upgrade to the next tag?
Beta Was this translation helpful? Give feedback.
All reactions