With JENKINS-32107, other build steps will be able to see which APK(s) have been uploaded during a build.
So the current "Recent changes" part of the APK upload build step could be (potentially) split out into its own build step, where it would automatically pick up the APKs used (and credentials).
This would be good, as this new "Upload recent changes text" would be helpful as a standalone build step. e.g. There is an APK in beta, with beta-tester release notes. When using Jenkins to promote that APK to production, you may also want to apply updated release notes.