MetroMusic 1.0.1

Packaging only. The application is unchanged from
1.0 — it scans, plays and scrobbles
exactly as that did — and this release exists so the app can be built from source by F-Droid
instead of distributed as a binary.

The release build no longer insists on signing itself. F-Droid's builder edits the Gradle file
before it builds: it deletes the signingConfigs { } block and every line matching
signingConfig = <one token>, and signs the result with its own key. The config here was assigned
over two lines, findByName("release") ?: getByName("debug"), of which their pattern matched only the
first — leaving a dangling ?: that does not compile. The choice is now made in a val above, so the
line they remove is a single token and what is left builds unsigned, which is what they want. Proven
by running their own remove_signing_keys over a clone and building it: app-release-unsigned.apk,
the first thing their build looks for.

A local assembleRelease is unaffected: with keystore.properties it signs with that key, without it
with the debug key, and the APK attached here carries the same certificate as 1.0
(SHA-256 494018a9…2acf7c09), so it installs over it as an update.

The app's page now lives in the repository, at fastlane/metadata/android/en-US: title, short and
full descriptions, the launcher icon rendered out of the vector the app itself draws, five screenshots
and a changelog per version code. F-Droid reads it from the same commit it builds, so the page and the
binary cannot drift apart.

---

minSdk 26 · compileSdk 36 · GPLv3 · third-party notices are in the app, on settings → about.