build(deps): bump the dependencies group with 10 updates

[dependabot]

Bumps the dependencies group with 10 updates:

Package	From	To
org.junit:junit-bom	5.12.1	5.12.2
com.google.code.gson:gson	2.12.1	2.13.0
commons-io:commons-io	2.18.0	2.19.0
io.swagger.core.v3:swagger-annotations	2.2.29	2.2.30
io.swagger.core.v3:swagger-models	2.2.29	2.2.30
com.graphql-java:graphql-java	22.3	23.0
org.jetbrains.kotlinx:kotlinx-coroutines-core	1.10.1	1.10.2
com.google.guava:guava	33.4.6-jre	33.4.7-jre
com.diffplug.spotless:spotless-maven-plugin	2.44.3	2.44.4
software.amazon.awssdk:bom	2.31.16	2.31.21

Updates org.junit:junit-bom from 5.12.1 to 5.12.2

Release notes

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

JUnit 5.12.2 = Platform 1.12.2 + Jupiter 5.12.2 + Vintage 5.12.2

See Release Notes.

Full Changelog: junit-team/junit-framework@r5.12.1...r5.12.2

Commits

• 0a44659 Release 5.12.2
• 4c7dfdc Finalize 5.12.2 release notes
• 561613e Fix handling of CleanupMode.ON_SUCCESS
• 19d07d2 Add 5.12.2 release notes from template
• 803cbb6 Add build parameter for enabling dry-run mode for test execution
• eb43e62 Back to snapshots for further development
• See full diff in compare view

Updates com.google.code.gson:gson from 2.12.1 to 2.13.0

Release notes

Sourced from com.google.code.gson:gson's releases.

Gson 2.13.0

What's Changed

• A bug in deserializing collections has been fixed. Previously, if you did something like this:

  gson.fromJson(jsonString, new TypeToken<ImmutableList<String>>() {})
  

  then the inferred type would be ImmutableList<String>, but Gson actually gave you an ArrayList<String>. Usually that would lead to an immediate ClassCastException, but in some circumstances the code might sometimes succeed despite the wrong type. Now you will see an exception like this:

  com.google.gson.JsonIOException: Abstract classes can't be instantiated!
  Adjust the R8 configuration or register an InstanceCreator or a TypeAdapter for this type.
  Class name: com.google.common.collect.ImmutableList
  

  because Gson now really is trying to create an ImmutableList through its constructor, but that isn't possible. Either change the requested type (in the TypeToken) to List<String>, or register a TypeAdapter or JsonDeserializer for ImmutableList.

• The internal classes $Gson$Types and $Gson$Preconditions have been renamed to remove the $ characters. Since these are internal classes (as signaled not only by the package name but by the $ characters), client code should not be affected. If your code was depending on these classes then we suggest making a copy of the class (subject to the license) rather than depending on the new names.

Full Changelog: google/gson@gson-parent-2.12.1...gson-parent-2.13.0

Commits

