gradle-play-publisher v3.0.0 Release Notes

Release Date: 2020-09-09 // 6 months ago
  • Note: Gradle 6.5 and the Android Gradle Plugin v4.1.0 are the new minimum requirements. GPP 2.x will not support AGP 4.1 or above.

    ๐Ÿ†• New features

    • ๐Ÿ‘ Better compatibility with the maven-publish plugin. If present, GPP will now add its dependencies to the publish task.
    • Proxy authentication courtesy of @wintermute766.

    ๐Ÿ› Bug fixes

    • ๐Ÿ›  Fixed a critical issue where playConfigs would sometimes inadvertently overwrite each other.

    ๐Ÿ’ฅ Breaking changes

    • ๐Ÿ”„ All properties now use the Gradle Property API. Upgrade steps: change foo = blah to foo.set(blah). For more guidance, see the updated docs.
    • ๐Ÿšš The outputProcessor property has been removed. The same functionality can now be achieved using native AGP APIs.
    • ๐Ÿ‘Œ Support for PKCS12 credentials (aka .p12 files) has been removed along with the serviceAccountEmail property. Use JSON credentials instead.
    • ๐Ÿšš Deprecated task names have been removed.
    • ๐Ÿšš promo-graphics are no longer supported in the Publishing API and have been removed.

    Behavior changes

    Promote task

    The promote task now handles its different configuration options more simply. Promotion needs a from track and a promote track. If the fromTrack isn't specified explicitly, the least stable release track will be used. If the promoteTrack isn't specified explicitly, it will be assumed that you want to do an in-place update so the resolved fromTrack will be used. Previously, the track property was involved in the computation of both other properties.


Previous changes from v2.8.0

    • Support for authenticating GPP with an environment variable! See the docs.
    • ๐Ÿ‘Œ Support for in-app update priority.
    • ๐Ÿ›  Fixed an incompatibility with Gradle 6.5.
    • ๐Ÿ›  Fixed a crash publishing releases to a new track.
    • โœ‚ Removed unnecessary warnings.

    ๐Ÿš€ > PS: this release uses a new publishing mechanism, so in theory you can use any of our modules directly (though this isn't officially supported).