From 48784a2eb32c9c293e81077d53866506684ee67f Mon Sep 17 00:00:00 2001 From: Guyiome Date: Wed, 2 Sep 2026 13:09:10 +0200 Subject: [PATCH] Prepare v0.3.1: bump version to 0.3.1 (versionCode 4) Patch release over v0.3.0: the new artist logo (#30), the camera preview/overlay freeze fix on in-app language change (#26), the security policy and issue templates (#24), and two dependency batches (#25, #31). Bumping versionName is not cosmetic here, it's required before tagging: the in-app update checker compares BuildConfig.VERSION_NAME against the latest GitHub release tag, so tagging v0.3.1 while the build still reported 0.3.0 would show a permanent, unclearable "update available" badge to users already running the newest build. No README sync this time, unlike the v0.3.0 preparation: that one tracked newly added features, whereas everything since is fixes plus the logo. Checked that no tracked doc still credits the previous placeholder logo. Verified the built APK actually reports the new version (aapt2 dump badging: versionCode='4' versionName='0.3.1') rather than assuming the edit took effect. Unit tests, debug build and lint all pass. --- app/build.gradle.kts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/app/build.gradle.kts b/app/build.gradle.kts index d9985d0..db7bdf2 100644 --- a/app/build.gradle.kts +++ b/app/build.gradle.kts @@ -34,8 +34,8 @@ android { // et ARCore/CameraX/MediaPipe filtrent de toute façon les appareils trop anciens. minSdk = 30 targetSdk = 37 - versionCode = 3 - versionName = "0.3.0" + versionCode = 4 + versionName = "0.3.1" testInstrumentationRunner = "androidx.test.runner.AndroidJUnitRunner" }