I have the F-Droid version of Mightier Amp installed on several Android devices. Recently I noticed that the Play Store app was attempting to upgrade Mightier Amp and failing because the installed version from F-Droid has the wrong signature. This is as expected so no real problem there. I'll just wait for F-Droid to catch up.
When it didn't after a few weeks, I checked the repository here and noticed that the latest release was 1.0.10 (dated Dec 06, 2023), which is the same as the version available from the F-Droid repository. The Play Store version is currently at 1.0.12 (date Apr 04, 2024), which confused me at first since this project hasn't posted any released higher than 1.0.10. Looking at the commit history, I see 2 commits named "version 1.0.11" and "version 1.0.12".
Mystery solved, I guess. It seems that there is an out-of-band release process for the Play Store that doesn't follow the release cadence of this repository. Seems like it should be the other way around: tag and publish releases to the Github repo first, then push out updates to public app stores. Much less confusing.
I humbly request that this repo be updated when a release is ready for public consumption, not just the Play Store.
I have the F-Droid version of Mightier Amp installed on several Android devices. Recently I noticed that the Play Store app was attempting to upgrade Mightier Amp and failing because the installed version from F-Droid has the wrong signature. This is as expected so no real problem there. I'll just wait for F-Droid to catch up.
When it didn't after a few weeks, I checked the repository here and noticed that the latest release was 1.0.10 (dated Dec 06, 2023), which is the same as the version available from the F-Droid repository. The Play Store version is currently at 1.0.12 (date Apr 04, 2024), which confused me at first since this project hasn't posted any released higher than 1.0.10. Looking at the commit history, I see 2 commits named "version 1.0.11" and "version 1.0.12".
Mystery solved, I guess. It seems that there is an out-of-band release process for the Play Store that doesn't follow the release cadence of this repository. Seems like it should be the other way around: tag and publish releases to the Github repo first, then push out updates to public app stores. Much less confusing.
I humbly request that this repo be updated when a release is ready for public consumption, not just the Play Store.
Thanks - this is a wonderful project.