fdroid/README.md (1616 bytes)
1 # F-Droid 2 3 `dev.equwal.assistkey.yml` is the F-Droid metadata of Rebind. F-Droid builds 4 the `fdroid` flavour. That flavour has no Google Play Billing, no licence check 5 and no apps of other makers inside. The `rm` line removes the folder of those 6 apps before the build, because F-Droid does not accept prebuilt binaries. 7 8 ## First submission (one time) 9 10 1. Fork `fdroid/fdroiddata` on GitLab, then clone your fork. 11 2. Copy `dev.equwal.assistkey.yml` into `metadata/` of your clone. 12 3. Run `fdroid readmeta` and `fdroid lint dev.equwal.assistkey`. 13 4. Commit on a new branch and push it to your fork. 14 5. Open a merge request against `fdroid/fdroiddata`. 15 16 ## Each new version (automatic) 17 18 The metadata has `UpdateCheckMode: Tags` and `AutoUpdateMode: Version`. F-Droid 19 checks the tags of this repository. When it finds a new tag, it reads 20 `assistkey.versionName` and `assistkey.versionCode` from `gradle.properties` 21 at that tag and adds a build by itself. 22 23 To release a version: 24 25 1. Set `assistkey.versionName` and `assistkey.versionCode` in `gradle.properties`. 26 The version code must be higher than the last one. 27 2. Add the entry to `CHANGELOG.md`. Add `fastlane/metadata/android/en-US/changelogs/<versionCode>.txt`. 28 3. Commit, then tag with `v` and the version name, for example `v0.1.2-beta`. Push the tag. 29 30 The workflow `.github/workflows/tag-check.yml` runs on each `v*` tag. It fails 31 if the tag does not match `gradle.properties`, if the changelog file is 32 missing, if a test fails, or if the F-Droid build holds a bundled app or the 33 billing library. Fix the failure and move the tag before F-Droid picks it up.