This repository was archived by the owner on Dec 18, 2025. It is now read-only.
fix(deps): update dependency org.jetbrains.kotlinx:kotlinx-serialization-json to v1.9.0#53
Open
renovate[bot] wants to merge 1 commit intomasterfrom
Conversation
4ff8ac8 to
867a660
Compare
867a660 to
c1b2048
Compare
97b4b62 to
4a8a68f
Compare
4a8a68f to
53c21e0
Compare
53c21e0 to
cf96ed4
Compare
cf96ed4 to
7fc7611
Compare
920c9c8 to
a985d2e
Compare
a985d2e to
5636867
Compare
5636867 to
b79b2bc
Compare
b79b2bc to
49318e0
Compare
49318e0 to
31c1da2
Compare
31c1da2 to
30f3563
Compare
30f3563 to
79f8951
Compare
79f8951 to
f44b85e
Compare
f44b85e to
dd186e0
Compare
dd186e0 to
65ef180
Compare
65ef180 to
df4def7
Compare
df4def7 to
de0a799
Compare
de0a799 to
c5448b6
Compare
c5448b6 to
1b58db3
Compare
1b58db3 to
4d76b51
Compare
4d76b51 to
f348186
Compare
f348186 to
0791ba1
Compare
0791ba1 to
11580fe
Compare
11580fe to
c8d558d
Compare
c8d558d to
47948c4
Compare
371db47 to
9798855
Compare
…ion-json to v1.9.0
9798855 to
32a22d0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.5.1->1.9.0Release Notes
Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)
v1.9.0==================
This release updates Kotlin version to 2.2.0, includes several bugfixes and provides serializers for kotlin.time.Instant.
Add kotlin.time.Instant serializers
Instant class was moved from kotlinx-datetime library to Kotlin standard library.
As a result, kotlinx-datetime 0.7.0 no longer has serializers for the Instant class.
To use new kotlin.time.Instant class in your @Serializable classes,
you can use this 1.9.0 kotlinx-serialization version (Kotlin 2.2 is required).
You can choose between default
InstantSerializerwhich uses its string representation,or specify
InstantComponentSerializerthat represents instant as its components.See details in the PR.
Other bugfixes
v1.8.1==================
This release updates Kotlin version to 2.1.20, while also providing several important improvements
and bugfixes.
Improvements
Bugfixes
v1.8.0==================
This release contains all of the changes from 1.8.0-RC. Kotlin 2.1.0 is used as a default, while upcoming 2.1.10 is also supported.
Also added small bugfixes, including speedup of ProtoWireType.from (#2879).
v1.7.3==================
This release aims to fix important issues that were discovered in the 1.7.2 release,
including the inability to sync certain projects into Android Studio/IntelliJ IDEA and exceptions from custom Uuid serializers.
It uses Kotlin 2.0.20 by default.
v1.7.2==================
This release provides several new features, including a major Cbor configuration rework.
It uses Kotlin 2.0.20 by default.
Cbor feature set for COSE compliance
This change brings a lot of features to the CBOR format, namely:
@CborLabelannotation andpreferCborLabelsOverNamesflag.encode*Tagsandverify*Tagsset of flagsuseDefiniteLengthEncoding. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported.alwaysUseByteStringflag.Since there are quite a lot of flags now, they were restructured to a separate
CborConfigurationclass, similarly toJsonConfiguration.It is possible to retrieve this configuration from
CborEncoder/CborDecoderinterfaces in your custom serializers (see their documentation for details).All of these features make it possible to serialize and parse COSE-compliant CBOR, for example, ISO/IEC 18013-5:2021-compliant mobile driving license data.
In case you want to make use of them, there is a predefined
Cbor.CoseCompliantinstance.However, some canonicalization steps (such as sorting keys) still need to be performed manually.
This functionality was contributed to us by Bernd Prünster.
Keeping generated serializers
One of the most requested features for serialization plugin was to continue to generate a serializer even if a custom one is specified for the class.
It allows using a plugin-generated serializer in a fallback or delegate strategy, accessing type structure via descriptor, using default serialization behavior in inheritors that do not use custom serializers.
Starting with this release, you can specify the
@KeepGeneratedSerializerannotation on the class declaration to instruct the plugin to continue generating the serializer.In this case, the serializer will be accessible using the
.generatedSerializer()function on the class's companion object.You can check out the examples in the documentation and in the PRs: #2758, #2669.
Serializer for kotlin.uuid.Uuid
Kotlin 2.0.20 added a common class to represent UUIDs in a multiplatform code.
kotlinx.serialization 1.7.2 provides a corresponding
Uuid.serializer()for it, making it possible to use it in@Serializableclasses.Note that for now, serializer should be provided manually with
@Contextualannotation.Plugin will be able to automatically insert
Uuidserializer in Kotlin 2.1.0.See more details in the corresponding PR.
Other bugfixes and improvements
v1.7.1==================
This is a bugfix release that aims to fix missing
kotlinx-serialization-hoconartifact.It also contains experimental integration with
kotlinx-iolibrary.Kotlin 2.0.0 is used by default.
Fixed HOCON publication
Sadly, 1.7.0 release was published incomplete:
kotlinx-serialization-hoconartifact is missing from 1.7.0 and 1.7.0-RC releases.This release fixes this problem and now
kotlinx-serialization-hoconis available again with 1.7.1 version.No other changes were made to this artifact. Related ticket: #2717.
Add integration with a kotlinx-io library
kotlinx-iois an official multiplatform library that provides basic IO primitives, similar to Okio.kotlinx.serialization integration is now available in a separate artifact, located at the
kotlinx-serialization-json-iocoordinates.Integration artifact provides functions similar to existing Okio integration:
encodeToSink,decodeFromSource, anddecodeSourceToSequence.Check out the PR for more details.
Other bugfixes
v1.7.0==================
This release contains all of the changes from 1.7.0-RC and is compatible with Kotlin 2.0.
Please note that for reasons explained in the 1.7.0-RC changelog, it may not be possible to use it with the Kotlin 1.9.x
compiler plugin. Yet, it is still fully backwards compatible with previous versions.
The only difference with 1.7.0-RC is that
classDiscriminatorModeproperty inJsonBuilderis marked as experimental,as it should have been when it was introduced (#2680).
v1.6.3==================
This release provides a couple of new features and uses Kotlin 1.9.22 as default.
Class discriminator output mode
Class discriminator provides information for serializing and deserializing polymorphic class hierarchies.
In case you want to encode more or less information for various third party APIs about types in the output, it is possible to control
addition of the class discriminator with the
JsonBuilder.classDiscriminatorModeproperty.For example,
ClassDiscriminatorMode.NONEdoes not add class discriminator at all, in case the receiving party is not interested in Kotlin types.You can learn more about this feature in the documentation and corresponding PR.
Other features
Bugfixes and improvements
v1.6.2==================
This is a patch release accompanying Kotlin 1.9.21. It also provides additional targets that were not available in 1.6.1:
wasm-wasi and (deprecated) linuxArm32Hfp.
v1.6.1==================
This release uses Kotlin 1.9.20 by default, while upcoming 1.9.21 is also supported.
Trailing commas in Json
Trailing commas are one of the most popular non-spec Json variations.
A new configuration flag,
allowTrailingComma, makes Json parser accept them instead of throwing an exception.Note that it does not affect encoding, so kotlinx.serialization always produces Json without trailing commas.
See details in the corresponding PR
Support of WasmJs target
Kotlin/Wasm has been experimental for some time and gained enough maturity to be added to the kotlinx libraries.
Starting with 1.6.1, kotlinx.serialization provides a wasm-js flavor, so your projects with Kotlin/Wasm can have even more
functionality.
As usual, just add serialization dependencies to your build
and declare wasmJs target.
Please remember that Kotlin/Wasm is still experimental, so changes are expected.
Bugfixes and improvements
v1.6.0==================
This release contains all features and bugfixes from 1.6.0-RC plus some bugfixes on its own (see below).
Kotlin 1.9.0 is used as a default, while 1.9.10 is also supported.
Bugfixes
Configuration
📅 Schedule: 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.
This PR was generated by Mend Renovate. View the repository job log.