build: update dependencies

[dkhawk]

Automated dependency update.

Changes:

• kotlin 2.2.21 -> 2.3.10
• androidx.activity:activity-compose 1.12.3 -> 1.12.4
• androidx.compose:compose-bom 2026.01.01 -> 2026.02.00
• com.android.tools.lint:lint 32.0.0 -> 32.0.1

[googlemaps-bot]

Code Coverage

Overall Project	40.1%	🍏

There is no coverage information present for the Files changed

[kikoso]

@dkhawk , we are increasing the dependency of the android-maps-utils directly, is this intended?

[dkhawk]

@dkhawk , we are increasing the dependency of the android-maps-utils directly, is this intended?

No. That was not intended. I am working on a tool to help with version updates. It should be fixed now.

[dkhawk]

@dkhawk , we are increasing the dependency of the android-maps-utils directly, is this intended?

No. That was not intended. I am working on a tool to help with version updates. It should be fixed now.

This was due to testing cascading updates. It should be fixed

[kikoso]

LGTM

[kikoso]

@dkhawk , one more comment: should the title of the PR be changed to chore, to avoid triggering a PR?

[dkhawk]

@dkhawk , one more comment: should the title of the PR be changed to chore, to avoid triggering a PR?

I want to include the change with 4.1.0 (#1654)

[kikoso]

@dkhawk , one more comment: should the title of the PR be changed to chore, to avoid triggering a PR?

I want to include the change with 4.1.0 (#1654)

Even if it is a chore, it will be added to the upcoming release.

When we merge #1654, it will trigger a new release build, including whatever we have in main. Being marked as a chore, it will not appear on the PR, though.

I am not sure if for dependencies we should be using build or chore. Dependabot has been using build. I guess arguably it could be a feat too, if the dependencies are bringing any change to the current app.