Bump the minor-and-patch-dependencies group with 4 updates

[dependabot]

Bumps the minor-and-patch-dependencies group with 4 updates: org.junit.jupiter:junit-jupiter, org.assertj:assertj-core, com.google.truth:truth and org.junit.vintage:junit-vintage-engine.

Updates org.junit.jupiter:junit-jupiter from 5.10.1 to 5.10.2

Release notes

Sourced from org.junit.jupiter:junit-jupiter's releases.

JUnit 5.10.2 = Platform 1.10.2 + Jupiter 5.10.2 + Vintage 5.10.2

See Release Notes.

Full Changelog: junit-team/junit5@r5.10.1...r5.10.2

Commits

• 4c0ddda Release 5.10.2
• 463a147 Finalize release notes for 5.10.2
• 43c105a Revert "Apply method predicate before searching type hierarchy"
• 63d464d Revert "Harmonize application of method and field filters in search algorithms"
• 85ec2fc Revert "Apply field predicate before searching type hierarchy"
• 6209006 Update release notes
• 5ee499f Fix CI build
• d919ba7 Namespace user-specific build parameters
• e26cd83 Prepare release notes for 5.10.2
• ec8d428 Include LauncherInterceptor in launcher module declaration
• Additional commits viewable in compare view

Updates org.assertj:assertj-core from 3.25.2 to 3.25.3

Release notes

Sourced from org.assertj:assertj-core's releases.

v.3.25.3

🐛 Bug Fixes

• Lock maven-clean-plugin version for all modules

Core

• Fix a performance regression in the recursive comparison related to FieldLocation #3350
• Don't fail when the recursive comparison checks compared fields in collection elements #3349 (proper fix: #3354)

🔨 Dependency Upgrades

• Upgrade to Flatten Maven Plugin 1.6.0 #3335
• Upgrade to Groovy 4.0.18 #3347
• Upgrade to Hibernate Core 6.4.2.Final #3338
• Upgrade to Maven Surefire Report Plugin 3.2.5 #3330
• Upgrade to PITest Maven 1.15.6 #3348
• Upgrade to SpotBugs Maven Plugin 4.8.3.0 #3336
• Upgrade to advanced-security/maven-dependency-submission-action to 4 #3346

❤️ Contributors

Thanks to all the contributors who worked on this release:

@​ash211

Commits

• cd72df8 [maven-release-plugin] prepare release assertj-build-3.25.3
• c9b3177 fix: missing license
• ae62aca Ignore containers when checking compared fields existence in the recursive co...
• bad16ef chore(deps-dev): bump org.hibernate.orm:hibernate-core from 6.4.2.Final to 6....
• c794057 Fix a performance regression in the recursive comparison related to FieldLoca...
• 9ecb7f4 Lock maven-clean-plugin version for all modules
• d42d40c chore(deps): bump org.pitest:pitest-maven from 1.15.3 to 1.15.6 (#3348)
• 5b32492 chore(deps): bump org.apache.maven.plugins:maven-surefire-report-plugin from ...
• e27cc02 chore(deps): bump org.codehaus.mojo:flatten-maven-plugin from 1.5.0 to 1.6.0 ...
• 9771091 chore(deps): bump com.github.spotbugs:spotbugs-maven-plugin from 4.8.2.0 to 4...
• Additional commits viewable in compare view

Updates com.google.truth:truth from 1.3.0 to 1.4.0

Release notes

Sourced from com.google.truth:truth's releases.

1.4.0

In this release, our assertions on Java 8 types continue to move from the Truth8 class to the main Truth 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

Foo.java:152: error: reference to assertThat is ambiguous
    assertThat(repo.findFileWithName("foo")).isNull();
    ^
  both method assertThat(@org.jspecify.nullness.Nullable Path) in Truth8 and method assertThat(@org.jspecify.nullness.Nullable Path) in Truth match

Simplest upgrade strategy (if you can update all your code atomically in the same commit as the Truth upgrade)

In the same commit:

1. Upgrade Truth to 1.4.0.
2. Replace import static com.google.common.truth.Truth8.assertThat; with import static com.google.common.truth.Truth.assertThat;.
   • If you use Kotlin, replace import com.google.common.truth.Truth8.assertThat with import com.google.common.truth.Truth.assertThat.
3. Replace import com.google.common.truth.Truth8; with import com.google.common.truth.Truth;.
   • again, similarly for Kotlin if needed
4. Replace remaining references to Truth8 with references to Truth.
   • For example, replace Truth8.assertThat(optional).isPresent() with Truth.assertThat(optional).isPresent().

If you're feeling lucky, you can try this one-liner for the code updates:

git grep -l Truth8 | xargs perl -pi -e 's/import static com.google.common.truth.Truth8.assertThat;/import static com.google.common.truth.Truth.assertThat;/g; s/import com.google.common.truth.Truth8.assertThat/import com.google.common.truth.Truth.assertThat/g; s/import com.google.common.truth.Truth8/import com.google.common.truth.Truth/g; s/\bTruth8[.]/Truth./g;'

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 some Truth.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:

1. Make the optional changes discussed in the release notes for 1.3.0.
2. For any remaining calls to Truth8.assertThat, change them to avoid static import.
   • That is, replace assertThat(optional).isPresent() with Truth8.assertThat(optional).isPresent().
3. Upgrade Truth to 1.4.0.
4. Optionally replace references to Truth8 with references to Truth (including restoring static imports if desired), as discussed in section about the simple upgrade strategy above.

Optional additional changes

• If you use assertWithMessage(...).about(intStreams()).that(...), expect.about(optionalLongs()).that(...), or similar, you can remove your call to about. This change will never be necessary; it is just a simplification.
  • This is similar to a previous optional change from 1.3.0, except that 1.3.0 solved this problem for streams and optionals, whereas 1.4.0 solves it for the other Truth8 types.

For help

... (truncated)

Commits

• 2e8e488 Set version number for truth-parent to 1.4.0.
• 1f81827 Copy Truth8.assertThat overloads for Path and OptionalLong to the main ...
• 9be8e77 Copy remaining Truth8.assertThat overloads to the main Truth class—except...
• b02a658 Migrate most usages of Truth8.assertThat to equivalent usages of `Truth.ass...
• 0999369 Automated Code Change
• 7c65fc6 Make it possible to write expect.that(optionalInt).isPresent(), `assertWith...
• 87b371d Bump styfle/cancel-workflow-action from 0.12.0 to 0.12.1
• See full diff in compare view

Updates org.junit.vintage:junit-vintage-engine from 5.10.1 to 5.10.2

Release notes

Sourced from org.junit.vintage:junit-vintage-engine's releases.

JUnit 5.10.2 = Platform 1.10.2 + Jupiter 5.10.2 + Vintage 5.10.2

See Release Notes.

Full Changelog: junit-team/junit5@r5.10.1...r5.10.2

Commits

• 4c0ddda Release 5.10.2
• 463a147 Finalize release notes for 5.10.2
• 43c105a Revert "Apply method predicate before searching type hierarchy"
• 63d464d Revert "Harmonize application of method and field filters in search algorithms"
• 85ec2fc Revert "Apply field predicate before searching type hierarchy"
• 6209006 Update release notes
• 5ee499f Fix CI build
• d919ba7 Namespace user-specific build parameters
• e26cd83 Prepare release notes for 5.10.2
• ec8d428 Include LauncherInterceptor in launcher module declaration
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions