RenovateBot unexpectedly modifies values set by Release Please

[suztomo]

trafficstars

Example https://github.com/googleapis/google-cloud-java/pull/8237

It causes conflicts in pull requests (https://github.com/googleapis/google-cloud-java/pull/8340):

@ddixit14 Would you evaluate whether this is a problem or not?

[ddixit14]

@suztomo I think this is because these artifacts have already been released on maven central, and renovate bot is just updating them with the latest version. And this process is messing up with release-please attempt to update the versions on release. This is mainly due to the lag google-cloud-java has in doing a release for the artifact (because we are not releasing in shadow mode). Once we start releasing from monorepo, such conflicts should not occur (hope so). What do you think?

[suztomo]

@ddixit14 That's good reasoning. But if RenovateBot is making conflicts in this repository and our versions become inconsistent as per Release Please, we cannot start releasing artifacts from this repository.

Can you configure renovate.json to limit the scope of RenovateBot into only java-shared-config and java-shared-dependencies?

[suztomo]

@ddixit14 As discussed, there should be RenovateBot's option to enable "create pull requests only when corresponding item is checked in Dependency Dashboard". Find the option.

If you don't find option and taking 30 mins or more, I'll search it.

[suztomo]

Now we have #7649