-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate org.wordpress-mobile dependency group in favor of org.wordpress #19989
Deprecate org.wordpress-mobile dependency group in favor of org.wordpress #19989
Conversation
Generated by 🚫 dangerJS |
📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.
|
📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🎊 !
// 'org.wordpress-mobile' group is deprecated. It's kept for now for smoother transition | ||
// but it should be removed soon (within couple weeks) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could remove org.wordpress-mobile
once version 24.1 is code frozen and we generate an alpha version of Gutenberg Mobile to include changes from WordPress/gutenberg#58017.
@oguzkocer I'm encountering issues after this change and WordPress/gutenberg#58017 when publishing a new GBM version and pointing it in the following line: WordPress-Android/build.gradle Line 26 in eefbd25
|
Out of abundance of caution, we are updating the group id used to publish
gutenberg-mobile
artifacts fromorg.wordpress-mobile
toorg.wordpress
since we don't own thewordpress-mobile
domain. Instead of removing the old group id, I opted to deprecate it for now for smoother transition for developers. I intend to remove these deprecated domains some time next week.I didn't test this because the artifacts are not ready yet, but it's a straightforward change and one that can't break anything. So, my suggestion is to merge it and address any issues once the artifacts are updated.