chore(deps): update net.ltgt.gradle:gradle-errorprone-plugin to v4 #131
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.
This PR contains the following updates:
3.1.0
->4.2.0
Release Notes
tbroyer/gradle-errorprone-plugin (net.ltgt.gradle:gradle-errorprone-plugin)
v4.2.0
Handle configurations more lazily
This is in preparation for Gradle 8.14 which will no longer realize all configurations in the
base
plugin, allowing truly lazily-initialized configurations.This change should allow the
javacConfiguration
to only be initialized when JDK 8 is being used, and the variousannotationProcessor
configurations from source sets to only be initialized when needed, e.g. when a compilation tasks for that source set is run (it's likely that thejava
plugin doesn't yet take advantage of this new possibility itself though)v4.1.0
--should-stop=ifError=FLOW
to the compiler; it fixes a few issues in all versions of Error Prone, and the next version will make it mandatory (should have been the case in 2.34 already, but didn't actually apply to the JavaC plugin).v4.0.1
Only assign
options.isFork
if neededThis is a first step in preparation for some changes coming in Gradle 9.
v4.0.0
The
errorprone
configuration can no longer be resolved. It only exists to declare dependencies, i.e. as a dependency scope configuration.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.