From 66d253b318b6d6d48140de0a6b51164cac59d135 Mon Sep 17 00:00:00 2001 From: Alex Saveau Date: Fri, 5 Apr 2019 15:26:27 -0700 Subject: [PATCH] v2.2.0 (#545) Signed-off-by: Alex Saveau --- README.md | 44 +++++++++++++++++++++++++++++++++++++---- plugin/build.gradle.kts | 2 +- 2 files changed, 41 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 810dfdb39..84a44d5cb 100644 --- a/README.md +++ b/README.md @@ -96,7 +96,7 @@ through the `plugins {}` DSL: ```kt plugins { id("com.android.application") - id("com.github.triplet.play") version "2.1.0" + id("com.github.triplet.play") version "2.2.0" } ``` @@ -107,7 +107,7 @@ plugins { ```groovy plugins { id 'com.android.application' - id 'com.github.triplet.play' version '2.1.0' + id 'com.github.triplet.play' version '2.2.0' } ``` @@ -235,6 +235,42 @@ channel, `default.txt` will be uploaded. > Note: the Play Store limits your release notes to a maximum of 500 characters. +#### Uploading developer facing release names + +The Play Console supports customizing release names. These aren't visible to users, but may be +useful for internal processes. Similar to release notes, release names may be specified by placing +a `[track].txt` file in the `release-names` directory under your `play` folder. For example, here's +a custom release name for the alpha track in the `play/release-names/alpha.txt` file: + +``` +My custom release name +``` + +> Note: the Play Store limits your release names to a maximum of 50 characters. + +#### Uploading a pre-existing artifact + +By default GPP will rebuild your project before every release. In advanced use cases, this might not +be the desired behavior. For example, if you need to inject translations into your APK or App Bundle +_after_ building it but _before_ publishing it. Or maybe it's a simple as you already having an +artifact you want to publish. GPP supports this class of use cases by letting you specify a +directory in which publishable artifacts may be found: + +```kt +play { + // ... + artifactDir = file("path/to/apk-or-app-bundle/dir") +} +``` + +For quick access, you can also use the `--artifact-dir` CLI option: + +```sh +./gradlew publishBundle --artifact-dir path/to/app-bundle/dir +``` + +> Note: all artifacts in the specified directory will be published. + ### Publishing an App Bundle Run `./gradlew publishBundle`. @@ -630,7 +666,7 @@ android { playConfigs { myCustomVariantOrProductFlavor { - isEnabled = true + enabled = true } // ... @@ -638,7 +674,7 @@ android { } play { - isEnabled = false // This disables GPP by default. It could be the other way around. + enabled = false // This disables GPP by default. It could be the other way around. // ... } ``` diff --git a/plugin/build.gradle.kts b/plugin/build.gradle.kts index 6132df52a..e40c351ee 100644 --- a/plugin/build.gradle.kts +++ b/plugin/build.gradle.kts @@ -42,7 +42,7 @@ tasks.named("clean") { } group = "com.github.triplet.gradle" -version = "2.2.0-SNAPSHOT" +version = "2.2.0" gradlePlugin { plugins.create("play") {