Skip to content

fix(deps): update dependency org.jetbrains.kotlinx:kotlinx-serialization-json to v1.10.0#192

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/kotlinxserializationjson
Open

fix(deps): update dependency org.jetbrains.kotlinx:kotlinx-serialization-json to v1.10.0#192
renovate[bot] wants to merge 1 commit intomainfrom
renovate/kotlinxserializationjson

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 9, 2026

This PR contains the following updates:

Package Change Age Confidence
org.jetbrains.kotlinx:kotlinx-serialization-json 1.9.01.10.0 age confidence

Release Notes

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 - "before 9am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

@renovate renovate bot added the dependencies label Feb 9, 2026
@claude
Copy link

claude bot commented Feb 9, 2026

Claude finished @renovate[bot]'s task in 2m 4s —— View job


Code Review: kotlinx-serialization-json 1.9.0 → 1.10.0

Summary

This dependency update is safe to merge after running tests. The update is primarily a stabilization release with no breaking changes affecting this codebase.


Compatibility Analysis

Kotlin Version Compatibility

  • Project uses Kotlin 2.2.21 (gradle/libs.versions.toml:22)
  • kotlinx-serialization-json 1.10.0 requires Kotlin 2.3.0
  • Note: There's a version mismatch here. The release notes state 1.10.0 is "based on Kotlin 2.3.0", but your project is on Kotlin 2.2.21. However, kotlinx-serialization typically maintains backward compatibility with older Kotlin versions for runtime usage.

Usage Pattern Analysis
The codebase uses kotlinx-serialization in a straightforward manner:

  • Data classes with @Serializable annotation (LogEntry.kt:17, NetworkRequest.kt:11, BugReportMetadata.kt:8, etc.)
  • Basic JSON encoding/decoding (BugReportDraftStorage.kt:80, BugReportFileWriters.kt:29)
  • Simple Json configuration: Json { ignoreUnknownKeys = true } and Json { prettyPrint = false }

No Advanced Features Used
The codebase does NOT use any of the experimental features that were stabilized in 1.10.0:

  • No decodeEnumsCaseInsensitive, allowTrailingComma, or allowComments configuration
  • No @EncodeDefault annotations
  • No JsonUnquotedLiteral usage
  • No unsigned type JsonPrimitive constructors

What Changed in 1.10.0

Stabilized APIs (not affecting this project):

  • Configuration options: decodeEnumsCaseInsensitive, allowTrailingComma, allowComments, prettyPrintIndent
  • @EncodeDefault annotation and modes
  • JsonUnquotedLiteral and unsigned type constructors

Bug Fixes:

  • ProtoBuf packing of unsigned types (#3079)
  • Class discriminator conflict detection improvements (#3105)
  • Various CBOR decoder strictness improvements

New Features:

  • subclassesOfSealed utility for polymorphic modules (not used in this project)
  • Better diagnostics: .serialName in MissingFieldException (#3114)

Risk Assessment

Low Risk 🟢

  1. No Breaking Changes: This is a stabilization release. All changes are backward-compatible.
  2. Simple Usage: The project uses only basic serialization features (data classes, basic JSON config).
  3. No Polymorphic Serialization: The project doesn't use polymorphic or sealed class hierarchies with serialization, so the discriminator changes don't apply.
  4. Improved Diagnostics: Better error messages will help debugging if issues arise.

Potential Concerns:

  • The Kotlin version mismatch (2.2.21 vs 2.3.0 requirement) might cause issues, though kotlinx-serialization typically maintains backward compatibility. Monitor for any compilation warnings.

Recommendations

  1. Run Tests ✓ (Required)

    ./gradlew spotlessApply
    ./gradlew :debugoverlay-core:check

    This will verify serialization/deserialization still works correctly, especially for:

    • BugReportMetadata.kt:58 serialization/deserialization
    • LogEntry.kt:18 and NetworkRequest.kt:12 JSON encoding
    • Bug report draft storage operations
  2. Consider Kotlin Update (Future)

    • Consider updating to Kotlin 2.3.0+ in a future PR to match kotlinx-serialization-json's target version
    • This would ensure optimal compatibility and access to any Kotlin 2.3.0-specific optimizations
  3. Test Bug Report Flow (Manual, Optional)

    • Run the sample app and create a bug report to verify serialization works end-to-end
    • Verify draft saving/loading works (uses JSON serialization in BugReportDraftStorage.kt:80, :440, :449)

Files Affected by Serialization

For reference, here are the key files using kotlinx-serialization:

  • debugoverlay-core/src/main/kotlin/com/ms/square/debugoverlay/model/LogEntry.kt:4
  • debugoverlay-core/src/main/kotlin/com/ms/square/debugoverlay/model/NetworkRequest.kt:3
  • debugoverlay-core/src/main/kotlin/com/ms/square/debugoverlay/internal/bugreport/BugReportDraftStorage.kt:34
  • debugoverlay-core/src/main/kotlin/com/ms/square/debugoverlay/internal/bugreport/BugReportFileWriters.kt:10
  • debugoverlay-core/src/main/kotlin/com/ms/square/debugoverlay/internal/bugreport/model/BugReportMetadata.kt:3
  • debugoverlay-core/src/main/kotlin/com/ms/square/debugoverlay/internal/data/model/DeviceInfo.kt
  • debugoverlay-core/src/main/kotlin/com/ms/square/debugoverlay/internal/bugreport/model/AppInfo.kt

Verdict

✅ APPROVE pending successful test execution.

This is a safe, low-risk dependency update. The changes are primarily API stabilization and bug fixes that don't affect this codebase's usage patterns.


| Branch: renovate/kotlinxserializationjson

@github-actions
Copy link

github-actions bot commented Feb 9, 2026

Qodana 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

Contact Qodana team

Contact us at qodana-support@jetbrains.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants