chore(deps): update kotlin core dependencies #580
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.8.1->1.10.20.5.0->0.7.1-0.6.x-compat1.6.3->1.9.01.6.3->1.9.01.6.3->1.9.0Release Notes
Kotlin/kotlinx.coroutines (org.jetbrains.kotlinx:kotlinx-coroutines-core)
v1.10.2Compare Source
kotlinx-coroutines-debugJAR file including themodule-info.classfile twice, resulting in failures in various tooling (#4314). Thanks, @RyuNen344!Flow.stateInhanging when the scope is cancelled in advance or the flow is empty (#4322). Thanks, @francescotescari!.limitedParallelism(#4330) and during flow collection (#4272).runBlockingfailing to run its coroutine to completion in some cases if its JVM thread got interrupted (#4399).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).v1.9.0Compare Source
Features
limitedParallelismnow optionally accepts the name of the dispatcher view for easier debugging (#4023).Dispatchers.IOon the JVM when other standard dispatchers are accessed (#4166). Thanks, @metalhead8816!Flow<T>.chunked(size: Int): Flow<List<T>>operator that groups emitted values into groups of the given size (#1290).AutoCloseablenow (#4123).Fixes
hasNexton aChannel's iterator is idempotent (#4065). Thanks, @gitpaxultek!CoroutineScope()created without an explicit dispatcher usesDispatchers.Defaulton Native (#4074). Thanks, @whyoleg!Dispatchers.Mainfrom initializing when the Firebase dependency is used (#3914).runBlocking(#4134).MutextoSemaphore(#4176).asDeferredon aFuturemany times (#4156).Deprecations and promotions
BroadcastChannel-based API (#4197).kotlinx-coroutines-testAPI (#4198).Job.cancelFutureOnCompletion(#4173).CoroutineDispatcher.limitedParallelismto stable (#3864).CoroutineStart.ATOMICfromExperimentalCoroutinesApitoDelicateCoroutinesApi(#4169).CancellableContinuation.resumewith anonCancellationlambda to stable, providing extra arguments to the lambda (#4088).InternalForInheritanceCoroutinesApiopt-in (#3770).ExperimentalForInheritanceCoroutinesApiopt-in (#3770).Other
CoroutineStartandChannel-based API (#4147, #4148, #4167). Thanks, @globsterg!Job(#4053).Kotlin/kotlinx-datetime (org.jetbrains.kotlinx:kotlinx-datetime)
v0.7.1-0.6.x-compatv0.7.1kotlinx.datetime.Instantandkotlinx.datetime.Clocktype aliases to, respectively,kotlin.time.Instantandkotlin.time.Clockto make migration more convenient.v0.7.0-0.6.x-compatv0.7.0Breaking changes:
kotlinx.datetime.Instantandkotlinx.datetime.Clockin favor ofkotlin.time.Instant(#506). See https://github.com/Kotlin/kotlinx-datetime?tab=readme-ov-file#deprecation-of-instant for a description of what to do if this causes problems.LocalDateandLocalDateTimevalues on all platforms (#432).dayOfMonthtoday,monthNumbertomonth(#84).DayOfWeekandMonthno longer type aliases tojava.time.DayOfWeekandjava.time.Month(#96)."UTC"and not"Z"be the timezone identifier forTimeZone.UTC(#474)."z"inTimeZone.of, with the same meaning as"Z"(#529).DateTimeFormat-basedKSerializerimplementations for datetime entities, and change the default serializers to be based ontoString/parsepairs (#415).Additions:
java.io.Serializableimplementations for most of the entities in the library (#143). Thanks for spotting and fixing a potential vulnerability, @lukellmann!LocalDateRange, a range ofLocalDatevalues (#190). Thanks, @PeterAttardo!YearMonthandYearMonthRange(#457).Tweaks and fixes:
timeZoneId()directive (#444).timeZoneId()directive, allowing parsing values not present in the timezone database (#531).DateTimeComponentsvalue (#471).kotlinx.serialization.coreto be optional (#496).v0.6.2TimeSource.asClock(#164). Thanks, @hfhbd!NSDatetoInstantconversions (#427)DatePeriod.plusandDateTimePeriod.pluswith a warning (#381)Clock.asTimeSourcewith a warning (#372)module-infopreventing usingkotlinx.datetime.formattogether with JPMS (#438). Thanks, @cdelabou!v0.6.1DateTimeFormat(#405)/etc/localtimeset, defaulting toTimeZone.UTCas the system time zone (#426)v0.6.0Instantvalues without the second-of-minute component on the JVM and JS, fixing inconsistency with Native (#369)kotlinx-serializationclasses when serialization is not used (#336)Changelog relative to version 0.6.0-RC.2
Instantvalues without the second-of-minute component on the JVM and JS, fixing inconsistency with Native (#369)statusages to comply with Apple's new publishing requirements (#385)optionalis directly between numbers (#362)Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-properties)
v1.9.0==================
This release updates Kotlin version to 2.2.0, includes several bugfixes and provides serializers for kotlin.time.Instant.
Add kotlin.time.Instant serializers
Instant class was moved from kotlinx-datetime library to Kotlin standard library.
As a result, kotlinx-datetime 0.7.0 no longer has serializers for the Instant class.
To use new kotlin.time.Instant class in your @Serializable classes,
you can use this 1.9.0 kotlinx-serialization version (Kotlin 2.2 is required).
You can choose between default
InstantSerializerwhich uses its string representation,or specify
InstantComponentSerializerthat represents instant as its components.See details in the PR.
Other bugfixes
v1.8.1==================
This release updates Kotlin version to 2.1.20, while also providing several important improvements
and bugfixes.
Improvements
Bugfixes
v1.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).
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).
Configuration
📅 Schedule: Branch creation - "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 is behind base branch, 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.