Linthra v0.1.13

F-Droid release reliability fix

Linthra v0.1.13 carries forward the clean-reinstall protection intended for v0.1.12 while fixing the Android release-only lint failure that prevented v0.1.12 from producing APK and AAB artifacts.

What’s new

• Fixed the lintVitalRelease failure that blocked Android and F-Droid release builds.
• Updated Android backup rules to use only storage domains supported by the pinned Android lint schema.
• Added lintVitalRelease to pull-request CI so release-only Android resource errors are caught before a stable tag is created.
• Preserved clean reinstall behavior: uninstalling and reinstalling Linthra no longer restores obsolete songs, settings, server state, or inaccessible folder references.
• Normal in-place updates continue to preserve accounts, playlists, settings, catalog, and cache.
• No database migration, UI feature, or playback behavior change is included in this release.

Technical details

• Removed unsupported device_root, device_file, device_database, and device_sharedpref backup domains.
• Retained the supported root, file, database, sharedpref, and external exclusions.
• Retained android:allowBackup="false" for debug, profile, and release builds.
• Strengthened regression tests to prevent unsupported device_* domains from being reintroduced.
• Implemented in PR #304.

Upgrade notes

Existing users can update normally without losing their data.

Users who uninstall Linthra before reinstalling will receive a clean library rather than stale state restored by Android.

GitHub and F-Droid builds use different signing keys and cannot update one another. Continue using the same installation source you currently use.

No ads, no tracking, no analytics, no telemetry.