Olivier Halligon

@fr0l Can you update your fork to the latest `master` and merge it back to this PR (or rebase this PR on top of the latest `fastlane:master`? One of the...

> @AliSoftware is there a process for requesting a release with this change? @joshdholtz just [recently worked on automating the release process for new fastlane versions](https://mastodon.social/@joshdholtz/112637615677467343). They are not yet...

@Liquidsoul FYI: Just did similar update to latest CocoaPods in https://github.com/AliSoftware/OHHTTPStubs/pull/368 than the one you included in this PR

Done some similar work in https://github.com/AliSoftware/OHHTTPStubs/pull/368 just now

Just ran the testing instructions this morning and confirmed via `$ANDROID_SDK_ROOT/build-tools/34.0.0/aapt2 dump badging artifacts/WooCommerce-Wear-19.3-universal.apk` that the downloaded APK when passing `app:WooCommerce-Wear` was the one for Wear indeed (`versionCode='50567' versionName='19.3-rc-1w'`, `uses-library:'com.google.android.wearable'`,...

Update: since Google Play requires that we mention `Wear OS` in all our localized Play Store Listing too (and not just the English one), we'll have to update the `fastlane/metadata/android/{locale}/full_description.txt`...

FYI, I just ran the following _fastlane_ command from this PR's branch to upload the new content of all the `fastlane/metadata/android/*/*.txt` files to Google Play: ```bash bundle exec fastlane run...

## Next Steps once Google approves the current listing (🤞 ) - [x] Merge this PR to `release/19.3` - [ ] Backmerge `release/19.3` to `trunk`, so that `PlayStoreStrings.pot` gets sent...

@ThomazFB as someone who already experienced the process a bit for the first Wear OS release, what do you think about this proposed small change in the process? See the...

@iangmaia I'll let you decide when to land this PR so that you can potentially sync its landing with the update of the release scenario and announcement when all is...