fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Age	Confidence
gradle (source)		minor	9.2.1 → 9.3.1
org.jetbrains.kotlinx:kotlinx-serialization-json	dependencies	minor	1.9.0 → 1.10.0
org.jetbrains.kotlin.multiplatform	plugin	patch	2.3.0 → 2.3.10

---

Release Notes

gradle/gradle (gradle)

v9.3.1: 9.3.1

Compare Source

This is a patch release for 9.3.0. We recommend using 9.3.1 instead of 9.3.0.

The following issues were resolved:

• Cannot find testcases from Android Screenshot Test plugin since Gradle 9.3.0
• Excluding dependencies from included builds doesn't work in Gradle 9.3.0
• ExternalDependency and DependencyConstraint cannot be passed to DependencyResolveDetails#useTarget
• Gradle 9.3.0 generate JUnit test result files with wrong name
• Build cache cannot handle outputs with non-BMP characters in the filename
• Emojis in test names should not break build caching
• Non utf-8 c code is no longer buildable
• Breaking change in 9.3.0 regarding cross-project dependency manipulation
• JUnit3 tests cannot be run with Gradle 9.3.0
• Test.setScanForTestClasses(false) causes all junit4 tests to be skipped

Read the Release Notes

Upgrade instructions

Switch your build to use Gradle 9.3.1 by updating your wrapper:

./gradlew wrapper --gradle-version=9.3.1 && ./gradlew wrapper

See the Gradle 9.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v9.3.0

Compare Source

Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)

v1.10.0

==================

This release is based on Kotlin 2.3.0 and contains all of the changes from 1.10.0-RC.
The only additional change is a fix for ProtoBuf packing of Kotlin unsigned types (#​3079).
Big thanks to KosmX for contributing the fix.

For your convenience, the changelog for 1.10.0-RC is duplicated below:

Stabilization of APIs

kotlinx-serialization 1.10 and subsequent releases will be focused on stabilization of existing APIs.
The following APIs and configuration options are no longer experimental because they're widely used without any known major issues:

• Json configuration options: decodeEnumsCaseInsensitive, allowTrailingComma, allowComments, and prettyPrintIndent. (#​3100)
• @EncodeDefault annotation and its modes. (#​3106)
• JsonUnquotedLiteral constructor function (#​2900)
• JsonPrimitive constructor function overloads that accept unsigned types. (#​3117)
• JSON DSL functions on JsonElement with Nothing? overloads. (#​3117)

Readiness for return value checker

Kotlin 2.3.0 introduces a new feature aimed
at helping you to catch bugs related to the accidentally ignored return value of the function.
kotlinx-serialization 1.10.0-RC code is fully marked for this feature, meaning that you
can get warnings for unused function calls like Json.encodeToString(...).
To get the warnings, the feature has to be enabled in your project as described here.

Polymorphism improvements

Polymorphic serialization received a couple of improvements in this release:

New subclassesOfSealed utility to automatically register sealed subclasses serializers in polymorphic modules (#​2201).
Use it in your SerializersModule when configuring a polymorphic hierarchy which contains both abstract and sealed classes.
For example, when root of your hierarchy is an interface, but most of your inheritors are sealed classes.
The new function will register all known sealed subclasses for you, so you don’t need to list them one by one.
This makes writing your SerializerModules much faster and simpler.
Big thanks to Paul de Vrieze for contributing this feature.

Class discriminator conflict check rework (#​3105).
If a payload already contains a property with the same name as the configured discriminator (for example, type),
it is called a class discriminator conflict.
To produce a correct output and allow more inputs to be deserialized at the same time, the following changes were made:

• Conflicts introduced by JsonNamingStrategy transformations are now detected during serialization as well and will cause SerializationException.
  It also affects non-polymorphic classes.
• Conflicts from ClassDisciminatorMode.ALL_JSON_OBJECTS and SerializersModuleBuilder.polymorphicDefaultSerializer are also detected.
• It is allowed to deserialize such a conflicting key for both sealed and open polymorphic hierarchies.
  Previously, it was possible in the sealed hierarchies alone due to missing assertion. See #​1664 for details.

General improvements

• Add .serialName to MissingFieldException for clearer diagnostics. (#​3114)
• Generate unique Automatic-Module-Name entries for metadata JARs. (#​3109)
• Revised ProGuard rules and added R8 tests. (#​3041)
• CBOR: Improved error message when a byte string/array type mismatch is encountered. (#​3052)

Bugfixes

• Fix the type in the BIGNUM_NEGATIVE tag name. (#​3090)
• CBOR: Fix various bugs in the decoder implementation to be more strict and consistent with the specification.

---

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 is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.