Add explanation of what to do if in problematic version range

Co-Authored-By: Paul Merlin <paul@nosphere.org>
This commit is contained in:
Jonathan Leitschuh 2020-02-12 13:59:11 -05:00 committed by GitHub
parent aea0bb6ee7
commit 91b8d34dbf
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -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. 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. 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. 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 ## Resources
To learn more about verifying the Gradle Wrapper JAR locally, see our To learn more about verifying the Gradle Wrapper JAR locally, see our