Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deps: update dependency org.jetbrains.kotlinx:kotlinx-serialization-core to v1.7.3 #605

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 28, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.jetbrains.kotlinx:kotlinx-serialization-core 1.7.1 -> 1.7.3 age adoption passing confidence

Release Notes

Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-core)

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.

  • Use explicit kotlin-stdlib and kotlin-test versions from version catalog (#​2818)
  • Drop usage of deprecated Any?.freeze() in K/N target (#​2819)
  • Check against serialName instead of simpleClassName (#​2802)
  • Ignore NoClassDefFoundError when initializing builtins map for serializer() function (#​2803)
  • Clarify example for SerializationException (#​2806)

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:

  • 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.

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 @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.

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 @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.

See more details in the corresponding PR.

Other bugfixes and improvements

  • Prohibited using of zero and negative field numbers in ProtoNumber (#​2766)
  • Improve readability of protobuf decoding exception messages (#​2768) (thanks to xiaozhikang0916)
  • docs(serializers): Fix grammatical errors (#​2779) (thanks to jamhour1g)
  • Fixed VerifyError after ProGuard optimization (#​2728)
  • Add wasm-wasi target to Okio integration (#​2727)

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.


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

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

@sschuberth
Copy link
Contributor

@charleskorn any idea what's up with the tests?

@charleskorn
Copy link
Owner

@charleskorn any idea what's up with the tests?

I'm guessing something has changed with kotlin.uuid.Uuid (maybe it's moved to a new package as part of a Kotlin release, and kotlinx.serialization was built against that new release?).

The upgrade to Kotlin 2.0.20 is blocked due to kotest needing some fixes in its compiler plugin to address breaking changes in the Kotlin compiler.

@renovate renovate bot force-pushed the renovate/org.jetbrains.kotlinx-kotlinx-serialization-core-1.x branch 5 times, most recently from ae505f2 to 251b807 Compare September 13, 2024 05:33
@sschuberth
Copy link
Contributor

The upgrade to Kotlin 2.0.20 is blocked due to kotest needing some fixes in its compiler plugin to address breaking changes in the Kotlin compiler.

By "compiler plugin" I guess you mean "Gradle plugin". Anyway, we could use a snapshot version of the plugin while sticking with Kotest to the latest release as described here.

@renovate renovate bot force-pushed the renovate/org.jetbrains.kotlinx-kotlinx-serialization-core-1.x branch from 251b807 to abd61b6 Compare September 13, 2024 07:21
@renovate renovate bot changed the title fix(deps): update dependency org.jetbrains.kotlinx:kotlinx-serialization-core to v1.7.2 fix(deps): update dependency org.jetbrains.kotlinx:kotlinx-serialization-core to v1.7.3 Sep 19, 2024
@renovate renovate bot force-pushed the renovate/org.jetbrains.kotlinx-kotlinx-serialization-core-1.x branch 5 times, most recently from d8aee8f to ede14ef Compare September 25, 2024 21:43
@renovate renovate bot force-pushed the renovate/org.jetbrains.kotlinx-kotlinx-serialization-core-1.x branch from ede14ef to 49ca179 Compare October 7, 2024 21:19
@renovate renovate bot force-pushed the renovate/org.jetbrains.kotlinx-kotlinx-serialization-core-1.x branch 10 times, most recently from b7b4889 to 83b799d Compare October 29, 2024 22:27
@renovate renovate bot changed the title fix(deps): update dependency org.jetbrains.kotlinx:kotlinx-serialization-core to v1.7.3 deps: update dependency org.jetbrains.kotlinx:kotlinx-serialization-core to v1.7.3 Oct 29, 2024
@renovate renovate bot force-pushed the renovate/org.jetbrains.kotlinx-kotlinx-serialization-core-1.x branch from 83b799d to 18d351f Compare October 29, 2024 22:30
@renovate renovate bot force-pushed the renovate/org.jetbrains.kotlinx-kotlinx-serialization-core-1.x branch from 18d351f to 15ab829 Compare October 29, 2024 23:08
@renovate renovate bot force-pushed the renovate/org.jetbrains.kotlinx-kotlinx-serialization-core-1.x branch from 15ab829 to ba69995 Compare October 29, 2024 23:14
@charleskorn charleskorn merged commit 1043bd7 into main Oct 30, 2024
11 checks passed
@renovate renovate bot deleted the renovate/org.jetbrains.kotlinx-kotlinx-serialization-core-1.x branch October 30, 2024 00:32
Copy link

🎉 This PR is included in version 0.62.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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.

2 participants