Right now, we have a variety of ways to source gradle dependencies. Some directly in the relevant build.gradle, some through ext blocks, some flow through Classpaths.groovy, and others through BOM inclusion.
In the spirit of #5115, we should see if we can do better to allow automated tooling to open PRs against this repository.
https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#gradle does specifically point out support for gradle/libs.versions.toml, and so that is something to consider.
Best to look at this after #4693
Right now, we have a variety of ways to source gradle dependencies. Some directly in the relevant build.gradle, some through ext blocks, some flow through Classpaths.groovy, and others through BOM inclusion.
In the spirit of #5115, we should see if we can do better to allow automated tooling to open PRs against this repository.
https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#gradle does specifically point out support for
gradle/libs.versions.toml, and so that is something to consider.Best to look at this after #4693