helcel/keepass-fidelity
3
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases 19 Wiki Activity

Update dependency org.jetbrains.kotlinx:kotlinx-serialization-json to v1.10.0 #205

Merged
bot merged 1 commits from renovate/org.jetbrains.kotlinx-kotlinx-serialization-json-1.x into main 2026-01-22 03:01:47 +01:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
bot commented 2026-01-22 03:01:44 +01:00
Member
Copy Link

This PR contains the following updates:

Package Type Update Change
org.jetbrains.kotlinx:kotlinx-serialization-json dependencies minor 1.9.0 -> 1.10.0

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 - "every weekday,every weekend" (UTC), Automerge - "every weekend" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [org.jetbrains.kotlinx:kotlinx-serialization-json](https://github.com/Kotlin/kotlinx.serialization) | dependencies | minor | `1.9.0` -> `1.10.0` | --- ### Release Notes <details> <summary>Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)</summary> ### [`v1.10.0`](https://github.com/Kotlin/kotlinx.serialization/blob/HEAD/CHANGELOG.md#1100--2026-01-21) \================== 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 ([#&#8203;3079](https://github.com/Kotlin/kotlinx.serialization/issues/3079)). Big thanks to [KosmX](https://github.com/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`. ([#&#8203;3100](https://github.com/Kotlin/kotlinx.serialization/issues/3100)) - `@EncodeDefault` annotation and its modes. ([#&#8203;3106](https://github.com/Kotlin/kotlinx.serialization/issues/3106)) - `JsonUnquotedLiteral` constructor function ([#&#8203;2900](https://github.com/Kotlin/kotlinx.serialization/issues/2900)) - `JsonPrimitive` constructor function overloads that accept unsigned types. ([#&#8203;3117](https://github.com/Kotlin/kotlinx.serialization/issues/3117)) - JSON DSL functions on `JsonElement` with `Nothing?` overloads. ([#&#8203;3117](https://github.com/Kotlin/kotlinx.serialization/issues/3117)) #### Readiness for return value checker Kotlin 2.3.0 [introduces a new feature](https://kotlinlang.org/docs/whatsnew23.html#unused-return-value-checker) 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](https://kotlinlang.org/docs/unused-return-value-checker.html#configure-the-unused-return-value-checker). #### Polymorphism improvements Polymorphic serialization received a couple of improvements in this release: New `subclassesOfSealed` utility to automatically register sealed subclasses serializers in polymorphic modules ([#&#8203;2201](https://github.com/Kotlin/kotlinx.serialization/issues/2201)). Use it in your `SerializersModule` when configuring a polymorphic hierarchy which contains both abstract and sealed classes. [For example](https://github.com/Kotlin/kotlinx.serialization/issues/2199), 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 `SerializerModule`s much faster and simpler. Big thanks to [Paul de Vrieze](https://github.com/pdvrieze) for contributing this feature. Class discriminator conflict check rework ([#&#8203;3105](https://github.com/Kotlin/kotlinx.serialization/issues/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 [#&#8203;1664](https://github.com/Kotlin/kotlinx.serialization/issues/1664) for details. #### General improvements - Add `.serialName` to `MissingFieldException` for clearer diagnostics. ([#&#8203;3114](https://github.com/Kotlin/kotlinx.serialization/issues/3114)) - Generate unique `Automatic-Module-Name` entries for metadata JARs. ([#&#8203;3109](https://github.com/Kotlin/kotlinx.serialization/issues/3109)) - Revised ProGuard rules and added R8 tests. ([#&#8203;3041](https://github.com/Kotlin/kotlinx.serialization/issues/3041)) - CBOR: Improved error message when a byte string/array type mismatch is encountered. ([#&#8203;3052](https://github.com/Kotlin/kotlinx.serialization/issues/3052)) #### Bugfixes - Fix the type in the `BIGNUM_NEGATIVE` tag name. ([#&#8203;3090](https://github.com/Kotlin/kotlinx.serialization/issues/3090)) - CBOR: Fix various bugs in the decoder implementation to be more strict and consistent with the specification. </details> --- ### Configuration 📅 **Schedule**: Branch creation - "every weekday,every weekend" (UTC), Automerge - "every weekend" (UTC). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi41OC4zIiwidXBkYXRlZEluVmVyIjoiNDIuNTguMyIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiYm90IiwicmVub3ZhdGUiXX0=-->
bot added 1 commit 2026-01-22 03:01:44 +01:00
Update dependency org.jetbrains.kotlinx:kotlinx-serialization-json to v1.10.0 d8d91f091a
bot scheduled this pull request to auto merge when all checks succeed 2026-01-22 03:01:44 +01:00
bot merged commit 7866c074ed into main 2026-01-22 03:01:47 +01:00
bot deleted branch renovate/org.jetbrains.kotlinx-kotlinx-serialization-json-1.x 2026-01-22 03:01:47 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bot fgerber sora
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: helcel/keepass-fidelity#205
No description provided.
Delete Branch "renovate/org.jetbrains.kotlinx-kotlinx-serialization-json-1.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?