fix(deps): update dependency com.google.truth:truth to v1.4.2 #138
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:
1.3.0
->1.4.2
Release Notes
google/truth (com.google.truth:truth)
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.v1.4.0
: 1.4.0In this release, our assertions on Java 8 types continue to move from the
Truth8
class to the mainTruth
class. This change should not break compatibility for any supported JDK or Android version, even users who test under old versions of Android without API desugaring. Additionally, we will never break binary compatibility, though some users will have to make changes to their source code in order for it to compile against newer versions.This release is likely to lead to more build failures than 1.3.0 did. However, those failures should be straightforward to fix.
Example build failure
Simplest upgrade strategy (if you can update all your code atomically in the same commit as the Truth upgrade)
In the same commit:
import static com.google.common.truth.Truth8.assertThat;
withimport static com.google.common.truth.Truth.assertThat;
.import com.google.common.truth.Truth8.assertThat
withimport com.google.common.truth.Truth.assertThat
.import com.google.common.truth.Truth8;
withimport com.google.common.truth.Truth;
.Truth8
with references toTruth
.Truth8.assertThat(optional).isPresent()
withTruth.assertThat(optional).isPresent()
.If you're feeling lucky, you can try this one-liner for the code updates:
In most cases, that can be further simplified to:
After that process, it is possible that you'll still see build errors from ambiguous usages of
assertThat
static imports. If so, you can find a workaround in the section about overload ambiguity in the release notes for 1.3.0. Alternatively, you can wait to upgrade until after a future Truth release, which will eliminate the ambiguity by changing the signatures of someTruth.assertThat
overloads.Incremental upgrade strategy
If you have a very large repo or you have other reasons to prefer to upgrade incrementally, you can use the approach that we used inside Google. Roughly, that approach was:
Truth8.assertThat
, change them to avoid static import.assertThat(optional).isPresent()
withTruth8.assertThat(optional).isPresent()
.Truth8
with references toTruth
(including restoring static imports if desired), as discussed in section about the simple upgrade strategy above.Optional additional changes
assertWithMessage(...).about(intStreams()).that(...)
,expect.about(optionalLongs()).that(...)
, or similar, you can remove your call toabout
. This change will never be necessary; it is just a simplification.streams
andoptionals
, whereas 1.4.0 solves it for the otherTruth8
types.For help
Please feel welcome to open an issue to report problems or request help.
Changelog
Truth8.assertThat
overloads to the mainTruth
class. (9be8e77
,1f81827
)that
overloads to make it possible to write type-specific assertions when using the remaining Java 8 types. (7c65fc6
)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.