Question: how does Renovate treat 0.x -> 0.y updates by default? #30925
-
What would you like help with?Other How are you running Renovate?None If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.No response Please tell us more about your question or problemHello, Renovate team! How does Renovate treat 0.x -> 0.y updates by default? Are they detected as major, or minor? I'm asking because I believe the convention is to treat them as major (since v0 is changing rapidly and things break often), but in this example Renovate treats them as minor: In case they are treated as minor, is there a config that could tweak that? Thanks! Logs (if relevant)No response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
A major update is one where the major version changes. 0.x -> 0.y is not a major update, but it may be a breaking update. Renovate treats v0 -> v0 updates as minor because that's what they are. You should treat them as potentially breaking though. If you want to do things like exclude v0 updates from a non-major group then you can use the |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much, @rarkins! |
Beta Was this translation helpful? Give feedback.
A major update is one where the major version changes. 0.x -> 0.y is not a major update, but it may be a breaking update. Renovate treats v0 -> v0 updates as minor because that's what they are. You should treat them as potentially breaking though. If you want to do things like exclude v0 updates from a non-major group then you can use the
allowedVersionsconfig inpackageRules.