This repository was archived by the owner on Mar 6, 2025. It is now read-only.
[deps]: Update kotlin #309
Merged
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:
0.8.3->0.9.11.7.3->1.8.01.9.0->1.10.11.9.0->1.10.12024.11.00->2024.12.01Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
Kotlin/kotlinx-kover (org.jetbrains.kotlinx.kover)
v0.9.1===================
Kover Gradle Plugin
Features
#714Added ability to specify inclusion filter for source setsBugfixes
#716Fixed Gradle 9.0 migration issue#721Fixed creation of Kover Agent arguments filev0.9.0===================
Kover Gradle Plugin
Features
#645Added ability to supplement coverage values from external binary reports#673Implemented ability to specify instrumentation include filterBugfixes
#678Added USAGE attribute to all Kover configurations#666Replaced JaCoCo ant-calls with programmatic calls of JaCoCo's classesKover Aggregation Plugin
Features
Bugfixes
Kover CLI
Features
#677Implemented merging of binary reports in Kover CLI and Kover FeaturesBugfixes
#709Fixed offline instrumentation of jar filesKover JVM Agent
Bugfixes
Documentation
#660Fixed mistake in JVM agent docsKover Maven Plugin
Documentation
#658Fixed documentation about Maven plugin#701Fixed warning for empty Kotlin plugin configurationChangelog relative to version
0.9.0-RCKover Aggregation Plugin
Kover Maven Plugin
#701Fixed warning for empty Kotlin plugin configurationKover CLI
#709Fixed offline instrumentation of jar filesKotlin/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)
Kotlin/kotlinx.coroutines (org.jetbrains.kotlinx:kotlinx-coroutines-test)
v1.10.1Compare Source
v1.10.0Compare Source
Flow.any,Flow.all, andFlow.none(#4212). Thanks, @CLOVIS-AI!kotlinx-coroutines-debugandkotlinx-coroutines-corecode to avoid a split package between the two artifacts (#4247). Note that directly referencingkotlinx.coroutines.debug.AgentPremainmust now be replaced withkotlinx.coroutines.debug.internal.AgentPremain. Thanks, @sellmair!kotlinx-coroutines-debug, reducing the artifact size and simplifying the build configuration of client code. Thanks, @sellmair!NullPointerExceptionwhen using Java-deserializedkotlinx-coroutines-coreexceptions (#4291). Thanks, @AlexRiedler!CoroutineDispatcher.dispatchinstead of raising internal errors (#4091). Thanks, @zuevmaxim!Dispatchers.DefaultorDispatchers.IOtask after ayield()in rare scenarios (#4248).main()coroutine on Wasm/WASI from executing after adelay()call in some scenarios (#4239).runBlockingtasks on Kotlin/Native that arrive after therunBlockingblock was exited (#4245).Flowoperators sometimes resuming without taking cancellation into account (#4254). Thanks, @jxdabc!ThreadLocalvalues not to get cleaned when using non-CoroutineDispatchercontinuation interceptors (#4296).Configuration
📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (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.