phandroid

#Phandroid 2.0.2 has been released.

For those, that are interested: How does this work?

I have an cron job running that checks for upstream ( @phanpy ) releases every 6 hours, pulls the changes, builds the apk and pushes the build to my staging environment.
I test it manually and (when satisfied) then push the release to the Codeberg repository which makes it available to Obtainium (or for manual installs).

https://codeberg.org/umrath/Phandroid/releases/tag/v2.0.2

(Reminder: 2.0.0 had a breaking change!)

I have realized that #Phandroid so far used the wrong upstream-branch.

I have used this finding to change the way releases are handled.
There are now 2 release channels:
1. Manually tested standard releases (Phandroid, using the stable production-branch of #Phanpy)
2. fully automatic dev-Releases (Phandroid Dev, main-branch)

If you do nothing, the setup will continue to provide you with stable releases, just less frequently.
Optionally you can install Dev (side-by-side, dedicated settings).

There are some fundamental changes to the #Phandroid repository, which affects all existing users:

The jump to 2.0.0 fixes some basic (organizational) errors I committed while creating the test version (e.g. correcting a wrong application ID, etc.)

This is a disruptive change and requires manual interaction due to the fact that Obtainium will refuse to update to 2.0.0 and beyond.
The exact steps are outlined at https://codeberg.org/umrath/Phandroid#readme

(1/2)