Hi, at the moment scala-steward is opening a single PR for each dependency update. Scala-steward provides a way of grouping multiple updates into single PR[1]. I was thinking it might be valuable to explore this route. Some benefits I can think of: less noisy, a single approval for the patch/minor updates, less conflicts with multiple PRs opened.
A proposal could be: - Grouping all the patch updates into a single PR. I would expect patch updates to be straightforward and have less chance to break anything in our CI step. - Grouping all the minor updates into a single PR. Is this feasible? How many minor updates break our CI? - Keep all the major updates as separate PRs. There is an high chance that major updates break something. Having them bundled together is not helping the debugging. My main concern is that some dependencies don't strictly follow the semver. We might end up with a bundle of patch updates that are not only semver patches. Any opinion or thought? Is it something is worth exploring? Samuele [1] https://github.com/scala-steward-org/scala-steward/blob/main/docs/repo-specific-configuration.md?plain=1#L68
