Create test versions to verify app auto-update functionality and version migration.
48
53%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.skillshare/skills/1k-app-upgrade-test/SKILL.mdAutomates creation of test version branches with hardcoded build configurations for testing app upgrade functionality and version migration flows.
Test versions follow the pattern: 9XXX.YY.Z
9XXX - Test version indicator (e.g., 9005)YY.Z - Matches production version being testedExample: 9005.20.0 for testing production 5.20.0
Build number is calculated as:
DATE=$(date +%Y%m%d)
BUILD_NUMBER=$((${DATE}00 + 30))Format: 10 digits = YYYYMMDD00 + 30
Example: If today is 20260130, build number is 2026013030
Ask user for test version number:
9XXX.YY.Z9005.20.0DATE=$(date +%Y%m%d)
BUILD_NUMBER=$((${DATE}00 + 30))
echo "Build number: $BUILD_NUMBER"git checkout -b <test_version>
# Example: git checkout -b 9005.20.0Update these files in order:
.env.version
.github/actions/shared-env/action.yml
.github/workflows/release-android.yml
.github/workflows/release-ios.yml
.github/workflows/daily-build.yml
apps/mobile/android/app/build.gradle
git add .
git commit -m "chore: create test version <version>"
git push origin <test_version>| File | What to Update |
|---|---|
.env.version | VERSION |
.github/actions/shared-env/action.yml | Hardcode BUILD_NUMBER, remove conditionals |
.github/workflows/release-android.yml | Hardcode BUILD_NUMBER in .env.version write |
.github/workflows/release-ios.yml | Hardcode BUILD_NUMBER in .env.version write |
.github/workflows/daily-build.yml | Hardcode BUILD_NUMBER in Setup ENV step |
apps/mobile/android/app/build.gradle | versionCode, versionName |
For comprehensive test version creation workflow with examples, see upgrade-test-version.md.
Topics covered:
/1k-dev-commands - Git and development workflow conventions/1k-dev-commands - Build and release commandsd71e6b7
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.