Skip to content

Decouple the app version from the pinned ezvpn core - #14

Merged
andrewchen5678 merged 1 commit into
mainfrom
decouple-app-version
Sep 1, 2026
Merged

andrewchen5678 merged 1 commit into
mainfrom
decouple-app-version

Conversation

@andrewchen5678

Copy link
Copy Markdown
Contributor

Summary

  • ezvpn.versionName / ezvpn.versionCode are now the app's own version; scripts/bump-jnilibs.sh runs in core-key mode (new option in the shared devtools script) and only rewrites the release pin.
  • app/build.gradle.kts exposes the pinned release as BuildConfig.EZVPN_CORE_VERSION; the footer reads ezvpn 0.0.44 · core 0.0.44.
  • Docs updated. The app version stays at 0.0.44 (code 5) as its starting point.

Requires the devtools commit that adds BUMP_VERSION_MODE to android/bump-jnilibs.sh (pushed to devtools main).

Test plan

  • ./gradlew :app:assembleDebug :app:testDebugUnitTest locally; generated BuildConfig has EZVPN_CORE_VERSION = "0.0.44"
  • scripts/bump-jnilibs.sh v0.0.44 is a no-op diff
  • CI

🤖 Generated with Claude Code

https://claude.ai/code/session_016bFY7oe5SzmhaKxy3TTo3y

ezvpn.versionName/versionCode are now the app's own version: bump-jnilibs.sh
runs in core-key mode and only rewrites the release pin. The pinned release
(minus "v") is exposed as BuildConfig.EZVPN_CORE_VERSION so the footer reads
"ezvpn 0.0.44 · core 0.0.44". The app version stays at 0.0.44 (code 5) as its
starting point.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016bFY7oe5SzmhaKxy3TTo3y
@andrewchen5678
andrewchen5678 merged commit e2b0293 into main Sep 1, 2026
1 check passed
@andrewchen5678
andrewchen5678 deleted the decouple-app-version branch September 1, 2026 23:38
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