Trying to automerge certain deps but reporting "Automerge Disabled by config" #31115
Replies: 6 comments 2 replies
-
|
matchPackagePatterns are deprecated, try again with matchPackageNames instead |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, Get your discussion fixed faster 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:
Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
-
|
Hi @rarkins, I assume my config is probably right and this behaviour is unexpected, given the tag set. I'm going to make a minimal reproduction as requested, but this will have to wait a bit since I'm going on vacation. |
Beta Was this translation helpful? Give feedback.
-
|
I found that automerge only gets enabled if I set the This does not work: I also tested with This works for both packages: I did several tests, deleting both PR and branches on every loop. |
Beta Was this translation helpful? Give feedback.
-
|
I'm sorry, I'm not doing the minimal reproduction. Honestly, I would like to contribute that way but that would take me so much time :S In our setup regexp matching / minimax matching is broken, at least for matchPackageNames. Our full configuration is still the exposed above. Maybe matchUpdateTypes and matchPackageNames in the same package rule are colliding? Anyway, finally we made a package rule to automerge everything about patch updates, but excluding some explicit packages with another rule and works perfectly: Maybe this can help anyone. Thanks anyway and congratulations for this helpful tool. |
Beta Was this translation helpful? Give feedback.
-
|
We've been experiencing the same issue: packageRules using regexes in After spending several days creating a minimal reproduction, I was able to narrow down the problem to our use of the Maybe your problem had the same cause as ours, @spekdrum. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What would you like help with?
I would like help with my configuration
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
BitBucket Server 7.17.13
Please tell us more about your question or problem
I'm running latest version of Renovate from a docker image with npx.
Everything is working but I'm struggling with automerge configuration.
I would like to automerge (PR) AWS sdk patch updates (maven software.amazon.awssdk:*). I'm aware about the need to separate patch branches ("separateMinorPatch": true). But it's not working. A PR is created (but not merged) and in the body says:
Automerge: Disabled by config. Please merge this manually once you are satisfied.I think I read everything in the documentation about automerge. Did some tests and combinations. Maybe there is any configuration conflicting with this feature, I can't see the problem.
This is my global config file (I've put ***** to hide urls):
And this is the renovate.json config file in the repository:
Tried to set
matchPackagePatternswithsoftware.amazon.awssdk:**also, without success.I see in the logs this repo config is taken, but I don't know why automerge is not enabled.
Thank you in advance for your time and assistance.
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions