maxMajorIncrement does not work #40692
Unanswered
sjedlick
asked this question in
Request Help
Replies: 1 comment
-
|
Hi there, Please help this Discussion progress by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible. Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues. Please follow these steps:
If you need help with running Renovate on your minimal reproduction repository, please refer to our Running Renovate guide. The Renovate team |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
Self-hosted Renovate
Which platform you running Renovate on?
GitLab (.com or self-hosted)
Which version of Renovate are you using?
42.92.5
Please tell us more about your question or problem
I see the following line in the log.
DEBUG: Skipping <packagename> because major increment 8981 exceeds maxMajorIncrement 500
The <packagename> is referenced in my .gitlab-ci.yml
To avoid this I configured the following in my renovate.json5 :
But unfortunately this does not work.
Are there any hints ?
Thank you and best regards
Swen
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions