fix(deps): update dependency com.github.triplet.gradle:play-publisher to v2.8.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.github.triplet.gradle:play-publisher	2.2.1 -> 2.8.1

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

---

Release Notes

Triple-T/gradle-play-publisher

v2.8.1

Compare Source

v2.8.0: Gradle Play Publisher 2.8.0

Compare Source

• 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).

v2.7.5: Gradle Play Publisher 2.7.5

Compare Source

• Fixed a compatibility issue with Gradle 6.3.
• Fixed a bug causing local release notes to be picked from the promoteTrack instead of the fromTrack.

v2.7.3: Gradle Play Publisher 2.7.3

Compare Source

This release fixes a few key bugs:

• Bootstrapping images started failing across various GPP versions due to an API change.
• Using a product flavor named play would fail.
• GPP would crash on a non-existent mapping file.

In addition, partial compatibility with AGP 4.1.x is now available.

v2.7.2: Gradle Play Publisher 2.7.2

Compare Source

This release makes incompatibility errors with the Android Gradle Plugin clearer.

Note: the minimum AGP version was bumped from 3.6.0-rc03 to 3.6.0 now that 3.6 stable has shipped.

v2.7.1: Gradle Play Publisher 2.7.1

Compare Source

This release fixes a dependency resolution issue caused by https://github.com/googleapis/google-api-java-client/issues/1487.

v2.7.0: Gradle Play Publisher 2.7.0

Compare Source

This release is focused on fixing long-standing bugs and minor feature requests.

Note: GPP v2.7 requires at least Gradle 6.2 and the Android Gradle Plugin 3.6.0.

Improvements

• Support for top-level graphics is now available. This means that you can put your app's icon (for example) in graphics/icon.png instead of graphics/icon/1.png.
• If no local release notes are found, existing release notes from the Play Console will be carried over when publishing your APK or App Bundle.
• You can now upload and/or install debuggable internal sharing artifacts.
• A warning is now logged if your playConfigs contain an unrecognized variant, product flavor, or build type.

Bug fixes

• CLI params now always override your build script configuration instead of failing if you had playConfigs.
• CLI params on lifecycle tasks (such as promoteArtifact instead of promoteReleaseArtifact) now propage down to their respective implementation tasks correctly.
• The --artifact-dir CLI param is now correctly respected in eagerly configured Gradle projects.

Deprecations

• The --track CLI param on promotion tasks has been removed as it led to confusing bugs and unpredictable behavior. Use --promote-track instead.

v2.6.2: Gradle Play Publisher 2.6.2

Compare Source

• Fixed incompatibilities with Gradle 6.1 and AGP 4.0
• Improved error message formatting

v2.6.1: Gradle Play Publisher 2.6.1

Compare Source

Fixed an issue where promoting a release with R8/Proguard enabled would fail.

v2.6.0: Gradle Play Publisher 2.6.0

Compare Source

This release of GPP requires at least Gradle 6.0.

Bug Fixes

• Fixed an incompatibility with Gradle 6.0
• Fixed numerous bugs related to incremental play resource generation and listing publication
• Clarified some ambitious logs and warnings

v2.5.0: Gradle Play Publisher 2.5.0

Compare Source

This release mainly consists of a huge refactor towards a testable architecture. As a bonus, numerous bugs have been fixed in the process.

Other notable changes are:

• Support for installing Internal Sharing artifacts. See the docs here.
• PKCS12 based authentication is deprecated and will be removed in v3.

v2.4.2: Gradle Play Publisher 2.4.2

Compare Source

• Fix another AGP 3.6 incompatibility - #​696, #​711
• Fix regression causing build failure on unproguarded builds - #​711
• Fix not all hidden files being ignored - #​703

v2.4.1: Gradle Play Publisher 2.4.1

Compare Source

Fixed an incompatibility with the Android Gradle Plugin v3.5.x - #​693

v2.4.0: Gradle Play Publisher 2.4.0

Compare Source

