Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently they are 9 years old. That is quite ancient. It would be good for them to be kept completely up-to-date. This may improve building times on local machines. This will also fix potential security vulnerabilities the current outdated JAR may have. See here for why updating these is recommended.
For obvious security purposes (a jar file has been modified), the command I ran was
./gradlew wrapper --gradle-version 8.7 --distribution-type bin
in Git Bash. You can independently verify the integrity of these files by running this command on your own machine and then using a file comparison tool (like WinMerge for example) to compare the results between this PR and your machine.The updated JAR's integrity can be verified through this as well: https://gradle.org/release-checksums/