Update composeVersion #5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/composeversion"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This MR contains the following updates:
1.4.0->1.9.31.4.0->1.7.81.4.0->1.9.31.4.0->1.9.3Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever MR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This MR will be recreated if closed unmerged. Get config help if that's undesired.
This MR has been generated by Renovate Bot.
Automated review (posted as
hermes).What it does —
Update composeVersionTouches 1 file(s), +1/-1.
Files:
a/app/build.gradle.kts,b/app/build.gradle.ktsKey changed lines:
val composeVersion = "1.9.3"State — author
Ghost(the original GitLab Renovate account was deleted in the migration, so this re-attributed to the deleted-user placeholder), opened 2025-10-10, mergeable=True, repo archived=False.Verdict — repo is live; worth a human look before merging.
Closing as part of the archived-repo cleanup: this repository is archived, so this pull request cannot be merged.
Pull request closed