Automerge automerging major updates when it shouldn't #28747
Unanswered
naanlizard
asked this question in
Request Help
Replies: 2 comments
-
|
Beta Was this translation helpful? Give feedback.
0 replies
-
That was quick, thank you. I'll try removing it
…On Tue, Apr 30, 2024 at 00:33 Rhys Arkins ***@***.***> wrote:
RENOVATE_AUTOMERGE: true is a mistake. By setting that you are turning on
automerge for all updates
—
Reply to this email directly, view it on GitHub
<#28747 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABV4BWPDGFEO2EEHUFJIMLTY74NJNAVCNFSM6AAAAABG7P2RWCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TENZQGA4TO>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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
-
What would you like help with?
I would like help with my configuration
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 problem
I've got a private gitlab instance (self hosted) and am using renovate-runner to update an old project.
I told renovate-runner to not automerge major versions (I think) with the renovate.json in the repository, below, and I'm also including the renovate-runner repo's .gitlab-ci.yml.
It merges minor stuff, which is good, but also major patches like this
^5.0.3
->^6.0.0
It also shows some MRs as "major" in the title, but others not. All of them have "Automerge: enabled" in the description
I assume I'm doing something wrong, but I'm unsure what. Would love a hand
{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"config:best-practices"
],
"packageRules": [
{
"matchUpdateTypes": ["minor", "patch", "pin", "digest"],
"automerge": true
}
]
}
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions