v1.3.1
Fixes
[#28] Add support for projects using Gradle's configuration cache
Why version change to 1.3.1 from 1.2.0?
For the last release (1.2.0), @PatilShreyas pushed a tag with the name 1.3.0 directly and after knowing about this mistake, he deleted it instantly, but the CI job was already done causing the release of the CLI NPM artifact. So to avoid directly modifying the old release, keeping this release name as v1.3.1.
Full Changelog: v1.2.0...v1.3.1