1k-app-upgrade-test
Facilitates testing of application auto-update cycles and version migration strategies.
Install
mkdir -p .claude/skills/1k-app-upgrade-test && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8564" && unzip -o skill.zip -d .claude/skills/1k-app-upgrade-test && rm skill.zipInstalls to .claude/skills/1k-app-upgrade-test
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create test versions to verify app auto-update functionality and version migration.Key capabilities
- →Create test version branches
- →Verify auto-update functionality
- →Test version migration flows
- →Calculate build numbers
How it works
Automates the creation of branches with hardcoded configurations to simulate upgrade scenarios.
Inputs & outputs
When to use 1k-app-upgrade-test
- →Testing app auto-update behavior
- →Verifying version migration scripts
- →Simulating update failure scenarios
About this skill
Test Version Creation
Automates creation of test version branches with hardcoded build configurations for testing app upgrade functionality and version migration flows.
Quick Reference
Version Pattern
Test versions follow the pattern: 9XXX.YY.Z
9XXX- Test version indicator (e.g., 9005)YY.Z- Matches production version being tested
Example: 9005.20.0 for testing production 5.20.0
Build Number Formula
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
Workflow
Step 1: Get Version Information
Ask user for test version number:
- Format:
9XXX.YY.Z - Example:
9005.20.0
Step 2: Calculate Build Number
DATE=$(date +%Y%m%d)
BUILD_NUMBER=$((${DATE}00 + 30))
echo "Build number: $BUILD_NUMBER"
Step 3: Create Branch
git checkout -b <test_version>
# Example: git checkout -b 9005.20.0
Step 4: Modify Configuration Files
Update these files in order:
-
.env.version- Set VERSION to test version
-
.github/actions/shared-env/action.yml- Update version in outputs section
-
.github/workflows/release-android.yml- Hardcode BUILD_NUMBER in "Write .env.version" step
-
.github/workflows/release-ios.yml- Hardcode BUILD_NUMBER in "Write .env.version" step
-
.github/workflows/daily-build.yml- Hardcode BUILD_NUMBER in "Setup ENV" step
-
apps/mobile/android/app/build.gradle- Update versionCode
- Update versionName
Step 5: Commit and Push
git add .
git commit -m "chore: create test version <version>"
git push origin <test_version>
Files to Modify
| 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 |
Detailed Guide
For comprehensive test version creation workflow with examples, see upgrade-test-version.md.
Topics covered:
- Version number format and conventions
- Build number calculation formula
- Step-by-step file modification instructions
- Configuration file examples
- Git workflow for test versions
- QA testing considerations
When to Use This Skill
- Creating test builds for QA upgrade testing
- Testing version migration flows
- Verifying app upgrade functionality
- Creating release candidates with specific build numbers
- Testing version-specific features or fixes
Related Skills
/1k-dev-commands- Git and development workflow conventions/1k-dev-commands- Build and release commands
When not to use it
- →Production release creation
- →Non-upgrade testing
Prerequisites
Limitations
- →Follows specific 9XXX.YY.Z versioning pattern
How it compares
Uses a specific versioning pattern and build formula for upgrade testing rather than standard release flows.
Compared to similar skills
1k-app-upgrade-test side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| 1k-app-upgrade-test (this skill) | 0 | 1mo | Review | Beginner |
| agent-production-validator | 3 | 6mo | Review | Advanced |
| django-verification | 5 | 4mo | Review | Intermediate |
| xcodebuildmcp-cli | 3 | 5mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by OneKeyHQ
View all by OneKeyHQ →You might also like
agent-production-validator
ruvnet
Agent skill for production-validator - invoke with $agent-production-validator
django-verification
affaan-m
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.
xcodebuildmcp-cli
cameroncooke
Official skill for the XcodeBuildMCP CLI. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
validate-delivery
avifenesh
Use when validating task completion before shipping. Runs tests, build, and requirement checks. Returns pass/fail with fix instructions.
deployment-e2e-testing
dotnet
Guide for writing Aspire deployment end-to-end tests. Use this when asked to create, modify, or debug deployment E2E tests that deploy to Azure.
release-testing
mono
Run integration tests to verify SkiaSharp NuGet packages work correctly before publishing. Use when user asks to: - Test/verify packages before release - Run integration tests - Test on specific device (iPad, iPhone, Android emulator, Mac, Windows) - Verify SkiaSharp rendering works - Check if packages are ready for publishing - Run smoke/console/blazor/maui tests - Continue with release - Test version X Triggers: "test the release", "verify packages", "run tests on iPad", "check ios tests", "test mac catalyst", "run android tests", "continue", "test 3.119.2-preview.2".