From 49767840927b8b85ec4571521d0ad3850e3339e5 Mon Sep 17 00:00:00 2001 From: Tobi Date: Mon, 20 May 2024 20:27:05 +0200 Subject: [PATCH] Update docs/07_release_instructions.md Co-authored-by: opusforlife2 <53176348+opusforlife2@users.noreply.github.com> --- docs/07_release_instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/07_release_instructions.md b/docs/07_release_instructions.md index 20fd3e8..521db0c 100644 --- a/docs/07_release_instructions.md +++ b/docs/07_release_instructions.md @@ -265,7 +265,7 @@ Currently, @TheAssassin is the only holder of NewPipe's APK signing keys. Theref - Profit :-D ## Publish the release through the F-Droid main repo -Once the release is tagged, F-Droid is able to build and the sign the APK. Since NewPipe's APK is reproducible, the APK built by F-Droid will be identical to the one you built locally. Therefore, you can publish the release through the F-Droid main repo, which will make the new version available to all users. However, a second APK which is only signed by F-Droid is also published in their main repo. For that reason, we need to update the metadata and add signing data for the new version manually: +Once the release is tagged, F-Droid is able to build and sign the APK. Since NewPipe's APK is reproducible, the APK built by F-Droid will be identical to the one you built locally. Therefore, you can publish the release through the F-Droid main repo, which will make the new version available to all users. However, a second APK which is only signed by F-Droid is also published in their main repo. For that reason, we need to update the metadata and add signing data for the new version manually: - Clone or update F-Droid metadata repo - `git clone https://gitlab.com/fdroid/fdroiddata.git` / `git pull`