v7.2.4

• Core alignment will add rejections in the substitution rule rather than in an aligned platform rule, and will add relevant rejections to all direct dependencies. This second part is done to ensure that rejections are not only added after resolution of direct dependencies, if the dependency is also brought in transitively.

• Gradle 5.5.1

v7.2.3

Always create a new group matcher and add exception details (#103)

* Always create a new group matcher and add exception details

* remove matcher reset since we always create a new group matcher

v7.0.14

Always create a group matcher to prevent thread safety issues

v7.2.2

Update to AlignedPlatformRules:

• Provide more information on versions rejected via substitution rule and alignment rules interacting
• Rejections and reasons from above are additive

v7.2.1

Update to AlignedPlatformRules:

• AlignedPlatformRule honors align rule excludes and includes
• Transitive dependencies show rejected constraints

v7.2.0

• Introduce AlignedPlatformRule for substitution and alignment interaction
• plugin-plugin 11.2.15

v7.1.0

Enable cache for AlignedPlatformMetadataRule. This was disabled when gradle/gradle#8311 was detected

v7.0.13

AlignRule - catch errors with align range and provide exception with …

v7.0.12

plugin-plugin 11.2.12

v7.0.11

Make AlignedPlatformMetadataRule open class

heads up @sghill