versionCode not increased? about audio-share HOT 8 CLOSED

Oof. And now comes the next release, still the same versionCode – and signed by another signing key? I'm quite confused…

from audio-share.

Yes, the versionCode should be increased. I'll increase it in the future release. For signing key, I move the release procedure to Github Action, which uses a different debug signing key. I'll delete this release and then test it.

from audio-share.

Thanks @mkckr0 – but should releases be signed by a debug key? And doesn't this further mean the key must be available at Github?

from audio-share.

I have finished the Github Action config, and released a new version by Github Action.
https://github.com/mkckr0/audio-share/releases/tag/v0.0.5
I save release.jks to this repo's secret variable, and will use it for future releases.

from audio-share.

Thanks! Pinning it to the new key then. The Android APK will become available here with the next sync around 6 pm UTC – so be welcome to pick a badge to link there e.g. from your Readme. Folks can discover it there and install it via their F-Droid clients, which then will also notify them when updates become available (which my updater will fetch within 24h of your making them available).

from audio-share.

Hi @mkckr0 – and congrats to your listing at F-Droid.org! As your app is available there now for 2 weeks, this would be the time I'd remove it from my repo. But I see your Readme still carries the badge linking here. Does that mean you want your app to stay in my repo, too? As you've established reproducible builds with F-Droid, and the APK is decently sized, that would be possible (though I try to keep the overlap minimal as my repo still runs on "limited" personal space).

from audio-share.

Ok. I'll remove the badge. Thanks for your guidance.

from audio-share.

Thanks! Should you one day need the app back in my repo for some reason, just let me know. Metadata have been archived, so restore is easy.

from audio-share.