Quick question about multi-repo setup: • there is example how to share build logic: https://docs.gradle.org/current/samples/sample_publishing_convention_plugins.html • there is also example regarding version catalog: https://docs.gradle.org/current/userguide/platforms.html Is there any recommendation how to combine those two? Should i read local version catalog when applying plugins and dependencies in my convention plugin? Should they be hardcoded in plugin and I should upgrade version of whole plugin and just have version catalog inside my convention plugins repo? Should I let each repo to decide about catalogs or have settings convention plugin to manage those? I assume that there are multiple paths there but probably there was some intent behind those two features and expected typical scenarios how they would interact with each other.

That highly depends on what you want, whether you want the consumer of the plugin to control the versions or not. For example also depends on whether you publish the convention plugin and use it in multiple builds, or just have it as included build so anyway control all versions together in one build.