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:
Serial Labels — see @CborLabel annotation and preferCborLabelsOverNames flag.
Tagging of keys and values — see encode*Tags and verify*Tags set of flags
Definite length encoding — see useDefiniteLengthEncoding. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported.
Option to globally prefer major type 2 for byte array encoding — see alwaysUseByteString flag.
Since there are quite a lot of flags now, they were restructured to a separate CborConfiguration class, similarly to JsonConfiguration. It is possible to retrieve this configuration from CborEncoder/CborDecoder interfaces 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.CoseCompliant instance.
However, some canonicalization steps (such as sorting keys) still need to be performed manually.
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 @KeepGeneratedSerializer annotation 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.
This annotation is currently experimental. Kotlin 2.0.20 or higher is required for this feature to work.
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 @Serializable classes.
Note that for now, serializer should be provided manually with @Contextual annotation. Plugin will be able to automatically insert Uuid serializer in Kotlin 2.1.0.
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:
Serial Labels — see @CborLabel annotation and preferCborLabelsOverNames flag.
Tagging of keys and values — see encode*Tags and verify*Tags set of flags
Definite length encoding — see useDefiniteLengthEncoding. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported.
Option to globally prefer major type 2 for byte array encoding — see alwaysUseByteString flag.
Since there are quite a lot of flags now, they were restructured to a separate CborConfiguration class, similarly to JsonConfiguration.
It is possible to retrieve this configuration from CborEncoder/CborDecoder interfaces 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.CoseCompliant instance.
However, some canonicalization steps (such as sorting keys) still need to be performed manually.
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 @KeepGeneratedSerializer annotation 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.
This annotation is currently experimental. Kotlin 2.0.20 or higher is required for this feature to work.
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 @Serializable classes.
Note that for now, serializer should be provided manually with @Contextual annotation.
Plugin will be able to automatically insert Uuid serializer in Kotlin 2.1.0.
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:
Serial Labels — see @CborLabel annotation and preferCborLabelsOverNames flag.
Tagging of keys and values — see encode*Tags and verify*Tags set of flags
Definite length encoding — see useDefiniteLengthEncoding. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported.
Option to globally prefer major type 2 for byte array encoding — see alwaysUseByteString flag.
Since there are quite a lot of flags now, they were restructured to a separate CborConfiguration class, similarly to JsonConfiguration. It is possible to retrieve this configuration from CborEncoder/CborDecoder interfaces 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.CoseCompliant instance.
However, some canonicalization steps (such as sorting keys) still need to be performed manually.
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 @KeepGeneratedSerializer annotation 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.
This annotation is currently experimental. Kotlin 2.0.20 or higher is required for this feature to work.
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 @Serializable classes.
Note that for now, serializer should be provided manually with @Contextual annotation. Plugin will be able to automatically insert Uuid serializer in Kotlin 2.1.0.
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:
Serial Labels — see @CborLabel annotation and preferCborLabelsOverNames flag.
Tagging of keys and values — see encode*Tags and verify*Tags set of flags
Definite length encoding — see useDefiniteLengthEncoding. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported.
Option to globally prefer major type 2 for byte array encoding — see alwaysUseByteString flag.
Since there are quite a lot of flags now, they were restructured to a separate CborConfiguration class, similarly to JsonConfiguration.
It is possible to retrieve this configuration from CborEncoder/CborDecoder interfaces 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.CoseCompliant instance.
However, some canonicalization steps (such as sorting keys) still need to be performed manually.
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 @KeepGeneratedSerializer annotation 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.
This annotation is currently experimental. Kotlin 2.0.20 or higher is required for this feature to work.
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 @Serializable classes.
Note that for now, serializer should be provided manually with @Contextual annotation.
Plugin will be able to automatically insert Uuid serializer in Kotlin 2.1.0.
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:
Serial Labels — see @CborLabel annotation and preferCborLabelsOverNames flag.
Tagging of keys and values — see encode*Tags and verify*Tags set of flags
Definite length encoding — see useDefiniteLengthEncoding. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported.
Option to globally prefer major type 2 for byte array encoding — see alwaysUseByteString flag.
Since there are quite a lot of flags now, they were restructured to a separate CborConfiguration class, similarly to JsonConfiguration. It is possible to retrieve this configuration from CborEncoder/CborDecoder interfaces 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.CoseCompliant instance.
However, some canonicalization steps (such as sorting keys) still need to be performed manually.
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 @KeepGeneratedSerializer annotation 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.
This annotation is currently experimental. Kotlin 2.0.20 or higher is required for this feature to work.
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 @Serializable classes.
Note that for now, serializer should be provided manually with @Contextual annotation. Plugin will be able to automatically insert Uuid serializer in Kotlin 2.1.0.
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:
Serial Labels — see @CborLabel annotation and preferCborLabelsOverNames flag.
Tagging of keys and values — see encode*Tags and verify*Tags set of flags
Definite length encoding — see useDefiniteLengthEncoding. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported.
Option to globally prefer major type 2 for byte array encoding — see alwaysUseByteString flag.
Since there are quite a lot of flags now, they were restructured to a separate CborConfiguration class, similarly to JsonConfiguration.
It is possible to retrieve this configuration from CborEncoder/CborDecoder interfaces 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.CoseCompliant instance.
However, some canonicalization steps (such as sorting keys) still need to be performed manually.
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 @KeepGeneratedSerializer annotation 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.
This annotation is currently experimental. Kotlin 2.0.20 or higher is required for this feature to work.
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 @Serializable classes.
Note that for now, serializer should be provided manually with @Contextual annotation.
Plugin will be able to automatically insert Uuid serializer in Kotlin 2.1.0.
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:
Serial Labels — see @CborLabel annotation and preferCborLabelsOverNames flag.
Tagging of keys and values — see encode*Tags and verify*Tags set of flags
Definite length encoding — see useDefiniteLengthEncoding. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported.
Option to globally prefer major type 2 for byte array encoding — see alwaysUseByteString flag.
Since there are quite a lot of flags now, they were restructured to a separate CborConfiguration class, similarly to JsonConfiguration. It is possible to retrieve this configuration from CborEncoder/CborDecoder interfaces 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.CoseCompliant instance.
However, some canonicalization steps (such as sorting keys) still need to be performed manually.
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 @KeepGeneratedSerializer annotation 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.
This annotation is currently experimental. Kotlin 2.0.20 or higher is required for this feature to work.
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 @Serializable classes.
Note that for now, serializer should be provided manually with @Contextual annotation. Plugin will be able to automatically insert Uuid serializer in Kotlin 2.1.0.
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:
Serial Labels — see @CborLabel annotation and preferCborLabelsOverNames flag.
Tagging of keys and values — see encode*Tags and verify*Tags set of flags
Definite length encoding — see useDefiniteLengthEncoding. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported.
Option to globally prefer major type 2 for byte array encoding — see alwaysUseByteString flag.
Since there are quite a lot of flags now, they were restructured to a separate CborConfiguration class, similarly to JsonConfiguration.
It is possible to retrieve this configuration from CborEncoder/CborDecoder interfaces 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.CoseCompliant instance.
However, some canonicalization steps (such as sorting keys) still need to be performed manually.
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 @KeepGeneratedSerializer annotation 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.
This annotation is currently experimental. Kotlin 2.0.20 or higher is required for this feature to work.
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 @Serializable classes.
Note that for now, serializer should be provided manually with @Contextual annotation.
Plugin will be able to automatically insert Uuid serializer in Kotlin 2.1.0.
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:
Serial Labels — see @CborLabel annotation and preferCborLabelsOverNames flag.
Tagging of keys and values — see encode*Tags and verify*Tags set of flags
Definite length encoding — see useDefiniteLengthEncoding. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported.
Option to globally prefer major type 2 for byte array encoding — see alwaysUseByteString flag.
Since there are quite a lot of flags now, they were restructured to a separate CborConfiguration class, similarly to JsonConfiguration. It is possible to retrieve this configuration from CborEncoder/CborDecoder interfaces 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.CoseCompliant instance.
However, some canonicalization steps (such as sorting keys) still need to be performed manually.
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 @KeepGeneratedSerializer annotation 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.
This annotation is currently experimental. Kotlin 2.0.20 or higher is required for this feature to work.
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 @Serializable classes.
Note that for now, serializer should be provided manually with @Contextual annotation. Plugin will be able to automatically insert Uuid serializer in Kotlin 2.1.0.
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:
Serial Labels — see @CborLabel annotation and preferCborLabelsOverNames flag.
Tagging of keys and values — see encode*Tags and verify*Tags set of flags
Definite length encoding — see useDefiniteLengthEncoding. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported.
Option to globally prefer major type 2 for byte array encoding — see alwaysUseByteString flag.
Since there are quite a lot of flags now, they were restructured to a separate CborConfiguration class, similarly to JsonConfiguration.
It is possible to retrieve this configuration from CborEncoder/CborDecoder interfaces 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.CoseCompliant instance.
However, some canonicalization steps (such as sorting keys) still need to be performed manually.
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 @KeepGeneratedSerializer annotation 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.
This annotation is currently experimental. Kotlin 2.0.20 or higher is required for this feature to work.
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 @Serializable classes.
Note that for now, serializer should be provided manually with @Contextual annotation.
Plugin will be able to automatically insert Uuid serializer in Kotlin 2.1.0.
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:
Serial Labels — see @CborLabel annotation and preferCborLabelsOverNames flag.
Tagging of keys and values — see encode*Tags and verify*Tags set of flags
Definite length encoding — see useDefiniteLengthEncoding. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported.
Option to globally prefer major type 2 for byte array encoding — see alwaysUseByteString flag.
Since there are quite a lot of flags now, they were restructured to a separate CborConfiguration class, similarly to JsonConfiguration. It is possible to retrieve this configuration from CborEncoder/CborDecoder interfaces in your custom serializers (see their documentation for details).
All of these features make it possible to serialize and parse
Bumps
kotlinx-serializationfrom 1.7.1 to 1.7.2. Updatesorg.jetbrains.kotlinx:kotlinx-serialization-corefrom 1.7.1 to 1.7.2Release notes
Sourced from org.jetbrains.kotlinx:kotlinx-serialization-core's releases.
Changelog
Sourced from org.jetbrains.kotlinx:kotlinx-serialization-core's changelog.
... (truncated)
Commits
8c84a5bPrepare 1.7.2 release (#2798)b3cfe56Merge remote-tracking branch 'origin/master' into dev550e1a8Rework opt-ins in build scripts (#2794)e4fa8a3Update Annotations.kt, fixed typo: RgpPixel -> RgbPixel (#2793)62aa4bbAdd serializer for kotlin.uuid.Uuid (#2744)4646740Prohibited using of zero and negative filed number in ProtoNumber and zero fi...4ca05ddUpdate Kotlin to 2.0.20 (#2792)35a9edcMigrate from kotlinOptions to compilerOptions (#2746)0b5145cImprove readability of protobuf decoding exception messages (#2768)b931598Remove redundant toString() (#2790)Updates
org.jetbrains.kotlinx:kotlinx-serialization-jsonfrom 1.7.1 to 1.7.2Release notes
Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's releases.
Changelog
Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's changelog.
... (truncated)
Commits
8c84a5bPrepare 1.7.2 release (#2798)b3cfe56Merge remote-tracking branch 'origin/master' into dev550e1a8Rework opt-ins in build scripts (#2794)e4fa8a3Update Annotations.kt, fixed typo: RgpPixel -> RgbPixel (#2793)62aa4bbAdd serializer for kotlin.uuid.Uuid (#2744)4646740Prohibited using of zero and negative filed number in ProtoNumber and zero fi...4ca05ddUpdate Kotlin to 2.0.20 (#2792)35a9edcMigrate from kotlinOptions to compilerOptions (#2746)0b5145cImprove readability of protobuf decoding exception messages (#2768)b931598Remove redundant toString() (#2790)Updates
org.jetbrains.kotlinx:kotlinx-serialization-hoconfrom 1.7.1 to 1.7.2Release notes
Sourced from org.jetbrains.kotlinx:kotlinx-serialization-hocon's releases.
Changelog
Sourced from org.jetbrains.kotlinx:kotlinx-serialization-hocon's changelog.
... (truncated)
Commits
8c84a5bPrepare 1.7.2 release (#2798)b3cfe56Merge remote-tracking branch 'origin/master' into dev550e1a8Rework opt-ins in build scripts (#2794)e4fa8a3Update Annotations.kt, fixed typo: RgpPixel -> RgbPixel (#2793)62aa4bbAdd serializer for kotlin.uuid.Uuid (#2744)4646740Prohibited using of zero and negative filed number in ProtoNumber and zero fi...4ca05ddUpdate Kotlin to 2.0.20 (#2792)35a9edcMigrate from kotlinOptions to compilerOptions (#2746)0b5145cImprove readability of protobuf decoding exception messages (#2768)b931598Remove redundant toString() (#2790)Updates
org.jetbrains.kotlinx:kotlinx-serialization-protobuffrom 1.7.1 to 1.7.2Release notes
Sourced from org.jetbrains.kotlinx:kotlinx-serialization-protobuf's releases.
Changelog
Sourced from org.jetbrains.kotlinx:kotlinx-serialization-protobuf's changelog.
... (truncated)
Commits
8c84a5bPrepare 1.7.2 release (#2798)b3cfe56Merge remote-tracking branch 'origin/master' into dev550e1a8Rework opt-ins in build scripts (#2794)e4fa8a3Update Annotations.kt, fixed typo: RgpPixel -> RgbPixel (#2793)62aa4bbAdd serializer for kotlin.uuid.Uuid (#2744)4646740Prohibited using of zero and negative filed number in ProtoNumber and zero fi...4ca05ddUpdate Kotlin to 2.0.20 (#2792)35a9edcMigrate from kotlinOptions to compilerOptions (#2746)0b5145cImprove readability of protobuf decoding exception messages (#2768)b931598Remove redundant toString() (#2790)Updates
org.jetbrains.kotlinx:kotlinx-serialization-cborfrom 1.7.1 to 1.7.2Release notes
Sourced from org.jetbrains.kotlinx:kotlinx-serialization-cbor's releases.
Changelog
Sourced from org.jetbrains.kotlinx:kotlinx-serialization-cbor's changelog.
... (truncated)
Commits
8c84a5bPrepare 1.7.2 release (#2798)b3cfe56Merge remote-tracking branch 'origin/master' into dev550e1a8Rework opt-ins in build scripts (#2794)e4fa8a3Update Annotations.kt, fixed typo: RgpPixel -> RgbPixel (#2793)62aa4bbAdd serializer for kotlin.uuid.Uuid (#2744)4646740Prohibited using of zero and negative filed number in ProtoNumber and zero fi...4ca05ddUpdate Kotlin to 2.0.20 (#2792)35a9edcMigrate from kotlinOptions to compilerOptions (#2746)0b5145cImprove readability of protobuf decoding exception messages (#2768)b931598Remove redundant toString() (#2790)Updates
org.jetbrains.kotlinx:kotlinx-serialization-propertiesfrom 1.7.1 to 1.7.2Release notes
Sourced from org.jetbrains.kotlinx:kotlinx-serialization-properties's releases.