Run any Skill in Manus with one click

Get Started

1k-app-upgrade-test

Stars2,378

Forks517

UpdatedMarch 23, 2026 at 10:29

Create test versions to verify app auto-update functionality and version migration.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

OneKeyHQ

OneKeyHQ/app-monorepo

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

2 files

SKILL.md

readonly

name	1k-app-upgrade-test
description	Create test versions to verify app auto-update functionality and version migration.
allowed-tools	Read, Grep, Glob, Write, Edit, Bash
disable-model-invocation	true

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-git-workflow - Git branching conventions
/1k-dev-commands - Build and release commands

More from this repository

same repository

1k-patch-package-workflow

OneKeyHQ/app-monorepo

Create or regenerate a patch-package patch in this monorepo. Use when you edit anything under node_modules/ and need a persisted .patch, or when `npx patch-package <pkg>` fails with "Couldn't find any versions for ... matches ^x@x". Keywords: patch-package, patch a package, regenerate patch, resolutions error.

2026-06-232.4k

1k-trade-swap-market

OneKeyHQ/app-monorepo

App-side OneKey Trade/Swap/Market guide for Swap core, Swap Pro, Market speed-swap, K-line/chart, token selectors, cold-start frame-by-frame validation, quote/build/send flows, history/status, provider channels, PrivateSend-like channels, stock-trading channels, limit/order flows, fees, slippage, ETA, and cross-module funding handoffs.

2026-06-182.4k

1k-create-pr

OneKeyHQ/app-monorepo

Creates a Pull Request from current changes for OneKey app-monorepo. Use when user wants to create PR, submit changes, or merge feature branch. Handles branch creation, commit, push, and PR creation with conversation context extraction for code review AI.

2026-06-172.4k

1k-ui-verify

OneKeyHQ/app-monorepo

AI-agent-driven UI verification for OneKey. Use to actually drive the running app and confirm a visual/interactive change works — Electron desktop via Chrome DevTools Protocol (CDP) on port 9222 with playwright-core, and React Native (iOS/Android) via callstack agent-device. Triggers on "verify the UI", "drive the app", "screenshot the change", "check it on desktop/simulator", "CDP 9222", "agent-device", "UI 验证", "跑一下看看", "截图确认".

2026-06-092.4k

1k-defi-module-integration

OneKeyHQ/app-monorepo

App-side OneKey DeFi guide for Earn, Borrow, Staking, vaults, lending, protocol integrations, ABI-backed operations, native/provider-backed operations, pending transactions, history, route handoffs, risk display, and DeFi regression review.

2026-06-062.4k

1k-perps-module

OneKeyHQ/app-monorepo

Use only for explicit OneKey Perps/Hyperliquid (`views/Perp`, ServiceHyperLiquid, perpetuals, 永续/合约, Perps trading). Covers orderbook/L2/BBO, TWAP, scale/TIF/trigger/reduce-only, Perps TradingView/K-line, Perps Relay deposit, token selector, positions/account state/PnL/funding/margin/liquidation. Exclude generic Swap/Market/TradingView; Swap Relay quote/status/pending/requestId alone is not enough unless Perps deposit/Hyperliquid/`views/Perp`/`usePerpDeposit`/`fetchPerpDeposit*`/`perpsDepositOrderAtom` is explicit.

2026-06-062.4k

name	1k-app-upgrade-test
description	Create test versions to verify app auto-update functionality and version migration.
allowed-tools	Read, Grep, Glob, Write, Edit, Bash
disable-model-invocation	true

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-git-workflow - Git branching conventions
/1k-dev-commands - Build and release commands