Bump the dependencies group with 4 updates

[dependabot]

Bumps the dependencies group with 4 updates: com.google.guava:guava, org.pitest:pitest-maven, org.junit.jupiter:junit-jupiter and org.assertj:assertj-core.

Updates com.google.guava:guava from 33.3.1-jre to 33.4.0-jre

Release notes

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

33.4.0

Maven

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>33.4.0-jre</version>
  <!-- or, for Android: -->
  <version>33.4.0-android</version>
</dependency>

Jar files

• 33.4.0-jre.jar
• 33.4.0-android.jar

Guava requires one runtime dependency, which you can download here:

• failureaccess-1.0.1.jar

Javadoc

• 33.4.0-jre
• 33.4.0-android

JDiff

• 33.4.0-jre vs. 33.3.1-jre
• 33.4.0-android vs. 33.3.1-android
• 33.4.0-android vs. 33.4.0-jre

Changelog

• Exposed additional Java 8 APIs to Android users. (6082782134, 9b0109c662, 6ace8bc8ea, b650b9fe77, c6c268006c, 984f713d76, f9f3fffb87, cdc225474e)
• base: Deprecated Charsets constants in favor of StandardCharsets. We will not remove the constants, but we recommend using StandardCharsets for consistency. (45e6be2688)
• base: Added ToStringHelper.omitEmptyValues(). (f5ec2ab85c)
• collect: Added an optimized copyOf method to TreeRangeMap. (a46565dd1c)
• collect.testing: Fixed @Require annotations so that features implied by absent features are not also required to be absent. (81be061f85)
• io: Changed ByteSink and CharSink to no longer call flush() in some cases before close(). This is a no-op for well-behaved streams, which internally flush their data as part of closing. However, we have discovered some stream implementations that have overridden close() to do nothing, including not to flush some buffered data. If this change causes problems, the simplest fix is usually to change the close() override to at least call flush(). (6ace8bc8ea)
• net: Added HttpHeaders.ALT_SVC and MediaType.CBOR. (503ba429f9, 7c0bf0892d)

Commits

• See full diff in compare view

Updates org.pitest:pitest-maven from 1.17.2 to 1.17.3

Release notes

Sourced from org.pitest:pitest-maven's releases.

1.17.3

• #1369 Dry Run Support

Maven users can now gather coverage information and generate mutants, but skip the mutant analysis stage by running setting the 'pit.dryRun' flag to true.

Commits

• 175105c Merge pull request #1369 from hcoles/feature/dry_run_support
• 5a41bf9 make mutants available to history coverage limit
• 10bc017 remove duplication parsing booleans
• d32d900 introduce dry run mode
• 116ef37 update readme for 1.17.2
• See full diff in compare view

Updates org.junit.jupiter:junit-jupiter from 5.11.3 to 5.11.4

Release notes

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

JUnit 5.11.4 = Platform 1.11.4 + Jupiter 5.11.4 + Vintage 5.11.4

See Release Notes.

Full Changelog: junit-team/junit5@r5.11.3...r5.11.4

Commits

• 6430ba4 Release 5.11.4
• d093121 Finalize 5.11.4 release notes
• 0444353 Fix Maven integration tests on JDK 24
• b5c7f4e Move #4153 to 5.11.4 release notes
• b20c4e2 Ensure the XMLStreamWriter is closed after use
• 6376f0a Configure Git username and email
• 2b485c4 Set reference repo URI
• 500b5a0 Inject username and password via new DSL
• d671961 Update plugin gitPublish to v5
• 3d11279 Add JAVA_25 to JRE enum
• Additional commits viewable in compare view

Updates org.assertj:assertj-core from 3.26.3 to 3.27.0

Release notes

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

v3.27.0

🚫 Deprecated

Core

• Deprecate ClassBasedNavigableIterableAssert and ClassBasedNavigableListAssert #3529

✨ New Features

Core

• Add actual() to access the object under test #3489
• Add isCompletedWithValueMatchingWithin to CompletableFuture assertions #3506
• Add completesExceptionallyWithin to CompletableFuture assertions #3597
• Add inBinary to CharSequence assertions #3600
• Support for Assertions.byLessThan(Duration) and Assertions.within(Duration) #3486
• Add standard representation for CharSequence #3617
• Add predicate descriptions overloads to anyMatch and noneMatch #3639
• Add doesNotMatch(Predicate) #3684
• Add usingEquals accepting a BiPredicate and an optional description to provide a custom comparison in assertions #3678

Guava

• Add isNotEmpty to Table assertions #3559

🐛 Bug Fixes

Core

• Recursive assertion hasNoNullFields throws NPE with fields of anonymous and local types #3534
• Fix incorrect mutation of actualElementsGroupedByHashCode in recursive comparison
• Recursive comparison ignoringFields not working properly with maps #2988
• Custom representation ignored when describing expected items not in the actual list #3646
• hasFieldOrPropertyWithValue swallows exceptions thrown by getters, and reports non-existent property instead #3563
• satisfies() with nested assertions obscures stack trace #2542

⚡ Improvements

Core

• Report all failing conditions when using satisfies(allOf(Condition...)) #3537
• Fix Unicode escapes in inUnicode() Javadoc
• Show error differences if values were compared with equals in recursive comparison #3209
• Propagate common basetype for extracting(Function...) #3673
• Add throwable stacktrace to ShouldNotContainCharSequence
• Remove unused code and other minor cleanup #3683
• Simplify comparison strategy isLessThan and isLessThanOrEqualTo in AbstractComparisonStrategy #3694
• Update AbstractCharSequenceAssert.java reference #3700
• Include stack trace of internal errors in all/any satisfy assertions

... (truncated)

Commits

• 74a8a44 [maven-release-plugin] prepare release assertj-build-3.27.0
• ba36228 Bump version to prepare 3.27.0 version
• f4d9c8f Bump version to prepare 3.27.0 version
• 6d15943 chore(deps-dev): bump org.hibernate.orm:hibernate-core from 6.6.3.Final to 6....
• e1b0a4e Custom Equality (BiPredicate) Comparator - resolves #3678
• d92ba37 Quality Improvements (#3697)
• 36e63c3 Add isNotEmpty to Table assertions (#3559)
• de48db6 chore(deps): bump com.google.guava:guava from 33.3.1-jre to 33.4.0-jre (#3705)
• b04f8a3 chore(deps): bump byte-buddy.version from 1.15.10 to 1.15.11 (#3703)
• 6500d22 chore(deps): bump junit-jupiter.version from 5.11.3 to 5.11.4 (#3702)
• 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

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report generated by PITest - https://pitest.org - if there are surviving mutants, please check the line comments under 'Files changed', or the full report under the 'CI / pitest' check below this comment.