versionCode not increased?

[IzzySoft]

Looks like today's release (v0.10.0) still has the same versionCode (17) as the previous v0.9.6. As Android uses versionCode to tell APKs apart, it's important to increase it with each release (or whoever had the previous version installed would get no notification of a newer one being available). Guess it just slipped through this time, so please take this just as a notification (oops, or reminder) to always increase versionCode right before releasing 😉 Thanks!

[vitorpamplona]

Nice catch! I just released v0.10.1 to fix this issue: https://github.com/vitorpamplona/amethyst/releases/tag/v0.10.1

[IzzySoft]

Yeah, my updater complained, that's how I caught it 🙈

Oh, sorry, I should have mentioned: Amethyst is listed in my F-Droid repo. If you wish you can pick a badge to link there e.g. from your Readme. If you wish I can send you the metadata used there in Fastlane format to include with your repo, so you can control description, screenshots etc (changes to them will then be picked up automatically with each new release). Updater runs once a day, starting around 6 pm UTC and publishing about an hour later.

[IzzySoft]

I just caught you again, @vitorpamplona – please keep up fixing! Ideally before tagging 🙊 💨

Binary files com.vitorpamplona.amethyst_38.apk and com.vitorpamplona.amethyst_v0.13.3.apk differ