Update dependency org.jetbrains.kotlinx:kotlinx-coroutines-core to v1.11.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
org.jetbrains.kotlinx:kotlinx-coroutines-core	1.7.3 → 1.11.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

Kotlin/kotlinx.coroutines (org.jetbrains.kotlinx:kotlinx-coroutines-core)

v1.11.0

Compare Source

Various

• Kotlin was updated to 2.2.20 (#​4545).
• Improved the published jar files (#​3842, #​4599).
• Various documentation improvements, including complete rewrites of structured concurrency and error handling-related KDoc (#​4433, #​4596).

Breaking changes and deprecations

• Moved Promise-related functions from JS and Wasm/JS to the new web target. On Wasm/JS, this is a breaking change. Before the change, Promise on Wasm/JS could work with arbitrary Kotlin types, but now, only JsAny subtypes are accepted (#​4563).
• Changed handling of coroutine exceptions that can't be propagated on JS and Wasm/JS. B
  efore, exceptions were logged, but now, they are reported to the JS runtime (#​4451, #​4631).
• Deprecated using CoroutineDispatcher as the coroutine context key; now, ContinuationInterceptor has to be used instead (#​4333).
• Advanced the deprecation levels on kotlinx-coroutines-test APIs (#​4604).
• Added lint functions that mark passing a Job to coroutine builders as deprecated (#​4435).

Bug fixes and improvements

• Added a callsInPlace(EXACTLY_ONCE) contract to runBlocking in code shared between JVM and Native (#​4368).
• Added a callsInPlace(EXACTLY_ONCE) contract to suspendCancellableCoroutine (#​4574).
• Fixed flowOn incorrectly handling ThreadContextElement updates (#​4403).
• Fixed exceptions in user-supplied Thread.UncaughtExceptionHandler instances causing the internal coroutines machinery to fail (#​4516).
• Fixed CoroutineDispatcher.asScheduler in the RxJava integration not cancelling outstanding work when a Worker gets cancelled, which led to memory leaks in some scenarios (#​4615).
• Fixed SharedFlow entering an invalid state when a subscriber and an emitter are cancelled simultaneously (#​4583).
• Fixed an R8 optimization leading to shareIn/stateIn coroutines getting garbage-collected (#​4646). Thanks, @​solevic!

Small additions

• Added CompletableDeferred.asDeferred for obtaining a read-only Deferred view (#​4408).
• Added SharedFlow.asFlow for obtaining a Flow view with hidden hot flow semantics (#​4530). Thanks, @​g000sha256!
• Added a StateFlow.collectLatest overload returning Nothing to assist with finding unreachable code (#​4454).
• Added ReceiveChannel.consumeTo for consuming a ReceiveChannel into a MutableCollection (#​4520).
• Added a StateFlow<T>.onSubscription overload returning a StateFlow<T>, similar to SharedFlow<T>.onSubscription returning SharedFlow<T> (#​4275). Thanks, @​xit0c!
• Added terminal Flow operators for collecting a Flow to a Map (#​1541).

Changelog relative to version 1.11.0

No changes, only the version is increased.

v1.10.2

Compare Source

• Fixed the kotlinx-coroutines-debug JAR file including the module-info.class file twice, resulting in failures in various tooling (#​4314). Thanks, @​RyuNen344!
• Fixed Flow.stateIn hanging when the scope is cancelled in advance or the flow is empty (#​4322). Thanks, @​francescotescari!
• Improved handling of dispatcher failures in .limitedParallelism (#​4330) and during flow collection (#​4272).
• Fixed runBlocking failing to run its coroutine to completion in some cases if its JVM thread got interrupted (#​4399).
• Small tweaks, fixes, and documentation improvements.

v1.10.1

Compare Source

• Fixed binary incompatibility introduced for non-JVM targets in #​4261 (#​4309).

v1.10.0

Compare Source

• Kotlin was updated to 2.1.0 (#​4284).
• Introduced Flow.any, Flow.all, and Flow.none (#​4212). Thanks, @​CLOVIS-AI!
• Reorganized kotlinx-coroutines-debug and kotlinx-coroutines-core code to avoid a split package between the two artifacts (#​4247). Note that directly referencing kotlinx.coroutines.debug.AgentPremain must now be replaced with kotlinx.coroutines.debug.internal.AgentPremain. Thanks, @​sellmair!
• No longer shade byte-buddy in kotlinx-coroutines-debug, reducing the artifact size and simplifying the build configuration of client code. Thanks, @​sellmair!
• Fixed NullPointerException when using Java-deserialized kotlinx-coroutines-core exceptions (#​4291). Thanks, @​AlexRiedler!
• Properly report exceptions thrown by CoroutineDispatcher.dispatch instead of raising internal errors (#​4091). Thanks, @​zuevmaxim!
• Fixed a bug that delayed scheduling of a Dispatchers.Default or Dispatchers.IO task after a yield() in rare scenarios (#​4248).
• Fixed a bug that prevented the main() coroutine on Wasm/WASI from executing after a delay() call in some scenarios (#​4239).
• Fixed scheduling of runBlocking tasks on Kotlin/Native that arrive after the runBlocking block was exited (#​4245).
• Fixed some terminal Flow operators sometimes resuming without taking cancellation into account (#​4254). Thanks, @​jxdabc!
• Fixed a bug on the JVM that caused coroutine-bound ThreadLocal values not to get cleaned when using non-CoroutineDispatcher continuation interceptors (#​4296).
• Small tweaks, fixes, and documentation improvements.

v1.9.0

Compare Source

Features

• Wasm/WASI target support (#​4064). Thanks, @​igoriakovlev!
• limitedParallelism now optionally accepts the name of the dispatcher view for easier debugging (#​4023).
• No longer initialize Dispatchers.IO on the JVM when other standard dispatchers are accessed (#​4166). Thanks, @​metalhead8816!
• Introduced the Flow<T>.chunked(size: Int): Flow<List<T>> operator that groups emitted values into groups of the given size (#​1290).
• Closeable dispatchers are instances of AutoCloseable now (#​4123).

Fixes

• Calling hasNext on a Channel's iterator is idempotent (#​4065). Thanks, @​gitpaxultek!
• CoroutineScope() created without an explicit dispatcher uses Dispatchers.Default on Native (#​4074). Thanks, @​whyoleg!
• Fixed a bug that prevented non-Android Dispatchers.Main from initializing when the Firebase dependency is used (#​3914).
• Ensured a more intuitive ordering of tasks in runBlocking (#​4134).
• Forbid casting a Mutex to Semaphore (#​4176).
• Worked around a stack overflow that may occur when calling asDeferred on a Future many times (#​4156).

Deprecations and promotions

• Advanced the deprecation levels for BroadcastChannel-based API (#​4197).
• Advanced the deprecation levels for the old kotlinx-coroutines-test API (#​4198).
• Deprecated Job.cancelFutureOnCompletion (#​4173).
• Promoted CoroutineDispatcher.limitedParallelism to stable (#​3864).
• Promoted CoroutineStart.ATOMIC from ExperimentalCoroutinesApi to DelicateCoroutinesApi (#​4169).
• Promoted CancellableContinuation.resume with an onCancellation lambda to stable, providing extra arguments to the lambda (#​4088).
• Marked the classes and interfaces that are not supposed to be inherited from with the new InternalForInheritanceCoroutinesApi opt-in (#​3770).
• Marked the classes and interfaces inheriting from which is not stable with the new ExperimentalForInheritanceCoroutinesApi opt-in (#​3770).

Other

• Kotlin was updated to 2.0 (#​4137).
• Reworked the documentation for CoroutineStart and Channel-based API (#​4147, #​4148, #​4167). Thanks, @​globsterg!
• Simplified the internal implementation of Job (#​4053).
• Small tweaks, fixes, and documentation improvements.

v1.8.1

Compare Source

• Remove the @ExperimentalTime annotation from usages of TimeSource (#​4046). Thanks, @​hfhbd!
• Introduce a workaround for an Android bug that caused an occasional NullPointerException when setting the StateFlow value on old Android devices (#​3820).
• No longer use kotlin.random.Random as part of Dispatchers.Default and Dispatchers.IO initialization (#​4051).
• Flow.timeout throws the exception with which the channel was closed (#​4071).
• Small tweaks and documentation fixes.

Changelog relative to version 1.8.1-Beta

• Flow.timeout throws the exception with which the channel was closed (#​4071).
• Small documentation fixes.

v1.8.0

Compare Source

• Implement the library for the Web Assembly (Wasm) for JavaScript (#​3713). Thanks @​igoriakovlev!
• Major Kotlin version update: was 1.8.20, became 1.9.21.
• On Android, ensure that Dispatchers.Main != Dispatchers.Main.immediate (#​3545, #​3963).
• Fixed a bug that caused Flow operators that limit cancel the upstream flow to forget that they were already finished if there is another such operator upstream (#​4035, #​4038)
• kotlinx-coroutines-debug is published with the correct Java 9 module info (#​3944).
• kotlinx-coroutines-debug no longer requires manually setting DebugProbes.enableCoroutineCreationStackTraces to false, it's the default (#​3783).
• kotlinx-coroutines-test: set the default timeout of runTest to 60 seconds, added the ability to configure it on the JVM with the kotlinx.coroutines.test.default_timeout=10s (#​3800).
• kotlinx-coroutines-test: fixed a bug that could lead to not all uncaught exceptions being reported after some tests failed (#​3800).
• delay(Duration) rounds nanoseconds up to whole milliseconds and not down (#​3920). Thanks @​kevincianfarini!
• Dispatchers.Default and the default thread for background work are guaranteed to use the same context classloader as the object containing it them (#​3832).
• It is guaranteed that by the time SharedFlow.collect suspends for the first time, it's registered as a subscriber for that SharedFlow (#​3885). Before, it was also true, but not documented.
• Atomicfu version is updated to 0.23.1, and Kotlin/Native atomic transformations are enabled, reducing the footprint of coroutine-heavy code (#​3954).
• Added a workaround for miscompilation of withLock on JS (#​3881). Thanks @​CLOVIS-AI!
• Small tweaks and documentation fixes.

Changelog relative to version 1.8.0-RC2

• kotlinx-coroutines-debug no longer requires manually setting DebugProbes.enableCoroutineCreationStackTraces to false, it's the default (#​3783).
• Fixed a bug that caused Flow operators that limit cancel the upstream flow to forget that they were already finished if there is another such operator upstream (#​4035, #​4038)
• Small documentation fixes.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}