From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Screenshot 2025-06-20 at 13.58.44.png

Screenshot 2025-06-20 at 13.58.50.png

anyone know how to diagnose “downgrades” in dependency resolution? I have this dep that’s being `Forced` down from 2.38.0 to 2.36.0 (as per a build scan) and I don’t know why. Is there a way to see more info about why it is forced? I can’t see any usages of `resolutionStrategy.force` in any of the buildscripts or plugins at least.

solved: there was a plugin adding a dependency using `dependencies.enforcedPlatform(` with a bom