Skip to content

Prepare v0.3.2: bump version to 0.3.2 (versionCode 5) - #37

Merged
guyiome merged 1 commit into
mainfrom
prepare-v0.3.2
Sep 16, 2026
Merged

guyiome merged 1 commit into
mainfrom
prepare-v0.3.2

Conversation

@guyiome

@guyiome guyiome commented Sep 16, 2026

Copy link
Copy Markdown
Owner

Summary

Version bump ahead of tagging v0.3.2. The point of this release is to get the tongue-out stage 3 packaging fix (#36) into an artifact users actually install: image_embedder.tflite was downloaded by no workflow, so the feature could never initialise in any published APK. It also carries the failed-init latch fix from the same PR.

As for v0.3.1, bumping versionName is a prerequisite rather than bookkeeping: the in-app update checker compares BuildConfig.VERSION_NAME against the latest release tag, so tagging v0.3.2 on a build still reporting 0.3.1 would leave a permanent "update available" badge on devices already running the newest build.

Deliberately not included: the three open Dependabot PRs (#33 codeql-action v4, #34 Kotlin 2.4.20, #35 ARCore 1.56.0). This release exists to prove one packaging fix; mixing in a compiler and SDK bump would muddy the diagnosis if anything misbehaved. The ARCore bump especially — it can no longer be exercised on the new test device, which isn't ARCore-certified.

Test plan

  • testDebugUnitTest, assembleDebug, lintDebug pass.
  • Verified the built APK reports the new version rather than assuming the edit took: aapt2 dump badgingversionCode='5' versionName='0.3.2'.
  • After tagging: download the published APK and confirm assets/image_embedder.tflite is actually inside it. That is the only possible proof of the packaging fix — a local build bundles the model regardless, so it cannot demonstrate anything here.

🤖 Generated with Claude Code

Patch release whose point is to get the tongue-out stage 3 packaging
fix (#36) into an artifact users actually install: image_embedder.tflite
was downloaded by no workflow, so the feature could never initialise in
any published APK. Also carries the failed-init latch fix from the same
PR.

As for v0.3.1, bumping versionName is a prerequisite rather than
bookkeeping: the in-app update checker compares BuildConfig.VERSION_NAME
against the latest release tag, so tagging v0.3.2 on a build still
reporting 0.3.1 would leave a permanent "update available" badge on
devices already running the newest build.

Verified the built APK reports the new version rather than assuming the
edit took (aapt2 dump badging: versionCode='5' versionName='0.3.2').
Unit tests, debug build and lint pass.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@guyiome
guyiome merged commit b79bad9 into main Sep 16, 2026
2 checks passed
@guyiome
guyiome deleted the prepare-v0.3.2 branch September 16, 2026 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant