Prepare for next beta release

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. _Do not_ update the `versionName` in the [build.gradle.kts](./build.gradle.kts) file to match the beta tag name since this will trigger a normal release in F-Droid
+   1. Make sure that the `versionName` in the [build.gradle.kts](./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` in the [build.gradle.kts](./build.gradle.kts) file (`versionName` should not be updated)
+1. Prepare for the next release by incrementing the `versionCode` and `versionName` in the [build.gradle.kts](./build.gradle.kts) file
 
 ## Checking F-Droid build status
 

app/build.gradle.kts

@@ -15,8 +15,8 @@ android {
         applicationId = "com.jkuester.unlauncher"
         minSdkVersion(21)
         targetSdkVersion(30)
-        versionName = "1.3.0"
-        versionCode = 12
+        versionName = "1.3.0-beta.3"
+        versionCode = 13
         testInstrumentationRunner = "androidx.test.runner.AndroidJUnitRunner"
         vectorDrawables { useSupportLibrary = true }
 //        signingConfigs {