Bump the versions group with 9 updates

[dependabot]

Bumps the versions group with 9 updates:

Package	From	To
ru.astrainteractive.klibs:mikro-core	1.8.7	1.8.8
ru.astrainteractive.klibs:mikro-platform	1.8.7	1.8.8
ru.astrainteractive.klibs:mikro-extensions	1.8.7	1.8.8
ru.astrainteractive.klibs:kstorage	3.1.2	3.1.3
ru.astrainteractive.klibs:kdi	1.4.7	1.4.8
com.russhwolf:multiplatform-settings	1.1.1	1.2.0
org.jetbrains.kotlinx:kotlinx-serialization-json	1.7.1	1.7.2
com.android.application	8.5.2	8.6.0
com.android.library	8.5.2	8.6.0

Updates ru.astrainteractive.klibs:mikro-core from 1.8.7 to 1.8.8

Commits

• 3b8ca01 build(deps): bump the versions group with 3 updates (#16)
• See full diff in compare view

Updates ru.astrainteractive.klibs:mikro-platform from 1.8.7 to 1.8.8

Commits

• 3b8ca01 build(deps): bump the versions group with 3 updates (#16)
• See full diff in compare view

Updates ru.astrainteractive.klibs:mikro-extensions from 1.8.7 to 1.8.8

Commits

• 3b8ca01 build(deps): bump the versions group with 3 updates (#16)
• See full diff in compare view

Updates ru.astrainteractive.klibs:mikro-platform from 1.8.7 to 1.8.8

Commits

• 3b8ca01 build(deps): bump the versions group with 3 updates (#16)
• See full diff in compare view

Updates ru.astrainteractive.klibs:mikro-extensions from 1.8.7 to 1.8.8

Commits

• 3b8ca01 build(deps): bump the versions group with 3 updates (#16)
• See full diff in compare view

Updates ru.astrainteractive.klibs:kstorage from 3.1.2 to 3.1.3

Commits

• e30eb58 Bump org.jetbrains.kotlin.multiplatform from 2.0.10 to 2.0.20 in the versions...
• See full diff in compare view

Updates ru.astrainteractive.klibs:kdi from 1.4.7 to 1.4.8

Commits

• 9c9a99c build(deps): bump org.jetbrains.kotlin.multiplatform from 2.0.10 to 2.0.20 in...
• See full diff in compare view

Updates com.russhwolf:multiplatform-settings from 1.1.1 to 1.2.0

Release notes

Sourced from com.russhwolf:multiplatform-settings's releases.

v1.2.0

• Update to Kotlin 2.0.0, Gradle 8.7, and Android Gradle Plugin 8.3.2
• Add alternative APIs to multiplatform-settings-serialization that don't require manually passing a serializer (#172). Thanks for contributions by @​findusl
• New experimental module multiplatform-settings-make-observable to convert non-observable settings to observable by wiring in callbacks when platform observability APIs don't exist (#155, #184). Thanks for contributions by @​psuzn.
• Add all supported targets to multiplatform-settings-coroutines and multiplatform-settings-serialization, including wasmJs.
• Add additional targets to multiplatform-settings-datastore based on multiplatform Datastore version 1.1.0
• Add wasmWasi support to multiplatform-settings, multiplatform-settings-test, and multiplatform-settings-make-observable.
• Add Stateflow analogs to existing Flow extensions in multiplatform-settings-coroutines. (#156)
• Make SettingsInitializer public so it's easier to configure custom android.startup initialization or write tests when using multiplatform-settings-no-arg
• Adjust KeychainSettings to avoid duplicated authentication requests (#193). Thanks for contributions by @​crysxd
• Modernize gradle and publication config. This shouldn't impact consumers, but please file an issue if you notice anything missing.

Changelog

Sourced from com.russhwolf:multiplatform-settings's changelog.

v1.2.0 (2024-09-01)

• Update to Kotlin 2.0.0, Gradle 8.7, and Android Gradle Plugin 8.3.2
• Add alternative APIs to multiplatform-settings-serialization that don't require manually passing a serializer ( #172). Thanks for contributions by @​findusl
• New experimental module multiplatform-settings-make-observable to convert non-observable settings to observable by wiring in callbacks when platform observability APIs don't exist (#155, #184). Thanks for contributions by @​psuzn.
• Add all supported targets to multiplatform-settings-coroutines and multiplatform-settings-serialization, including wasmJs.
• Add additional targets to multiplatform-settings-datastore based on multiplatform Datastore version 1.1.0
• Add wasmWasi support to multiplatform-settings, multiplatform-settings-test, and multiplatform-settings-make-observable.
• Add Stateflow analogs to existing Flow extensions in multiplatform-settings-coroutines. (#156)
• Make SettingsInitializer public so it's easier to configure custom android.startup initialization or write tests when using multiplatform-settings-no-arg
• Adjust KeychainSettings to avoid duplicated authentication requests (#193). Thanks for contributions by @​crysxd
• Modernize gradle and publication config. This shouldn't impact consumers, but please file an issue if you notice anything missing.

Commits

• 0f1f9ca Move group declaration to top-level build file
• 7e1511b Use only macos for deploy
• f524ffb Update readme to include new APIs in version 1.2
• fcca37a Changelog updates to prepare version 1.2
• 3ddda05 Update StateFlowExtensions Kdoc
• 3743c19 Change make-observable module to always use wrapper class, so implementatio...
• 87865d3 Make SharingStarted argument configurable in StateFlow extensions
• 4984dee Add keychain test targets
• d92d496 Extract separate convention plugin for modules without Android
• b63b20c Add test cases for nodejs via node-localstorage npm module
• Additional commits viewable in compare view

Updates org.jetbrains.kotlinx:kotlinx-serialization-json from 1.7.1 to 1.7.2

Release notes

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's releases.

1.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)

Changelog

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's changelog.

1.7.2 / 2024-08-28

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)

... (truncated)

Commits

• 8c84a5b Prepare 1.7.2 release (#2798)
• b3cfe56 Merge remote-tracking branch 'origin/master' into dev
• 550e1a8 Rework opt-ins in build scripts (#2794)
• e4fa8a3 Update Annotations.kt, fixed typo: RgpPixel -> RgbPixel (#2793)
• 62aa4bb Add serializer for kotlin.uuid.Uuid (#2744)
• 4646740 Prohibited using of zero and negative filed number in ProtoNumber and zero fi...
• 4ca05dd Update Kotlin to 2.0.20 (#2792)
• 35a9edc Migrate from kotlinOptions to compilerOptions (#2746)
• 0b5145c Improve readability of protobuf decoding exception messages (#2768)
• b931598 Remove redundant toString() (#2790)
• Additional commits viewable in compare view

Updates com.android.application from 8.5.2 to 8.6.0

Updates com.android.library from 8.5.2 to 8.6.0

Updates com.android.library from 8.5.2 to 8.6.0

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions