Skip to content

build: update dependencies#1656

Merged
dkhawk merged 4 commits into
mainfrom
chore/update-dependencies
Feb 20, 2026
Merged

build: update dependencies#1656
dkhawk merged 4 commits into
mainfrom
chore/update-dependencies

Conversation

@dkhawk

@dkhawk dkhawk commented Feb 20, 2026

Copy link
Copy Markdown
Contributor

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

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
@dkhawk dkhawk changed the title chore: update dependencies fix: update dependencies Feb 20, 2026
@googlemaps-bot

Copy link
Copy Markdown
Contributor

Code Coverage

Overall Project 40.1% 🍏

There is no coverage information present for the Files changed

@kikoso

kikoso commented Feb 20, 2026

Copy link
Copy Markdown
Collaborator

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

@dkhawk

dkhawk commented Feb 20, 2026

Copy link
Copy Markdown
Contributor Author

@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 commented Feb 20, 2026

Copy link
Copy Markdown
Contributor Author

@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 kikoso left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kikoso

kikoso commented Feb 20, 2026

Copy link
Copy Markdown
Collaborator

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

@dkhawk

dkhawk commented Feb 20, 2026

Copy link
Copy Markdown
Contributor Author

@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

kikoso commented Feb 20, 2026

Copy link
Copy Markdown
Collaborator

@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.

@dkhawk dkhawk changed the title fix: update dependencies build: update dependencies Feb 20, 2026
@dkhawk dkhawk merged commit 201f964 into main Feb 20, 2026
8 checks passed
@dkhawk dkhawk deleted the chore/update-dependencies branch February 20, 2026 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants