- Honor the build's log level in the reporters: the console summary prints at the lifecycle level, so
--quietsuppresses it; a skipped report file is logged at the info level; the "use --info for details" hint is dropped when the build already runs at that level; and an unresolved dependency no longer reports a version string as its project url (#278, #388, #726, #844, #1033) - Report a module published only as a snapshot as up to date, rather than as a failure to determine its latest version (#475, #1034)
- Skip the buildscript classpath of a project that declares no repository, which previously reported each of that project's buildscript dependencies as a failure to determine its latest version (#756, #1038)
- Name the projects that declared each version when one coordinate resolves to more than one, so the merged report of a multi-project build no longer prints the same dependency several times with nothing telling the entries apart (#1032, #1035)
- Mark a dependency that only a plugin contributed and name the configuration it came from, so a
jacoco,checkstyleorpmdtool version the build never sets no longer reads as a resolution bug (#1028, #1032, #1036) - Test isolated projects with Gradle 9.7.0-rc-2 (#1037)
Note
The console summary now honors the log level, so a script running the task under --quiet no longer sees it. The report file is still written. Report entries may also carry an indented attribution line naming the projects that declared a divergent version or the configuration a plugin contributed the dependency into, which a tool parsing the plain text report line by line has to skip. See Migrating from prior versions.