This release transitions GPP into a new publishing model. Previously, every task would create an edit against the Play Store and then commit that edit at the end of the task. In the new model, one build == one commit per app package, meaning one edit will be used across tasks for the same app package. This makes each publishing build an atomic operation: if anything fails, everything is reset and put back into a clean state. See #​629 for full details.

Note: Gradle 5.6.1 and AGP 3.5.0 are the new minimum dependency versions.

Artifact retention

GPP v2.4 supports retaining the main and patch OBB files. GPP can also retain releases if, for example, you want to retain your WearOS artifact. See the docs for more details.

In-app products bug fixes/improvements - #​690

• You can now create a completely new product with GPP (previously, it had to first be created in the Play Console)
• Prices are now auto expanded into different currencies so you don't have to explicitly specify them all
• Bootstrapping more than 100 products is now supported

Other changes

• You can now publish and promote artifacts within the same build - #​643
• Listing upload tasks now run in parallel - #​628
• An incompatibility with bundles in AGP 3.6 was fixed - #​633
• An incompatibility with Gradle 6.0 was fixed - #​688
• Cascading play config merge bugs were fixed - #​642
• --artifact-dir inconsistencies have been fixed: all relative paths now start from the root project directory - #​691
• Support for uploading multiple internal sharing APKs is now available - #​691

v2.3.0: Gradle Play Publisher 2.3.0

Compare Source

The theme of this release is polish, polish everywhere. 🌈

Required dependencies - #​564

This release of GPP enforces modern tooling. That means you'll need Gradle 5.4 and the Android Gradle Plugin 3.5.0 at a minimum. These dependency requirements were needed in order to use the new APIs that enable GPP v2.3.0's improvements.

Notable changes

Massive performance improvements - #​573

GPP now uses Gradle's Worker API in all applicable tasks. Depending on how many variants your project has and what you're uploading, you'll see fairly significant performance gains.

Revamped logging

On top of error message and task description improvements, GPP now logs the current status of every publishing task being run. This makes validating the correctness of your build much easier. Here's a sample log from running ./gradlew publish:

Click to expand/collapse

> Task :app:publishReleaseListing
Uploading app details
Uploading en-US listing
Uploading fr-FR listing
Committing changes

> Task :app:publishReleaseBundle
Starting App Bundle upload
App Bundle upload complete
Starting mapping file upload
Mapping file upload complete
Updating [completed] release (com.supercilex.test:[380135]) in track 'internal'
Committing changes

Support for uploading Internal Sharing artifacts - #​576

Google announced support for Internal Sharing artifacts which GPP now supports. Simply run ./gradlew uploadPrivateArtifact and copy the link outputted in the console.

CLI options cleanup - #​568, #​567, #​588

Previously, all CLI options from every task were available to all other tasks. This made things very confusing when, say, ./gradlew publishApk --default-to-app-bundles was valid. Now, every task has a tailored set of CLI options that are directly applicable to the task in question. As usual, you can find out what a task's CLI options are by running ./gradlew help --task [task]

Furthermore, the promote task now has an --update [track] option which is equivalent to --from-track [track] --track [track]; the --skip-commit CLI option has been renamed to --no-commit, following common naming conventions; and a --release-name option was added to change a release's name in the Play Console.

Bug fixes

Bootstrap task

• A new line is now added to the end of text files - #​566
• The task name has been simplified from bootstrap[Variant]PlayResources to bootstrap[Variant] - #​569
  • The old name will be removed in v3.0
• The play src directory is now wiped out to guarantee a clean slate - #​575
• Screenshot order from the Play Store is now properly respected - #​575
• If running the bootstrap and publishListing task in the same build, the tasks will now execute in the correct order - #​575

Other

• App Bundle uploading broke in AGP 3.6 alpha 2—it's now fixed - #​581
• Universal APKs are now uploaded again - #​595
• The promote task now always selects the highest version code available if no from-track is specified instead of picking something non-deterministic from the API response - #​571
• Local listing validation has been removed in favor of the Publishing API's validation - #​601
• Fixed tons of incremental processing bugs

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.