fix(deps): update androidx libraries

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
androidx.core:core-ktx (source)	1.17.0 → 1.18.0
androidx.activity:activity-compose (source)	1.12.4 → 1.13.0
androidx.core:core (source)	1.17.0 → 1.18.0

---

Configuration

📅 Schedule: Branch creation - "before 9am 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.

---

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

---

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

[claude]

Claude finished @renovate[bot]'s task in 44s —— View job

---

PR Review: fix(deps): update androidx libraries

• Gathering context and analyzing changes
• Reviewing the dependency updates
• Posting final review

---

Summary

This is a routine dependency update PR from Renovate bumping three AndroidX libraries:

Library	From	To
androidx.core:core	1.17.0	1.18.0
androidx.core:core-ktx	1.17.0	1.18.0
androidx.activity:activity-compose	1.12.4	1.13.0

Review

The changes are correct and safe to merge. These are minor version bumps in well-maintained AndroidX libraries with no breaking API changes expected.

One pre-existing issue worth noting (not introduced by this PR): androidx.core:core and androidx.core:core-ktx are both part of the same androidx.core release group and should always use the same version, but they are tracked via separate version refs in libs.versions.toml:

# gradle/libs.versions.toml:25
androidx-core = "1.18.0"   # used for androidx.core:core

# gradle/libs.versions.toml:52
coreKtx = "1.18.0"         # used for androidx.core:core-ktx

This creates a maintenance risk — a future Renovate update could update one but not the other, causing a version mismatch within the same artifact group. Consolidating them into a single version ref would prevent this drift. Fix this →

Verdict

✅ Approve to merge. The dependency updates are straightforward and low-risk.

[github-actions]

Qodana for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions