Skip to content

Update wordpress:utils 3.5.0 -> 3.15.0#1119

Open
ygnessin wants to merge 1 commit into
wordpress-mobile:trunkfrom
ygnessin:update-wordpress-utils-3.15.0
Open

Update wordpress:utils 3.5.0 -> 3.15.0#1119
ygnessin wants to merge 1 commit into
wordpress-mobile:trunkfrom
ygnessin:update-wordpress-utils-3.15.0

Conversation

@ygnessin
Copy link
Copy Markdown

Fix

Updates the wordpress:utils dependency to the latest: https://github.com/wordpress-mobile/WordPress-Utils-Android/releases

Primary motivation is that the GET_ACCOUNTS permission gets pulled into any apps using Aztec. This was fixed in version 3.8.0 of wordpress:utils.

Many other dependencies are severely out of date as well, hopefully there is a plan to update them at some point.

Test

Ran all unit tests and they passed

Review

??? Not sure

@ygnessin
Copy link
Copy Markdown
Author

@zwarm It looks like you are the most recent contributor to this project. Can you help land this PR?

@zwarm zwarm self-assigned this Mar 18, 2026
@zwarm
Copy link
Copy Markdown
Contributor

zwarm commented Mar 18, 2026

@zwarm It looks like you are the most recent contributor to this project. Can you help land this PR?

Hi @ygnessin, thanks for the contribution! I’ll need to take a deeper look at how this change could impact the apps currently using this library before moving forward. The utils haven’t been updated since 2024, and quite a bit has changed since then.

This review may take some time as I’m currently focused on higher-priority work, but I’ll share an update as soon as I’m able to dig in. 🙇

Copy link
Copy Markdown
Contributor

@zwarm zwarm left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution — removing the GET_ACCOUNTS permission bleed is a worthwhile fix!

A few things before this merges:

1. Changelog review
This jumps 10 minor versions (3.5.0 → 3.15.0). Could you skim the WordPress-Utils-Android releases for any behavioral changes or deprecations in the classes Aztec uses (AppLog, ImageUtils, PermissionUtils, ToastUtils, DeviceUtils) and confirm nothing breaks?

2. Transitive dependency check
The main goal is removing GET_ACCOUNTS — worth verifying no new permissions or unexpected transitive dependencies were introduced in the process. You can check with:

./gradlew :aztec:dependencies

A before/after diff of the output would be ideal.

3. Manual smoke test on the demo app
Unit tests passing is great. Since ImageUtils is used in real image-handling paths, a quick manual pass on image insertion in the demo app would help confirm nothing regressed there.

@ygnessin
Copy link
Copy Markdown
Author

ygnessin commented May 13, 2026

1. Changelog review This jumps 10 minor versions (3.5.0 → 3.15.0). Could you skim the WordPress-Utils-Android releases for any behavioral changes or deprecations in the classes Aztec uses (AppLog, ImageUtils, PermissionUtils, ToastUtils, DeviceUtils) and confirm nothing breaks?

I think the only thing of note is targetSdk updates from 33 to 34. The only Breaking Change call-out is removal of GET_ACCOUNTS which is of course the desired behavior.

Beyond that, I am relying on the semantic versioning policy of the library which indicates that a minor version bump shouldn't contain breaking changes.

2. Transitive dependency check The main goal is removing GET_ACCOUNTS — worth verifying no new permissions or unexpected transitive dependencies were introduced in the process. You can check with:

./gradlew :aztec:dependencies

A before/after diff of the output would be ideal.

Here you go: https://gist.github.com/ygnessin/e7553f7285056dd29edfdae403f61434

3. Manual smoke test on the demo app Unit tests passing is great. Since ImageUtils is used in real image-handling paths, a quick manual pass on image insertion in the demo app would help confirm nothing regressed there.

Works!

Screenshot_20260513_151105

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