Update kotlin #15
Open
Update kotlin #15
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
3b9e92b to
759f998
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
759f998 to
4aae55c
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
4aae55c to
12235b1
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
3 times, most recently
from
fe41d65 to
b31810f
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
b31810f to
e47353c
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
2 times, most recently
from
6c16aa4 to
76af3b1
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
76af3b1 to
5b5cbbb
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
5b5cbbb to
1718b7b
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
2 times, most recently
from
417affb to
9a53f55
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
2 times, most recently
from
4f0a6f9 to
cf9deea
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
cf9deea to
b602068
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
2 times, most recently
from
99143ab to
6da42c0
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
6da42c0 to
45dbb33
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
45dbb33 to
19aaa8f
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
3 times, most recently
from
61fc9c1 to
6a1723f
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
6a1723f to
4154ee6
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
2 times, most recently
from
432940b to
7e9f2d4
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
7e9f2d4 to
cea2186
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
cea2186 to
dd2263f
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
dd2263f to
d215bdf
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
d215bdf to
e2a60b2
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
2 times, most recently
from
9f9e44f to
af4bcf2
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
2 times, most recently
from
88ab7ef to
98be4ef
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
2 times, most recently
from
7db282d to
cf35dbc
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
2 times, most recently
from
37a3899 to
3dd37fd
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
3dd37fd to
52ea979
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
52ea979 to
1b1bb27
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
1b1bb27 to
938b2f6
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
938b2f6 to
55395a3
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
55395a3 to
798c897
Compare
renovate
bot
force-pushed
the
renovate/kotlin
branch
from
798c897 to
2233a09
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.9.22-1.0.16->2.1.0-1.0.291.4.1->1.8.00.3.5->0.3.81.1.2->2.1.01.7.3->1.10.11.7.3->1.10.11.7.3->1.10.11.7.3->1.10.11.9.22->2.1.01.9.22->2.1.01.9.22->2.1.0Release Notes
google/ksp (com.google.devtools.ksp:com.google.devtools.ksp.gradle.plugin)
v2.1.0-1.0.29Compare Source
Updates
Contributors
Thanks to everyone who reported bugs and participated in discussions!
v2.1.0-1.0.28Compare Source
What's Changed
Full Changelog: google/ksp@2.1.0-RC2-1.0.28...2.1.0-1.0.28
v2.0.21-1.0.28Compare Source
Updates
Contributors
Thanks to @GeorgCantor and everyone who reported bugs and participated in discussions!
v2.0.21-1.0.27Compare Source
Bugs Fixed
Contributors
Thanks to @jonamireh, @kuanyingchou, @martinbonnin, @pablobaxter, @scott-pollom, and everyone who reported bugs and participated in discussions!
v2.0.21-1.0.26Compare Source
Bugs Fixed
Full Changelog: google/ksp@911690b...2.0.21-1.0.26
Contributors
Thanks to @ansman, @asapha, @kaeawc, @kuanyingchou, @scott-pollom, and everyone who reported bugs and participated in discussions!
v2.0.21-1.0.25Compare Source
What's Changed
Full Changelog: google/ksp@2.0.21-RC-1.0.25...2.0.21-1.0.25
v2.0.20-1.0.25Compare Source
Bugs Fixed
Inlined JVM name is not correct #1493
[KSP2] NullPointerException when getting name of nested annotation #1963
[KSP2] The status was unresolved for FirSimpleFunctionImpl #1938
[KSP2] Class values in type annotations get resolved to error type #1933
[KSP2] Comparing KSType leads to exception #1918
[KSP2] Can't find values in repeatable annotations #1883
incremental: aggregating outputs should always be invalidated #2027
[KSP2] Not yet implemented: KSValueArgumentLiteImpl.getLocation #2048
[KSP2] Not yet implemented: KSValueArgumentImpl.getParent #2049
getSymbolsWithAnnotation returns copy function from data class #1996
[KSP2] Annotations got use-site target when there are none specified #1882
getting null pointer exception #1929
[KSP2] Calling getDeclarationsInSourceOrder throws KotlinIllegalStateExceptionWithAttachments #1930
[KSP2] A failure occurred while executing com.google.devtools.ksp.gradle.KspAAWorkerAction #1941
KSP2: Resolver.getJvmNames doesn't work for inline and internal classes #1640
kspCaches don't work together with Gradle build cache #2042
Contributors
Thank you so much! @ansman, @kuanyingchou
Full Changelog: google/ksp@2.0.20-1.0.24...2.0.20-1.0.25
v2.0.20-1.0.24Compare Source
What's Changed
v2.0.10-1.0.24Compare Source
What's Changed
v2.0.0-1.0.24Compare Source
What's Changed
#2013 Handle edge cases of KtAnnotated.annotations
#2009 Fix :kotlin-analysis-api:shadowJar failing on Windows
#2006 Use symbol-processing-aa-embeddable in Gradle
Bugs Fixed
#1956 IllegalAccessError in Dagger with KSP2.0.0-1.0.22 and KSP2
#1998 KSP2 version 2.0.0-1.0.23 crashes on Moshi codegen with NoSuchElementException: Collection contains no element matching the predicate.
Full Changelog: google/ksp@e880744...c63864c
v2.0.0-1.0.23Compare Source
Issues fixed
v2.0.0-1.0.22Compare Source
Important Changes
KSErrorType.toString()now contains the reference name it was tried to be resolved, and thereforeKSErrorTypeis no longer a singleton. Processors relying on equality checks of that (in contrast of usingKSType.isError) will need to be updated accordingly.Issues Fixed
#1908 KSP2: Calling KSP2 in programs does not appear to work on macOS or Windows
#1917 KSP2's symbol-processing-aa-embeddable artifact exposes an unresolvable pre-release kotlin 2.0.20 dependency
#1911 NoSuchMethodError when running KSP2 with Dagger (KSP 2.0.0-1.0.21)
#1909 KSP2: default annotation arguments no longer work in 1.0.21
#1232 Expose simple names on a missing types's synthetic declaration
#1857 [KSP2] Modifiers are missing for property accessors
#1924 [KSP2] Type arg becomes '*' after calling KSType.replace() with an error type
#1948 KSP2 default annotation KClass values for built-in types use java.lang.* versions
What's Changed
Full Changelog: google/ksp@2.0.0-1.0.21...2.0.0-1.0.22
v2.0.0-1.0.21Compare Source
This release brings mostly bug fixes into KSP2 beta
Users are encouraged to try out KSP2 beta.
new feature
expose an API in Resolver to retrieve the module name for handling mangling of internal members #1621
issues fixed
v1.9.25-1.0.20Compare Source
KSP 1.0.20 for Kotlin 1.9.25
v1.9.24-1.0.20Compare Source
KSP 1.0.20 for kotlin compiler version 1.9.24
v1.9.23-1.0.20Compare Source
KSP1 issues fixed
KSP2 issues fixed
v1.9.23-1.0.19New APIs
SymbolProcessorEnvironment.kspVersionCodeGenerator.associateWithFunctionsandCodeGenerator.associateWithPropertiesIssues fixed in KSP2
Issues fixed in KSP Gradle Plugin
Known issues
v1.9.22-1.0.17Compare Source
Issues fixed
Resolver#getJvmCheckedExceptionresults in<ERROR TYPE>when throwing type variable. #1460$in name arenullwhen used in Kotlin source #1671Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)
v1.8.0==================
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 ifinput 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 as
Json.decodeFromStringand others) would still reject them for everything else.See details in the corresponding PR.
Stabilization of
SerialDescriptorAPI and@SealedSerializationApiannotationSerialDescriptor,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 discouragepeople from subclassing it.
Fortunately, Kotlin 2.1 provides a special mechanism for such a
case — SubclassOptInRequired.
New
kotlinx.serialization.SealedSerializationApiannotation designates APIsas 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 of
SerialDescriptorand its builders API without the need to opt-in into experimentalserialization 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
TL;DR This change ensures better binary compatibility in the future for library. You should not experience any
difference from it.
kotlinx.serialization library contains a lot of interfaces with default method implementations. Historically, Kotlin
compiled a synthetic
DefaultImplsclass for them.Starting from Kotlin 1.4,
it was possible to compile them using as Java 8's
defaultmethods to ensurethat new methods can still be added to interfaces without the need for implementors to recompile.
To preserve binary compatibility with existing clients, a special
all-compatbilitymode is supported in compilerto generate both
defaultmethods and syntheticDefaultImplsclass.Now, kotlinx.serialization finally makes use of this
all-compatibilitymode,which potentially allows us to add new methods to interfaces such as
SerialDescriptor,Encoder,Decoder, etc.,without breaking existing clients. This change is expected to have no effect on existing clients, and no action from
your side is required.
Note that Kotlin 2.2 plans to enable
all-compatibilitymode by default.
Other bugfixes and improvements
is set to NONE (#2833)
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.
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:
@CborLabelannotation andpreferCborLabelsOverNamesflag.encode*Tagsandverify*Tagsset of flagsuseDefiniteLengthEncoding. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported.alwaysUseByteStringflag.Since there are quite a lot of flags now, they were restructured to a separate
CborConfigurationclass, similarly toJsonConfiguration.It is possible to retrieve this configuration from
CborEncoder/CborDecoderinterfaces 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.CoseCompliantinstance.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
@KeepGeneratedSerializerannotation 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.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@Serializableclasses.Note that for now, serializer should be provided manually with
@Contextualannotation.Plugin will be able to automatically insert
Uuidserializer in Kotlin 2.1.0.See more details in the corresponding PR.
Other bugfixes and improvements
v1.7.1==================
This is a bugfix release that aims to fix missing
kotlinx-serialization-hoconartifact.It also contains experimental integration with
kotlinx-iolibrary.Kotlin 2.0.0 is used by default.
Fixed HOCON publication
Sadly, 1.7.0 release was published incomplete:
kotlinx-serialization-hoconartifact is missing from 1.7.0 and 1.7.0-RC releases.This release fixes this problem and now
kotlinx-serialization-hoconis 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-iois 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-iocoordinates.Integration artifact provides functions similar to existing Okio integration:
encodeToSink,decodeFromSource, anddecodeSourceToSequence.Check out the PR for more details.
Other bugfixes
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
classDiscriminatorModeproperty inJsonBuilderis marked as experimental,as it should have been when it was introduced (#2680).
v1.6.3==================
This release provides a couple of new features and uses Kotlin 1.9.22 as default.
Class discriminator output mode
Class discriminator provides information for serializing and deserializing polymorphic class hierarchies.
In case you want to encode more or less information for various third party APIs about types in the output, it is possible to control
addition of the class discriminator with the
JsonBuilder.classDiscriminatorModeproperty.For example,
ClassDiscriminatorMode.NONEdoes not add class discriminator at all, in case the receiving party is not interested in Kotlin types.You can learn more about this feature in the documentation and corresponding PR.
Other features
Bugfixes and improvements
v1.6.2==================
This is a patch release accompanying Kotlin 1.9.21. It also provides additional targets that were not available in 1.6.1:
wasm-wasi and (deprecated) linuxArm32Hfp.
v1.6.1==================
This release uses Kotlin 1.9.20 by default, while upcoming 1.9.21 is also supported.
Trailing commas in Json
Trailing commas are one of the most popular non-spec Json variations.
A new configuration flag,
allowTrailingComma, makes Json parser accept them instead of throwing an exception.Note that it does not affect encoding, so kotlinx.serialization always produces Json without trailing commas.
See details in the corresponding PR
Support of WasmJs target
Kotlin/Wasm has been experimental for some time and gained enough maturity to be added to the kotlinx libraries.
Starting with 1.6.1, kotlinx.serialization provides a wasm-js flavor, so your projects with Kotlin/Wasm can have even more
functionality.
As usual, just add serialization dependencies to your build
and declare wasmJs target.
Please remember that Kotlin/Wasm is still experimental, so changes are expected.
Bugfixes and improvements
v1.6.0==================
This release contains all features and bugfixes from 1.6.0-RC plus some bugfixes on its own (see below).
Kotlin 1.9.0 is used as a default, while 1.9.10 is also supported.
Bugfixes
v1.5.1==================
This release contains an important Native targets overhaul, as well as numerous enhancements and bugfixes.
Kotlin 1.8.21 is used by default.
New set of Native targets
The official Kotlin target support policy has recently been published
describing new target policy: each target belongs to a certain tier, and different tiers have different stability guarantees.
The official recommendation for library authors is to support targets up to Tier 3,
and kotlinx.serialization now follows it.
It means that in this release, there are a lot of new targets added from this tier,
such as
androidNativeX86orwatchosDeviceArm64.Note that since they belong to Tier 3, they're not auto-tested on CI.
kotlinx.serialization also ships some deprecated Kotlin/Native targets that do not belong to any tier (e.g.
iosArm32,mingwX86).We'll continue to release them, but we do not provide support for them, nor do we plan to add new targets from the deprecated list.
Improvements in Json elements
There are two new function sets that should make creating raw Json elements easier.
First one contains overloads for
JsonPrimitiveconstructor-like functionthat accept unsigned types:
JsonPrimitive(1u).Second one adds new
addAllfunctions toJsonArrayBuilderto be used with collectionsof numbers, booleans or strings:
buildJsonArray { addAll(listOf(1, 2, 3)) }Both were contributed to us by aSemy.
Other enhancements
Configuration
📅 Schedule: Branch creation - "* 0-3 * * *" (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.
This PR was generated by Mend Renovate. View the repository job log.