search

polymorphicshade / Tubular

A fork of NewPipe that implements SponsorBlock and ReturnYouTubeDislike.
GNU General Public License v3.0
1.11k stars 24 forks source link

build and release the app using GitHub Actions #57

Closed ghost closed 2 months ago

ghost commented 2 months ago

Should solve #52

I believe that my work is complete, this workflow will handle everything from building to signing to creating a relevant tag and release names that are extracted from app/build.gradle.

All you need is to launch it when you like to publish a new release.

It is tested and it works pretty well as you can see here.

You can also check the release page to see the tag and release name, and I also made it to rename the apk file to match yours.

You just have to add KEYSTORE_BASE64 and KEYSTORE_PASSWORD and GH_TOKEN with the relevant permissons so it can create the release and upload the files.

polymorphicshade commented 2 months ago

I screwed up something. I'll just apply your changes manually 😁

sudoshindo commented 2 months ago

No IzzyOnDroid automation?

IzzySoft commented 2 months ago

@sudoshindo which IzzyOnDroid automation do you miss? As long as the APKs are provided at releases, the automation at IzzyOnDroid can take over. Update checker runs daily, thus should fetch updates within < 24h of the APK becoming available at releases – and ship them with the next sync, provided nothing went wrong. I hope this new CI workflow doesn't result in a changed signature, for example, as that would break it and require manual actions (at IzzyOnDroid, but also for everyone having installed the app from there or here).

sudoshindo commented 2 months ago

When I saw that the Tubular update was out, I was confused why my F-droid client wasn't showing it. I repeatedly visited the apt.izzysoft.de URL to check if the update was out yet.

It was taking a while so I assumed that the Tubular dev had to take some additional action for the update to be published.

@IzzySoft

IzzySoft commented 2 months ago

@sudoshindo the updater for IoD runs once a day, the sync happens around 8 pm local time (6 pm UTC in summer, 7 pm UTC in winter – screw those fiddling with the clock). So when the release happens just after the updater checked, it will be another 24h until it's fetched.

sudoshindo commented 2 months ago

Thanks for the explanation. I guess I just need to be more patient.