Explorar el Código

Prepare for 2.0.0 release

Joshua Kuestersteffen hace 2 años
padre
commit
105c8ce098
Se han modificado 2 ficheros con 4 adiciones y 4 borrados
  1. 2 2
      DEVELOPMENT.md
  2. 2 2
      app/build.gradle.kts

+ 2 - 2
DEVELOPMENT.md

@@ -5,9 +5,9 @@
 Building an Unlauncher release is straightforward.  
 
 1. Push a tag to GitHub (e.g. `1.2.1`) from the latest commit on the `master` branch
-    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. Add release notes to the draft Release on GitHub that was created by the CI and publish the 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
 1. Monitor the [F-Droid build status](#checking-f-droid-build-status) to make sure the tag is successfully published (can take several days depending on the build queue)
 
 ## Building a beta release

+ 2 - 2
app/build.gradle.kts

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