v16.19.0

Detect configuration methodCall() use case as a dependency declaration. It will invoke visitAnyObjectDependency rule callback. The logic now even calls the callback when the function cannot be evaluated. It will pass an instance of NotEvaluatedObject with the original AST node instead of evaluated object.

v16.18.0

Detect configuration methodCall() use case as a dependency declaration. It will invoke visitAnyObjectDependency rule callback.

v16.17.1

Fix groovy syntax and API usage to improve compatibility with upcoming Gradle 7.0 and Groovy 3.

NOTE: this release doesn't guarantee full compatibility with Gradle 7. It removes only the first wave of blockers and allows further testing.

v16.17.0

All fixes associated with a violation are applied all or none. This helps in scenarios where one fix can collide with another fix. A violation with a colliding fix will not apply any of its fixes.

v16.16.0

Callbacks providing parsed dependencies will now provide parsed dependency with original declaration preserving GString Expressions. For example: implementation 'group:name:${version}'. Version property will contain ${version}

v16.9.1

Fix a bug when a rule is applying multi-line change which ends with lines with trailing newlines.

v16.9.0

XML reports will now contain packages for each submodule holding a full path to the submodule. Previous releases aggregate all files in a single package with path to the root of the project.

v16.8.1

Fix: bypassed-forces rule works with groovy 2.4.15

v16.8.0

Configuration whether the report task will output all violations or only violations that would be applied during fix stage.

v16.7.2

Bypassed forces rule provides warning for only the affected projects