Consolidated dependency update PRs? #9228
Replies: 1 comment 5 replies
-
Renovate supports the same thing (with the possibility to either use existing presets or fine-tune the handling of multiple dependencies): https://docs.renovatebot.com/presets-group/ The question is whether we'd like to have this for all dependencies or for only for a specific subset. Any thoughts? |
Beta Was this translation helpful? Give feedback.
-
|
Maybe start with grouping all the maven-related ones together since they seem to be upgraded more frequently than the core dependencies? |
Beta Was this translation helpful? Give feedback.
-
|
That's what I did in #9238. See #9240 for an example PR created with the new configuration. |
Beta Was this translation helpful? Give feedback.
-
|
Nice! That works. What if we did one across all the dependencies or do you think that would become unmanageable? |
Beta Was this translation helpful? Give feedback.
-
|
I don't think this would be a substantial improvement. Instead of 10 individual PRs, you'd get a single, permanently updated PR with 10 changes until it's going to be merged. If you want to reduce the number of notifications of , maybe customizing the watch settings would make sense? Issues, discussions, security alerts sounds like a useful combination if you want to largely ignore PRs. 
|
Beta Was this translation helpful? Give feedback.
-
|
Yea thanks. I’m going to adjust those. I wish there was a way to ignore PRs with specific tags. I’m still interested in new functionality and bug fixes but all the dependency ones are noisy. Thank you for the suggestions |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I know with Dependabot, you can group dependency updates across multiple dependencies to a single PR. Can we do something similar with Renovate to have a single dependency PR per branch we are maintaining? Or, even better, a way to pin specific major versions we are tracking per branch and let the other Maven-dependencies (for example) be updated across all branches.
I'm primarily asking to cut down on the amount of notifications from both the
dropwizardandmetricsrepositories.Beta Was this translation helpful? Give feedback.
All reactions