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

fix(deps): update kotlin & dokka & compose compiler #655

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 13, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.jetbrains.kotlinx:kotlinx-datetime 0.5.0 -> 0.6.1 age adoption passing confidence
androidx.compose.compiler:compiler (source) 1.5.12 -> 1.5.15 age adoption passing confidence
org.jetbrains.kotlin.plugin.serialization (source) 1.9.23 -> 1.9.25 age adoption passing confidence
org.jetbrains.kotlin.multiplatform (source) 1.9.23 -> 1.9.25 age adoption passing confidence
org.jetbrains.kotlin.android (source) 1.9.23 -> 1.9.25 age adoption passing confidence
org.jetbrains.kotlin.jvm (source) 1.9.23 -> 1.9.25 age adoption passing confidence
org.jetbrains.kotlinx:kotlinx-serialization-json 1.6.3 -> 1.7.3 age adoption passing confidence
org.jetbrains.kotlinx:kotlinx-serialization-core 1.6.3 -> 1.7.3 age adoption passing confidence
org.jetbrains.kotlin:kotlin-reflect (source) 1.9.23 -> 1.9.25 age adoption passing confidence
org.jetbrains.kotlin:kotlin-stdlib-jdk8 (source) 1.9.23 -> 1.9.25 age adoption passing confidence
org.jetbrains.kotlin:kotlin-gradle-plugin (source) 1.9.23 -> 1.9.25 age adoption passing confidence

Release Notes

Kotlin/kotlinx-datetime (org.jetbrains.kotlinx:kotlinx-datetime)

v0.6.1

  • Prohibit parsing non-ASCII digits as numbers in DateTimeFormat (#​405)
  • More accurately determine which files represent time zones and which don't on Linux and Darwin (#​395)
  • Fix a regression that occasionally considered the right boundary of a time overlap to be a part of it on Native (#​399)
  • Introduce various small improvements to the timezone handling on Windows (#​390)
  • On Linux, allow not having any /etc/localtime set, defaulting to TimeZone.UTC as the system time zone (#​426)

v0.6.0

  • Introduce the widely requested API for locale-invariant parsing and formatting (#​343)
  • Completely overhaul the KDoc-based documentation (#​347)
  • Breaking change: forbid parsing Instant values without the second-of-minute component on the JVM and JS, fixing inconsistency with Native (#​369)
  • Breaking change: use the fully qualified name of classes in the JSON serializers (#​308)
  • Fix Proguard emitting warning about missing kotlinx-serialization classes when serialization is not used (#​336)
  • Reimplement the timezone database handling for Native targets from scratch (#​286, #​327)
  • Support Android NDK targets (#​344)
  • Small tweaks and fixes.
Changelog relative to version 0.6.0-RC.2
  • Completely overhaul the KDoc-based documentation (#​347)
  • Breaking change: forbid parsing Instant values without the second-of-minute component on the JVM and JS, fixing inconsistency with Native (#​369)
  • Improve error descriptiveness in some cases (#​360, #​371)
  • Remove stat usages to comply with Apple's new publishing requirements (#​385)
  • Fix parsing of formats where optional is directly between numbers (#​362)
  • Forbid empty and duplicate month, day-of-week, and AM/PM marker names in datetime formats (#​362)
JetBrains/kotlin (org.jetbrains.kotlin.plugin.serialization)

v1.9.25: Kotlin 1.9.25

Note: This is a technical release for IntelliJ IDEA.

Changelog

Tools. JPS
  • KT-69204 Generate lookups in dumb mode for compatibility with ref index

v1.9.24: 1.9.24

Changelog

Backend. Wasm
  • KT-64890 K/Wasm compiler crash with external class and Kodein
Compiler
  • KT-65235 JDK 21 might lead to change in overloads resolution
  • KT-66768 K1: False positive UNRESOLVED_REFERENCE in super.getFirst/getLast call
Native
  • KT-67218 Native: nested classes in kx.serialization ProtoBuf produce empty array for release binary
Tools. Gradle
  • KT-67139 Build reports can be overridden
  • KT-67138 Json report is empty for incremental compilation
Tools. Gradle. Multiplatform
  • KT-67127 KMP: IDE Dependency Resolver for CInterops reports errors on linux and windows machines
  • KT-66514 Don't get output file from Cinterop task for IDE Import if host os doesn't support it
Tools. JPS
  • KT-65043 JPS dumb mode should respect maps needed for the compiler
Tools. Wasm
  • KT-67785 Kotlin/Wasm: Node.JS 22 does not need experimental-wasm-gc flag anymore
  • KT-65864 K/Wasm: update Node.js to 22.x
Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)

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)

v1.7.1

==================

This is a bugfix release that aims to fix missing kotlinx-serialization-hocon artifact.
It also contains experimental integration with kotlinx-io library.
Kotlin 2.0.0 is used by default.

Fixed HOCON publication

Sadly, 1.7.0 release was published incomplete: kotlinx-serialization-hocon artifact is missing from 1.7.0 and 1.7.0-RC releases.
This release fixes this problem and now kotlinx-serialization-hocon is 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-io is 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-io coordinates.
Integration artifact provides functions similar to existing Okio integration: encodeToSink, decodeFromSource, and decodeSourceToSequence.
Check out the PR for more details.

Other bugfixes

  • Prohibited use of elements other than JsonObject in JsonTransformingSerializer with polymorphic serialization (#​2715)

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 classDiscriminatorMode property in JsonBuilder is marked as experimental,
as it should have been when it was introduced (#​2680).


Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@renovate renovate bot requested a review from a team as a code owner May 13, 2024 02:17
@renovate renovate bot added chore Maintanance update skip-changelog labels May 13, 2024
@renovate renovate bot force-pushed the renovate/kotlin-and-dokka-and-compose-compiler branch from 7e8d018 to f9744be Compare May 14, 2024 20:25
@renovate renovate bot force-pushed the renovate/kotlin-and-dokka-and-compose-compiler branch from f9744be to 4d9a93d Compare June 6, 2024 15:10
@renovate renovate bot force-pushed the renovate/kotlin-and-dokka-and-compose-compiler branch from 4d9a93d to 220b055 Compare June 25, 2024 19:45
@renovate renovate bot force-pushed the renovate/kotlin-and-dokka-and-compose-compiler branch from 220b055 to 93db902 Compare July 19, 2024 11:35
@renovate renovate bot force-pushed the renovate/kotlin-and-dokka-and-compose-compiler branch from 93db902 to 21f94d3 Compare August 8, 2024 13:50
@renovate renovate bot force-pushed the renovate/kotlin-and-dokka-and-compose-compiler branch from 21f94d3 to 747efcb Compare August 20, 2024 15:09
@renovate renovate bot force-pushed the renovate/kotlin-and-dokka-and-compose-compiler branch from 747efcb to 46a3019 Compare August 28, 2024 18:13
@renovate renovate bot force-pushed the renovate/kotlin-and-dokka-and-compose-compiler branch from 46a3019 to e623224 Compare September 19, 2024 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Maintanance update skip-changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants