firebase-kotlin-sdk
firebase-kotlin-sdk copied to clipboard
Bump org.jetbrains.kotlinx:kotlinx-serialization-core from 1.7.2 to 1.8.1
Bumps org.jetbrains.kotlinx:kotlinx-serialization-core from 1.7.2 to 1.8.1.
Release notes
Sourced from org.jetbrains.kotlinx:kotlinx-serialization-core's releases.
1.8.1
This release updates Kotlin version to 2.1.20, while also providing several important improvements and bugfixes.
Improvements
- Implemented encoding null in key and value of a map in Protobuf (#2910)
- Make type argument in JsonTransformingSerializer nullable (#2911)
- Use SPDX identifier in POMs (#2936) (thanks to Leon Linhart)
- Add watchosDeviceArm64 to Okio integration module (#2920) (thanks to Daniel Santiago)
- Update kotlinx-io version to 0.6.0 (#2933) (thanks to Piotr Krzemiński)
Bugfixes
- Fix incorrect enum coercion during deserialization from JsonElement (#2962)
- Supply proper equals(), hashCode(), and toString() for SerialDescriptor() wrapper (#2942)
- Do not encode empty packed collections in protobuf (#2907)
1.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).Changelog for 1.8.0-RC is presented below:
@JsonIgnoreUnknownKeysannotationPreviously, only global setting
JsonBuilder.ignoreUnknownKeyscontrolled whether Json parser would throw exception if input contained a property that was not declared in a@Serializableclass. There were a lot of complaints that this setting is not flexible enough. To address them, we added new@JsonIgnoreUnknownKeysannotation that can be applied on a per-class basis. With this annotation, it is possible to allow unknown properties for annotated classes, while general decoding methods (such asJson.decodeFromStringand others) would still reject them for everything else. See details in the corresponding PR.Stabilization of
SerialDescriptorAPI and@SealedSerializationApiannotation
SerialDescriptor,SerialKind, and related API has been around for a long time and has proven itself useful. The main reason@ExperimentalSerializationApiwas on SerialDescriptor's properties is that we wanted to discourage people from subclassing it. Fortunately, Kotlin 2.1 provides a special mechanism for such a case — SubclassOptInRequired. Newkotlinx.serialization.SealedSerializationApiannotation designates APIs as public for use, but closed for implementation — the case for SerialDescriptor, which is a non-sealed interface for technical reasons. Now you can use most ofSerialDescriptorand its builders API without the need to opt-in into experimental serialization API. See the PR for more details.Note: All
SerialKinds are stable API now, exceptPolymorphicKind— we may want to expand it in the future.Generate Java 8's default method implementations in interfaces
... (truncated)
Changelog
Sourced from org.jetbrains.kotlinx:kotlinx-serialization-core's changelog.
1.8.1 / 2025-03-31
This release updates Kotlin version to 2.1.20, while also providing several important improvements and bugfixes.
Improvements
- Implemented encoding null in key and value of a map in Protobuf (#2910)
- Make type argument in JsonTransformingSerializer nullable (#2911)
- Use SPDX identifier in POMs (#2936) (thanks to Leon Linhart)
- Add watchosDeviceArm64 to Okio integration module (#2920) (thanks to Daniel Santiago)
- Update kotlinx-io version to 0.6.0 (#2933) (thanks to Piotr Krzemiński)
Bugfixes
- Fix incorrect enum coercion during deserialization from JsonElement (#2962)
- Supply proper equals(), hashCode(), and toString() for SerialDescriptor() wrapper (#2942)
- Do not encode empty packed collections in protobuf (#2907)
1.8.0 / 2025-01-06
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).
1.8.0-RC / 2024-12-10
This is a release candidate for the next version. It is based on Kotlin 2.1.0 and includes a few new features, as well as bugfixes and improvements:
@JsonIgnoreUnknownKeysannotationPreviously, only global setting
JsonBuilder.ignoreUnknownKeyscontrolled whether Json parser would throw exception if input contained a property that was not declared in a@Serializableclass. There were a lot of complaints that this setting is not flexible enough. To address them, we added new@JsonIgnoreUnknownKeysannotation that can be applied on a per-class basis. With this annotation, it is possible to allow unknown properties for annotated classes, while general decoding methods (such asJson.decodeFromStringand others) would still reject them for everything else. See details in the corresponding PR.Stabilization of
SerialDescriptorAPI and@SealedSerializationApiannotation
SerialDescriptor,SerialKind, and related API has been around for a long time and has proven itself useful. The main reason@ExperimentalSerializationApiwas on SerialDescriptor's properties is that we wanted to discourage people from subclassing it. Fortunately, Kotlin 2.1 provides a special mechanism for such a case — SubclassOptInRequired. Newkotlinx.serialization.SealedSerializationApiannotation designates APIs as public for use, but closed for implementation — the case for SerialDescriptor, which is a non-sealed interface for
... (truncated)
Commits
afd811fPrepare 1.8.1 release (#2965)2b653deMerge remote-tracking branch 'origin/master' into devab1cd2cUpdate forward compatibility notes (#2964)b26c67aTests for fixes for #KT-62522 and #KT-62215 (#2474)8853917Bump Kotlin to 2.1.20 (#2963)9adedb4Fix incorrect enum coercion during deserialization from JsonElement (#2962)438fb8eBencoding now supports all platforms (#2954)27e352dImplement additional compiler flags as per KT-75078 (#2946)f13da7eCheck the Gradle distribution checksum (#2935)1e54f4bSupply proper equals(), hashCode(), and toString() for SerialDescriptor() wra...- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)