Skip to content

Update dependency org.jetbrains.kotlinx:kotlinx-serialization-json-jvm to v1.13.0 - #1079

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/kotlinx.serialization
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/kotlinx.serialization

Conversation

@renovate

@renovate renovate Bot commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
org.jetbrains.kotlinx:kotlinx-serialization-json-jvm 1.12.0 → 1.13.0 age confidence

Release Notes

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

v1.13.0

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

This release is based on Kotlin 2.4.10 and reverts a breaking change introduced in 1.12.0.

Besides that, it improves JsonElement.toString performance.

Exceptions rework rollback

In 1.12.0, Json format start intercepting almost all exceptions thrown by serializers during serialization and
deserialization, and wrap them into a JsonException with additional information about JSON path and input.

The impact of the change was underestimated, and it was decided to revert the change.

Performance improvements

JsonElement.toString was rewritten and its improved twofold on some benchmarks.
See #​3296 and #​3299 for details.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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 was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot enabled auto-merge (squash) November 12, 2026 00:48

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants