microsoft
Use Gradle version catalogs to have a single source of truth for dependency versions
I propose using Gradle's version catalogs to have a single source of truth for the project's dependency versions and also (hopefully) reduce the number of dependabot PRs for the same dependency in the project. This feature should also be supported by gradle 8.9 which this project uses. See https://docs.gradle.org/8.9/userguide/platforms.html
Hey @calebkiage We're already using that to share dependencies between main/java-8/android projects for each package. I don't think we can use it across packages since they have different dependencies (e.g. azure identity authentication provider needs azure core that's not needed in other packages)
Can you provide more information on how you'd use this feature in addition to the current configuration please?
Ah scratch the last comment, I thought we were referring to a dependencies catalog, but eventually clicked on the link. Yes a version catalog would be interesting. We should double check that dependenbot supports it first though.
Dependabot supports version catalogs https://github.com/dependabot/dependabot-core/pull/6249