• bfe0fd5 [maven-release-plugin] prepare release gson-parent-2.13.0
• 6ed64ca add multi-catch support to the code base (#2841)
• 0074376 Bump the maven group with 3 updates (#2840)
• 45e5e14 Rename $Gson$Preconditions and $Gson$Types. (#2838)
• c6d4425 Remove obsolete comment in pom.xml (#2835)
• 9afd6f8 Bump the maven group with 10 updates (#2831)
• ad5371e Fix findings that are new with the latest Error Prone. (#2834)
• de190d7 Restructure code to avoid assignment expression warning. (#2833)
• 3d66847 Bump the github-actions group with 3 updates (#2832)
• 2549ba9 Fix ConstructorConstructor creating mismatching Collection and Map instances ...
• Additional commits viewable in compare view

Updates commons-io:commons-io from 2.18.0 to 2.19.0

Updates io.swagger.core.v3:swagger-annotations from 2.2.29 to 2.2.30

Updates io.swagger.core.v3:swagger-models from 2.2.29 to 2.2.30

Updates io.swagger.core.v3:swagger-models from 2.2.29 to 2.2.30

Updates com.graphql-java:graphql-java from 22.3 to 23.0

Release notes

Sourced from com.graphql-java:graphql-java's releases.

23.0

Thanks to everyone for contributing to this release, through pull requests, issues, and discussions!

This is a major release which contains breaking changes.

Key changes

• Enable batching on Mutations graphql-java/graphql-java#3737

• Support for draft error handling directive @experimental_disableErrorPropagation graphql-java/graphql-java#3772

• DataFetchers can now return reactive-streams Publisher objects from them and they will be turned into a CompleteableFuture value. Note only a single value will be retrieved from the Publisher graphql-java/graphql-java#3731

• We changed from JetBrains nullability annotations to JSpecify annotations graphql-java/graphql-java#3851. JSpecify is a new industry consortium effort, which has been adopted by Spring. See more in the documentation: https://jspecify.dev/docs/start-here/

• A new experimental callback is available to track the execution state of GraphQL Java: it allows for being notified when GraphQL Java is running actively code vs waiting/finished. See https://github.com/graphql-java/graphql-java/blob/master/src/test/groovy/graphql/EngineRunningTest.groovy#L174 for how to use it

• We have also released DataLoader 4.0.0 and made graphql-java dependent on it. See the release notes: https://github.com/graphql-java/java-dataloader/releases

• @defer directive is now included in the schema by default graphql-java/graphql-java#3839

Performance improvements

• Only call overlapping validation once during validation, which will significantly reduce validation time, with more savings for larger operations. We found ~150% improvement in benchmarks. graphql-java/graphql-java#3835

• Reducing object allocations and overhead from stream, thanks @​kilink for contributing many improvements graphql-java/graphql-java#3804 graphql-java/graphql-java#3803 graphql-java/graphql-java#3801 graphql-java/graphql-java#3798 graphql-java/graphql-java#3797 graphql-java/graphql-java#3710

• Reducing object allocations for PropertyDataFetcher and SchemaGeneratorHelper graphql-java/graphql-java#3755 graphql-java/graphql-java#3754

• Improvement on DataFetchingSelectionSet.getImmediateFields(), if descendant traversal is not required this saves considerable time. Thanks @​timward60 graphql-java/graphql-java#3855

• Comparing performance improvements. We run performance benchmarks on all changes, and you can view these results inside the GitHub repo. You can then use this JMH visualisation tool to compare benchmarks from different commits, for example these before and after results from the DataFetcherSelectionSet optimisation: https://jmh.morethan.io/?sources=https://raw.githubusercontent.com/graphql-java/graphql-java/refs/heads/master/performance-results/2025-03-18T23%3A42%3A07Z-3d7dce5e49dfbe92d656629ae4fdbab979bba8be-jdk17.json,https://raw.githubusercontent.com/graphql-java/graphql-java/refs/heads/master/performance-results/2025-03-20T04%3A24%3A26Z-9a931ba6ad8e2ee49ea48c98ca86c2901f2343b1-jdk17.json

See all performance improvements on GitHub: https://github.com/graphql-java/graphql-java/issues?q=is%3Amerged%20label%3A%22performance%22%20milestone%3A%2223.0%20breaking%20changes%22%20

Breaking changes

• Strict runtime wiring redefinition checks now on by default. We now have stricter runtime wiring redefinition checks by default to catch invalid cases. For example, a field that already had a DataFetcher registered must not have a second DataFetcher registered. This can be toggled off. graphql-java/graphql-java#3824

• Removed an unused protected method in ExecutionStrategy. graphql-java/graphql-java#3881

• A small breaking change to AstPrinter to enable re-use of StringBuilders graphql-java/graphql-java#3853

• Improvement in a few directive and applied directive builders to address a bug where all elements were cleared. graphql-java/graphql-java#3825

• Breaking change for a new specification requirement, to prevent @include and @skip directives on subscription root fields graphql-java/graphql-java#3871

See all breaking changes on GitHub: https://github.com/graphql-java/graphql-java/issues?q=is%3Amerged%20label%3A%22breaking%20change%22%20milestone%3A%2223.0%20breaking%20changes%22

Security

... (truncated)

Commits

• 27b9def Merge pull request #3858 from graphql-java/java-dataloader-update
• d2c45ea Add performance results for commit 154bb89d14e9701d1b9f0764cbf813ba3a3c050a
• 35562f1 Merge branch 'master' into java-dataloader-update
• 154bb89 Merge pull request #3893 from graphql-java/tracking-refactor
• 59195c1 cleanup
• b3e94f4 Add performance results for commit 14c9136a6a33103f69f86f39bcd486bcae2ff525
• 14c9136 Merge pull request #3900 from graphql-java/updgrade-gradle-8.13
• 69f8230 upgrade to gradle 8.13
• 4ae0897 Merge branch 'master' into tracking-refactor
• 6054e56 Add performance results for commit 31b5f1b83c785c1acaff247c88aca6763328b754
• Additional commits viewable in compare view

Updates org.jetbrains.kotlinx:kotlinx-coroutines-core from 1.10.1 to 1.10.2

Release notes

Sourced from org.jetbrains.kotlinx:kotlinx-coroutines-core's releases.

1.10.2

• Fixed the kotlinx-coroutines-debug JAR file including the module-info.class file twice, resulting in failures in various tooling (#4314). Thanks, @​RyuNen344!
• Fixed Flow.stateIn hanging when the scope is cancelled in advance or the flow is empty (#4322). Thanks, @​francescotescari!
• Improved handling of dispatcher failures in .limitedParallelism (#4330) and during flow collection (#4272).
• Fixed runBlocking failing to run its coroutine to completion in some cases if its JVM thread got interrupted (#4399).
• Small tweaks, fixes, and documentation improvements.

Changelog

Sourced from org.jetbrains.kotlinx:kotlinx-coroutines-core's changelog.

Version 1.10.2

• Fixed the kotlinx-coroutines-debug JAR file including the module-info.class file twice, resulting in failures in various tooling (#4314). Thanks, @​RyuNen344!
• Fixed Flow.stateIn hanging when the scope is cancelled in advance or the flow is empty (#4322). Thanks, @​francescotescari!
• Improved handling of dispatcher failures in .limitedParallelism (#4330) and during flow collection (#4272).
• Fixed runBlocking failing to run its coroutine to completion in some cases if its JVM thread got interrupted (#4399).
• Small tweaks, fixes, and documentation improvements.

Commits

• 5f89004 Version 1.10.2
• 1a8de2e Merge remote-tracking branch 'origin/master' into develop
• e9b247e Advertise source jars for JVM-only libraries (#4394)
• 6baf7c8 Restore Android compatibility in Executor.asCoroutineDispatcher (#4396)
• dbca4c1 Reliably run finalizers even if runBlocking got interrupted. (#4399)
• 45893ce Add the issue template for guide-related problems (#4386)
• 8627cc3 Fix an explanation of flow emit (#4391)
• 5f8035c Specify explicit return types for some public API functions (#4389)
• 465e29d Set a predefined image width in debug-coroutines-with-idea.md (#4377)
• 96de301 Simplify newFixedThreadPoolContext using apply and remove unused import (#4378)
• Additional commits viewable in compare view

Updates com.google.guava:guava from 33.4.6-jre to 33.4.7-jre

Release notes

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

33.4.7

Known issue: This release breaks the build of Android apps with a minSdkVersion below 26. We will publish a fixed version soon. Sorry again for the continuing trouble.

Guava 33.4.7, like 33.4.6, fixes two problems that we introduced while modularizing Guava and migrating off Unsafe in 33.4.5.

Even if you're not upgrading from Guava 33.4.0 or earlier, still read the release notes for Guava 33.4.1. Those release notes contain information about the effects of Guava 33.4.5 and higher on the module system.

Maven

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

Jar files

• 33.4.7-jre.jar
• 33.4.7-android.jar

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

• failureaccess-1.0.3.jar

Javadoc

• 33.4.7-jre
• 33.4.7-android

JDiff

• 33.4.7-jre vs. 33.4.6-jre
• 33.4.7-android vs. 33.4.6-android
• 33.4.7-android vs. 33.4.7-jre

Changelog

• Modified the guava module's dependency on failureaccess to be transitive. Also, modified the guava-testlib module to make its dependency on guava transitive, to remove its dependency on failureaccess, and to add a dependency (transitive) on junit. (63ecdf2239)
• util.concurrent: Modified our fast paths to ensure that they continue to work when run through optimizers, such as those commonly used by Android apps. This fixes problems that some users may have seen since Guava 33.4.5. (b8dcaede09bcf1c3bd5fc037690498f6ac560c54, f9eff73b8d)
• util.concurrent: Changed the guava-android copy of AbstractFuture to try VarHandle before Unsafe, eliminating a warning under newer JDKs. (7336af1831)

Commits

• See full diff in compare view

Updates com.diffplug.spotless:spotless-maven-plugin from 2.44.3 to 2.44.4

Release notes

Sourced from com.diffplug.spotless:spotless-maven-plugin's releases.

Maven Plugin v2.44.4

Changed

• Use palantir-java-format 2.57.0 on Java 21. (#2447)
• Re-try npm install with --prefer-online after ERESOLVE error. (#2448)

Commits

• 0ca99e5 Published maven/2.44.4
• 1b1a4fb Published gradle/7.0.3
• 0fa3cab Published lib/3.1.1
• 0fe8f9b Update README.md for android kotlin callouts (#2438)
• d25f04d Minor tweak.
• fa3fd1e Add the cool blockquote warning trick to the other Android spot.
• 60993fd Fix the Android Kotlin warning and adjust its position.
• 0426db1 Apply Gradle's strict plugin types validation to the Spotless plugin in prepa...
• 48b4cde fix(deps): update dependency org.mockito:mockito-core to v5.17.0 (#2461)
• 81f2f8b fix(deps): update dependency org.mockito:mockito-core to v5.17.0
• Additional commits viewable in compare view

Updates software.amazon.awssdk:bom from 2.31.16 to 2.31.21

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

[jknack]

@dependabot recreate

[jknack]

@dependabot recreate

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.