Joshua Kuestersteffen 2 лет назад
Родитель
Сommit
0a2bcafa7a
2 измененных файлов с 4 добавлено и 4 удалено
  1. 2 2
      DEVELOPMENT.md
  2. 2 2
      app/build.gradle.kts

+ 2 - 2
DEVELOPMENT.md

@@ -20,11 +20,11 @@ However, an F-Droid user will only be prompted to upgrade an app (or have the ap
 So, creating a beta release for Unlauncher requires the following steps:
 
 1. Push a beta tag to GitHub (e.g. `2.0.0-beta.1`)
-   1. Make sure that the `versionName` in the [build.gradle.kts](./build.gradle.kts) matches the tag that you are pushing
+   1. Make sure that the `versionName` in the [build.gradle.kts](./app/build.gradle.kts) matches the tag that you are pushing
 1. Delete the draft Release on GitHub for the beta tag that was created by the CI
 1. Raise a MR to [fdroid/fdroiddata](https://gitlab.com/fdroid/fdroiddata) to add a new `Builds` entry for the beta release
     1. _Do not_ update the configured `CurrenVersion`/`CurrentVersionCode` since that will trigger a normal release
-1. Prepare for the next release by incrementing the `versionCode` and `versionName` in the [build.gradle.kts](./build.gradle.kts) file
+1. Prepare for the next release by incrementing the `versionCode` and `versionName` in the [build.gradle.kts](./app/build.gradle.kts) file
 
 ## Checking F-Droid build status
 

+ 2 - 2
app/build.gradle.kts

@@ -15,8 +15,8 @@ android {
         applicationId = "com.jkuester.unlauncher"
         minSdkVersion(21)
         targetSdkVersion(33)
-        versionName = "2.0.0"
-        versionCode = 18
+        versionName = "2.1.0"
+        versionCode = 19
         vectorDrawables { useSupportLibrary = true }
 //        signingConfigs {
 //            if (project.extra.has("RELEASE_STORE_FILE")) {