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:
4.1
->4.10.3
Release Notes
gradle/gradle
v4.10.3
: 4.10.3This bug-fix release contains 3 changes to Gradle 4.10.2:
It also incorporates all fixes to 4.10.1 and 4.10.2.
We recommend that you use Gradle 4.10.3 over 4.10, 4.10.1 and 4.10.2.
Upgrade Instructions
Switch your build to use Gradle 4.10.3 by updating your wrapper properties:
./gradlew wrapper --gradle-version=4.10.3
Standalone downloads are available at https://gradle.org/install.
Reporting Problems
If you find a problem with Gradle 4.10.3, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.
v4.10.2
: 4.10.2This bug-fix release contains 3 changes to Gradle 4.10.1:
AttributeDisambiguationRule
contains null entry #6747We recommend that you use Gradle 4.10.2 over 4.10.1 or 4.10.
Upgrade Instructions
Switch your build to use Gradle 4.10.2 by updating your wrapper properties:
./gradlew wrapper --gradle-version=4.10.2
Standalone downloads are available at https://gradle.org/install.
Reporting Problems
If you find a problem with Gradle 4.10.2, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.
v4.10.1
: 4.10.1This bug-fix release addresses 6 regressions in Gradle 4.10:
tasks.withType(ScalaCompile::class.java).configureEach
fails on multi-project builds.In addition, the Gradle Kotlin DSL has been updated to 1.0 RC6, see the release notes for the list of included fixes.
Upgrade Instructions
Switch your build to use Gradle 4.10.1 by updating your wrapper properties:
./gradlew wrapper --gradle-version=4.10.1
Standalone downloads are available at https://gradle.org/install.
Reporting Problems
If you find a problem with Gradle 4.10.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.
v4.8.1
: 4.8.1This bug-fix release addresses 6 regressions in Gradle 4.8:
artifactory
andbintray
publishing plugins.ConcurrentModificationException
whenproject.tasks.withType()
is used.SourceSet
to override the compile tasks' destination directory.dependencySubstitution
andfailOnVersionConflict
.Upgrade Instructions
Switch your build to use Gradle 4.8.1 by updating your wrapper properties:
./gradlew wrapper --gradle-version=4.8.1
Standalone downloads are available at https://gradle.org/install.
Reporting Problems
If you find a problem with Gradle 4.8.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.
v4.5.1
: 4.5.1This bug-fix release addresses 3 regressions in Gradle 4.5.
Changes in dependency management caused a regression in 4.5 where in some rare cases a dependency could be imported into a different scope than the one declared.
Starting in 4.5, the build cache configuration is shared between builds part of a composite build.
NullPointerException
could be observed if the parent build finished before the different composites. This lifecycle issue has now been resolved.A regression in Eclipse project generation caused a sub-project to be added as a dependency to itself, resulting in an error when opening the project in Eclipse.
For the full list of fixed issues, see the 4.5.1 GitHub milestone.
Upgrade Instructions
Switch your build to use Gradle 4.5.1 by updating your wrapper properties:
./gradlew wrapper --gradle-version=4.5.1
Standalone downloads are available at https://gradle.org/install.
Reporting Problems
If you find a problem with Gradle 4.5.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.
v4.4.1
: 4.4.1This bug-fix release addresses 3 regressions in Gradle 4.4.
We started shipping JGit 4.5.3.201708160445-r in Gradle 4.4. Some of the non-shaded JGit resources leaked into the
gradleApi()
dependency and caused problems in some builds. We now shade all of JGit's resources.Some builds using Kotlin DSL had problems applying the build-scan plugin in Gradle 4.4. We've updated to kotlin-dsl 0.13.2.
Gradle 4.4 contained changes to internal APIs that broke the popular Nebula dependency lock plugin. This release restores binary compatibility for that plugin. Internal APIs are subject to change, although we try to be mindful of the impact of every change in each Gradle release. If particular internal APIs are useful, please open an issue describing your use case, so we can judge where our public APIs are lacking.
For the full list of fixed issues, see the 4.4.1 GitHub milestone.
Upgrade Instructions
Switch your build to use Gradle 4.4.1 by updating your wrapper properties:
./gradlew wrapper --gradle-version=4.4.1
Standalone downloads are available at https://gradle.org/install.
Reporting Problems
If you find a problem with Gradle 4.4.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.
v4.3.1
: 4.3.1This bug-fix release addresses 3 regressions in Gradle 4.3.
Gradle 4.3 introduced an change where an error in resolving a module from one repository would prevent Gradle from searching for that same module in subsequent repositories.
However, the change to abort searching repositories on all unrecognized errors proved to be too aggressive. With 4.3.1, only repository timeout errors will prevent Gradle from searching for a module in a subsequent repository.
Moreover, the connection and socket timeouts for HTTP/HTTPS requests have been increased to 30 seconds.
This version of Gradle also removes an overload of
TaskInputs.property
which caused statically compiled plugin code to use the wrong method when callingTaskInputs.property(..., null)
.Finally, when using
--scan
the build scan plugin is applied before other plugins to avoid rendering a warning message.For the full list of fixed issues, see the GitHub milestone.
Upgrade Instructions
Switch your build to use Gradle 4.3.1 by updating your wrapper properties:
./gradlew wrapper --gradle-version=4.3.1
Standalone downloads are available at https://gradle.org/install.
Reporting Problems
If you find a problem with Gradle 4.3.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.
v4.2.1
: 4.2.1This bug-fix release addresses a regression in 4.2, which caused Android instrumented tests to fail. It also improves Java 9 compatibility and clarifies a few deprecation warnings. We recommend that all Gradle 4.2 users upgrade to 4.2.1
For the full list of fixed issues, see the GitHub milestone.
Upgrade Instructions
Switch your build to use Gradle 4.2.1 by updating your wrapper properties:
./gradlew wrapper --gradle-version=4.2.1
Standalone downloads are available at https://gradle.org/install.
Reporting Problems
If you find a problem with Gradle 4.2.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.
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 has been generated by Mend Renovate. View repository job log here.