Updated Reaktive to 2.1.0 and coroutines to 1.8.0

[arkivanov]

Also removed related workarounds that are no longer needed.

Summary by CodeRabbit

• Chores
  • Updated kotlinxCoroutines to version "1.8.0" and reaktive to version "2.1.0" for improved performance and stability.
• Refactor
  • Simplified the setup for Reaktive by using setupMultiplatform() directly, enhancing maintainability.
• Bug Fixes
  • Fixed an issue related to kotlinx.coroutines by removing a specific workaround.
  • Addressed a publication check oversight by reintroducing lifecycle-reaktive to the checks.

[coderabbitai]

Walkthrough

The recent updates involve upgrading dependencies to their stable versions, simplifying configurations, and reintroducing a previously excluded implementation. Notably, kotlinxCoroutines and reaktive dependencies were updated to their latest stable releases. Additionally, unnecessary implementations and platform-specific configurations were removed to streamline the setup, enhancing the overall project structure and maintenance.

Changes

Files	Change Summary
deps.versions.toml	Updated kotlinxCoroutines to "1.8.0" and reaktive to "2.1.0"
lifecycle-coroutines/build.gradle.kts	Removed implementation of atomicfu as a workaround for an issue
lifecycle-reaktive/build.gradle.kts	Simplified setup by removing platform-specific configurations and using setupMultiplatform() directly
tools/check-publication/build.gradle.kts	Reintroduced lifecycle-reaktive implementation previously excluded

🐰✨

In the realm of code, where the bits do hop,
Upgrades and cleans, our work, non-stop.
Dependencies fresh, the structure now sleek,
A rabbit's touch, for the changes we seek.
🌟📦🚀
Celebrate we do, with a hop and a leap,
In our digital burrow, the code runs deep.
🐾💻🎉

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

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>.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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/coderabbit-overrides.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.

[coderabbitai]

Actionable comments posted: 0

Actionable comments outside the diff hunks (1)

lifecycle-coroutines/build.gradle.kts (1)

Line range hint 1-1: The removal of "org.jetbrains.kotlinx:atomicfu:0.23.1" is a positive change, indicating that previous issues have been resolved.

Ensure that the removal of this dependency does not introduce any regressions.

Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 14e8405 and 799dc04.

Files selected for processing (4)

• deps.versions.toml (2 hunks)
• lifecycle-coroutines/build.gradle.kts (1 hunks)
• lifecycle-reaktive/build.gradle.kts (1 hunks)
• tools/check-publication/build.gradle.kts (1 hunks)

Additional comments not posted (3)

lifecycle-reaktive/build.gradle.kts (1)

12-12: The simplification to call setupMultiplatform() directly is a good improvement.

Ensure that all necessary configurations previously handled in a platform-specific manner are still correctly configured.

tools/check-publication/build.gradle.kts (1)

33-33: Reintroducing com.arkivanov.essenty:lifecycle-reaktive into publication checks is a positive step.

Verify that this reintroduction aligns with the project's criteria for publication checks.

deps.versions.toml (1)

6-6: Updating the versions of kotlinxCoroutines to "1.8.0" and reaktive to "2.1.0" aligns with best practices for dependency management.

Ensure that these updates do not introduce any compatibility issues with the rest of the project.

Also applies to: 15-15