Unexpected behaviour of packageRules.matchFileNames #30636
-
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.GitLab, Renovate v38.20.1 Please tell us more about your question or problemI have the following configuration in place:
What I expect is that Renovate will only update I've noticed that Im getting an MR from Renovate which contains an update in Is this the expected behaviour or have I got something wrong in my configuration? Logs (if relevant)Logs
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
You've got something wrong. A package rule with only "match" elements does nothing. If your goal is to disable certain dependencies or updates then you need at least one rule with enabled=false in order to disable things. The default behavior of renovate is to update everything. Look at any package rules in docs or this repo for examples |
Beta Was this translation helpful? Give feedback.
You've got something wrong. A package rule with only "match" elements does nothing. If your goal is to disable certain dependencies or updates then you need at least one rule with enabled=false in order to disable things. The default behavior of renovate is to update everything. Look at any package rules in docs or this repo for examples