Skip to content

Commit

Permalink
chore: update versionName for beta release
Browse files Browse the repository at this point in the history
  • Loading branch information
jkuester committed Jan 3, 2024
1 parent 96a334e commit bbb939f
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion DEVELOPMENT.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ 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](./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. Add release notes to the draft Release on GitHub that was created by the CI and publish it as a pre-release
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](./app/build.gradle.kts) file
Expand Down
2 changes: 1 addition & 1 deletion app/build.gradle.kts
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ android {
applicationId = "com.jkuester.unlauncher"
minSdkVersion(21)
targetSdkVersion(33)
versionName = "2.1.0"
versionName = "2.1.0-beta.1"
versionCode = 19
vectorDrawables { useSupportLibrary = true }
// signingConfigs {
Expand Down

0 comments on commit bbb939f

Please sign in to comment.