I'm a big fan of renovate, so I think its a good idea, but I also don't touch core, so have no idea what the impact would be.
On Mon, Jul 18, 2022 at 1:19 PM Alexander Brandes <[email protected]> wrote: > > Small ammandment: The semantic commit messages on the PoC can be turned off, > but are picked up, because recent (my) commits use them. > > On Monday, 18 July 2022 at 22:15:32 UTC+2 Alexander Brandes wrote: >> >> Hey everyone, >> >> dependabot does a good job at handling single artifacts, but it does a bad >> to no job handling modules of monorepos, see babel -cli, -core, -env, etc. >> for example. >> >> This typically leads me to moving several submodule dependency update PRs >> into a single PR, before reviewing, considering updating one part of a >> dependency without the other often doesn't work out well. >> See #6878 and #6879 landing in #6877 for such a case. >> This is just one example, there are more dependencies that fall into this >> category. >> >> I create a PoC of using renovate over dependabot on core available on >> https://github.com/NotMyFault/jenkins-renovate-poc >> renovate is very well able to create these kinds of "merged" PRs for >> submodules of a dependency, see #4 for example. >> >> For the reasons outlined above, I'd like to see renovate to handle >> dependency updates in core in the future. >> >> Kind regards >> Alex > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/456baae8-e49f-4d87-8d3e-0038257ea5d4n%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuusFce4CdvXeoxb6Hck_t2kiOs77%3DoE5Hz8J6H%2BM0ZxsA%40mail.gmail.com.
