be-gay-do-crimes
/
newpipe-documentation
mirror of https://github.com/TeamNewPipe/documentation
1
0
Fork 0
Code Issues Releases Wiki Activity

Update docs/07_release_instructions.md 

Co-authored-by: opusforlife2 <53176348+opusforlife2@users.noreply.github.com>
This commit is contained in:
Tobi 2024-05-20 20:27:05 +02:00 committed by GitHub
parent 6c29e5c3fa
commit 4976784092
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/07_release_instructions.md
View File

@ -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`