Claude
e8c7162bc0
The series a build is named for was written out three times — in the build file and in both workflows' tag lines — so bumping it meant changing all three and a release could be tagged one thing and built as another. It now lives in gradle.properties as plgVersionSeries, which the build reads when it stamps the APK and both workflows read when they name the tag. Set to 1.1. versionCode is deliberately left as the CI run number alone, which is what makes the bump safe: the run number keeps climbing across a change of series, so 1.1 never looks like a downgrade to Android and an OTA update is not interrupted. The series is a name for people; the run number is what the machines compare. The updater already read only the trailing number, and its comments now say so rather than naming 1.0. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_019Pr6B8xDDtJJcb6WJMw7Ud
26 lines
939 B
Properties
26 lines
939 B
Properties
# Project-wide Gradle settings.
|
|
org.gradle.jvmargs=-Xmx2048m -Dfile.encoding=UTF-8
|
|
org.gradle.parallel=true
|
|
org.gradle.caching=true
|
|
|
|
# AndroidX
|
|
android.useAndroidX=true
|
|
|
|
# Kotlin code style
|
|
kotlin.code.style=official
|
|
|
|
# Only build the resources needed for the configuration being built.
|
|
android.nonTransitiveRClass=true
|
|
|
|
# The version series every build and every release tag is named for: an APK is
|
|
# <series>.<run number>, a production tag is v<series>.<n> and a dev tag adds
|
|
# -dev. It lives here rather than in the build file because the workflows have
|
|
# to name the tag as well, and they read it straight out of this file — three
|
|
# copies of "1.1" would be three chances for a release to be tagged one thing
|
|
# and built as another.
|
|
#
|
|
# Only the series is set by hand. The number after it is the CI run number, so
|
|
# it keeps climbing on its own and an APK's versionCode never goes backwards
|
|
# when this changes.
|
|
plgVersionSeries=1.1
|