v0.59.0

• Report the version a resolution found for a dependency that another resolution failed on, which the failure used to suppress everywhere (#1050, #1052)
• Report the version that actually failed to resolve, rather than the lowest version the build declares for that module, and name it in the plain text report's unresolved section as every other section does (#1043, #1044)
• Collect the partial result of every project under the project that aggregates them, isolated projects included, so a project that exists only to hold a nested include no longer gains a build directory of its own (#1040, #1041, #1051)
• Skip the plugin-contributed marking on a configuration that has already been resolved, which failed the apply of any project that resolved one before the plugin was applied (#1049, #1051)
• Attribute the statuses only where a project has a variant of its own, so a project that publishes through its default configuration is aggregated under isolated projects rather than left out of the report, and its own consumers are no longer served the partial result in place of the artifact they asked for (#1046, #1047, #1051)
• Name the producer's configuration when mirroring an aggregation dependency, so a project named in the build's own dependencyUpdatesAggregation block no longer has its jar read as a partial result (#1048, #1051)
• Document how a change lands and how a release is published, and check on deploy that the version being published matches the release tag (#1042)
• Sort the migration notes into the same alerts the release notes use (#1045)

Important

• A declared version that resolved in one place and failed in another is now reported twice: once with the version found for it, and again as unresolved. A dependency declared without a version doubles the same way, as undeclared and unresolved. The JSON and XML reports count it in each place. A tool reading count as a dependency total, or treating the sections as disjoint, has to allow for the overlap.
• The unresolved section of the plain text report now names the declared version, which a tool parsing that section line by line has to allow.

See Migrating from prior versions.

Tip

Run ./gradlew dependencyUpdates --clean-legacy-partials once to remove the build/dependencyUpdates/partial.json that earlier releases wrote into each project. The clean task removes it from a project that directly or indirectly applies the Base plugin, but a project with no build script has no clean task.