Bump org.assertj:assertj-core from 3.25.1 to 3.25.2

[dependabot[bot]]

Bumps org.assertj:assertj-core from 3.25.1 to 3.25.2.

Release notes

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

v3.25.2

:bug: Bug Fixes

• Fix unresolvable Javadoc stylesheet URLs, simplify configuration #3324

Core

• Fix missing configuration for MatcherAssert soft assertions
• Make deprecation notice visible in AbstractAssert#asList #3327
• Recursive comparison uses equals on root object when useOverriddenEquals is enabled #3320
• satisfiesExactlyInAnyOrder fails if actual overrides equals #3339
• Avoid calling actual.hashCode() and expected.hashCode() in DualValue #3340
• Recursive comparison checks for existence of fields in types that parameterize nested unordered iterables #3332

:hammer: Dependency Upgrades

• Upgrade to EqualsVerifier 3.15.6 #3329
• Upgrade to Maven Surefire Plugin 3.2.5 #3328
• Upgrade to Spotless Maven Plugin 2.43.0 #3345

:heart: Contributors

Thanks to all the contributors who worked on this release:

@​manusa @​davidboden

Commits

• 96ef63e [maven-release-plugin] prepare release assertj-build-3.25.2
• abdb210 chore(deps): bump com.diffplug.spotless:spotless-maven-plugin from 2.41.1 to ...
• 3132090 Recursive comparison: only check the compared fields existence at the root le...
• e9ebcc2 DualValue hash code is not computed properly because it calls actual.hashCode...
• d51cfd9 Remove elements by reference in assertSatisfiesExactlyInAnyOrder
• 7f786bd The recursive comparison should never use equals on root objects since it def...
• e0f4542 chore(deps-dev): bump nl.jqno.equalsverifier:equalsverifier from 3.15.5 to 3....
• 19b9b3d chore(deps): bump org.apache.maven.plugins:maven-surefire-plugin from 3.2.3 t...
• 470c1ec doc: deprecation notice visible in AbstractAssert#asList (#3327)
• 0521edf Fix missing configuration for MatcherAssert soft assertions
• 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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (72cc7d9) 19.69% compared to head (08c8953) 19.69%.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #513 +/- ## ======================================= Coverage 19.69% 19.69% ======================================= Files 115 115 Lines 3966 3966 Branches 409 409 ======================================= Hits 781 781 Misses 3150 3150 Partials 35 35 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[github-actions[bot]]

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either: 1. Register at [Qodana Cloud](https://qodana.cloud/) and [configure the action](https://github.com/jetbrains/qodana-action#qodana-cloud) 2. Use [GitHub Code Scanning with Qodana](https://github.com/jetbrains/qodana-action#github-code-scanning) 3. Host [Qodana report at GitHub Pages](https://github.com/JetBrains/qodana-action/blob/3a8e25f5caad8d8b01c1435f1ef7b19fe8b039a0/README.md#github-pages) 4. Inspect and use `qodana.sarif.json` (see [the Qodana SARIF format](https://www.jetbrains.com/help/qodana/qodana-sarif-output.html#Report+structure) for details) To get `*.log` files or any other Qodana artifacts, run the action with `upload-result` option set to `true`, so that the action will upload the files as the job artifacts: ```yaml - name: 'Qodana Scan' uses: JetBrains/qodana-action@v2023.3.1 with: upload-result: true ```

Contact Qodana team

Contact us at [qodana-support@jetbrains.com](mailto:qodana-support@jetbrains.com) - Or via our issue tracker: https://jb.gg/qodana-issue - Or share your feedback: https://jb.gg/qodana-discussions