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:
8.5
->8.10.2
0.8.9
->0.8.12
5.10.2
->5.11.1
5.10.2
->5.11.1
3.39.0
->3.55.0
2.10.1
->2.11.0
33.0.0-jre
->33.3.1-jre
3.25.2
->3.25.5
3.25.2
->3.25.5
1.4.0
->1.4.4
1.4.0
->1.4.4
3.4.0
->3.4.3
3.2.2
->3.3.4
6.24.0
->6.25.0
Release Notes
gradle/gradle (gradle)
v8.10.2
Compare Source
v8.10.1
Compare Source
v8.10
Compare Source
v8.9
Compare Source
v8.8
: 8.8Compare Source
The Gradle team is excited to announce Gradle 8.8.
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Björn Kautler,
Denes Daniel,
Fabian Windheuser,
Hélio Fernandes Sebastião,
Jay Wei,
jhrom,
jwp345,
Jörgen Andersson,
Kirill Gavrilov,
MajesticMagikarpKing,
Maksim Lazeba,
Philip Wedemann,
Robert Elliot,
Róbert Papp,
Stefan M.,
Tibor Vyletel,
Tony Robalik,
Valentin Kulesh,
Yanming Zhou,
김용후
Upgrade instructions
Switch your build to use Gradle 8.8 by updating your wrapper:
See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.
For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.
Reporting problems
If you find a problem with this release, 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.
We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.
v8.7
Compare Source
v8.6
Compare Source
jacoco/jacoco (jacoco)
v0.8.12
: 0.8.12New Features
Fixed bugs
Non-functional Changes
v0.8.11
: 0.8.11New Features
Fixed bugs
VerifyError
when the last local variable of method parameters is overridden in the method body to store a value of type long or double (GitHub #893).Non-functional Changes
v0.8.10
: 0.8.10Fixed bugs
SecurityManager
outside of itscodeBase
(GitHub #1425).protocolbuffers/protobuf (com.google.protobuf:protobuf-java-util)
v3.25.5
v3.25.4
v3.25.3
google/truth (com.google.truth.extensions:truth-proto-extension)
v1.4.4
@NullMarked
annotation from individual classes up to the package to avoid a warning under--release 8
. (e107aea
)matches
to conditionally suggest usingcontainsMatch
. (7e9fc7a
)v1.4.3
: 1.4.3Known Issue for at least some builds targeting Java 8, fixed in 1.4.4: "unknown enum constant ElementType.MODULE": https://github.com/google/truth/issues/1320. As far as we know, this is only a warning, so it should cause practical problems only if you use
-Werror
or you perform reflection on@NullMarked
under a Java 8 runtime.ee680cb
)Subject.Factory
methods for Java 8 types. We won't remove them, but you can simplify your code by migrating off them: Just replaceassertAbout(foos()).that(foo)
withassertThat(foo)
(orabout(foos()).that(foo)
withthat(foo)
). (59e7a50
)v1.4.2
: 1.4.2This release is the final step of copying all our methods from
Truth8
toTruth
. If you have not already migrated your usages fromTruth8
toTruth
, you may see build errors:In most cases, you can migrate your whole project mechanically:
git grep -l Truth8 | xargs perl -pi -e 's/\bTruth8\b/Truth/g;'
. (You can make that change before upgrading to Truth 1.4.2 or as part of the same commit.)If you instead need to migrate your project incrementally (for example, because it is very large), you may want to upgrade your version of Truth incrementally, too, following our instructions for 1.3.0 and 1.4.0.
For help
Please feel welcome to open an issue to report problems or request help.
Changelog
Truth.assertThat(Stream)
andTruth.assertThat(Optional)
. This can create build errors, which you can fix by replacing all your references toTruth8
with references toTruth
. (45782bd
)v1.4.1
: 1.4.1This release deprecates
Truth8
.All its methods have become available on the main
Truth
class. In most cases, you can migrate your whole project mechanically:git grep -l Truth8 | xargs perl -pi -e 's/\bTruth8\b/Truth/g;'
While we do not plan to delete
Truth8
, we recommend migrating off it, at least if you static importassertThat
: If you do not migrate, such static imports will become ambiguous in Truth 1.4.2, breaking your build.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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.