mcpField
1
1k-app-upgrade-test

1k-app-upgrade-test

github.com/onekeyhqTesting & quality2.5k53 installsUpdated today
Repository

About 1k-app-upgrade-test

A development skill that guides creation of test-version branches for app upgrade and migration testing. It specifies a version format, build-number calculation, configuration files to update, and the Git steps for committing and pushing.

Key features

  1. 01Test version naming convention
  2. 02Date-based build number formula
  3. 03Configuration file update sequence
  4. 04Branch, commit, and push steps

Use cases

  1. 01Create QA builds for upgrade testing
  2. 02Verify app version migration flows
  3. 03Test version-specific fixes or features

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/onekeyhq/app-monorepo --skill 1k-app-upgrade-test

After installing, type/1k-app-upgrade-testin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/rules/upgrade-test-version.md

Details

From the project README

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:

  1. .env.version

    • Set VERSION to test version

  2. .github/actions/shared-env/action.yml

    • Update version in outputs section

  3. .github/workflows/release-android.yml

    • Hardcode BUILD_NUMBER in "Write .env.version" step

  4. .github/workflows/release-ios.yml

    • Hardcode BUILD_NUMBER in "Write .env.version" step

  5. .github/workflows/daily-build.yml

    • Hardcode BUILD_NUMBER in "Setup ENV" step

  6. 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

FileWhat to Update
.env.versionVERSION
.github/actions/shared-env/action.ymlHardcode BUILD_NUMBER, remove conditionals
.github/workflows/release-android.ymlHardcode BUILD_NUMBER in .env.version write
.github/workflows/release-ios.ymlHardcode BUILD_NUMBER in .env.version write
.github/workflows/daily-build.ymlHardcode BUILD_NUMBER in Setup ENV step
apps/mobile/android/app/build.gradleversionCode, 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

Comments

Markdown supported