From 91b8d34dbff84839f0fa1e64aec8a162c2c248d9 Mon Sep 17 00:00:00 2001 From: Jonathan Leitschuh Date: Wed, 12 Feb 2020 13:59:11 -0500 Subject: [PATCH] Add explanation of what to do if in problematic version range Co-Authored-By: Paul Merlin --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8943ef8..62731c7 100644 --- a/README.md +++ b/README.md @@ -100,7 +100,7 @@ Regardless of what you find, we still kindly request that you reach out to us an if your `gradle-wrapper.jar` was generated by Gradle 3.3 to 4.0, the check will fail. This is because these `gradle-wrapper.jar` versions were dynamically generated by Gradle in a non-reproducible manner. As such, it's not possible to verify the `gradle-wrapper.jar` for those versions are legitimate using a hash comparison. - +If the Gradle version in use is out of this range it is possible that your Wrapper JAR is out of sync. To fix this run `./gradlew wrapper`. If the Gradle version in use is in the problematic range, you should consider upgrading. ## Resources To learn more about verifying the Gradle Wrapper JAR locally, see our