Release Branch Management

Manages the bundle release workflow: developers branch from release/*, PRs target release/* directly, and after publishing, changes sync back to x via rebase.

Context

OneKey ships periodic App Shell releases (tagged v{X.Y.Z} on the x branch). After each App Shell release, a release branch (release/v{X.Y.Z}) is created from the tag. Bundle release features are developed directly on this branch — PRs target release/*, not x. After bundle publishing, changes are synced back to x via rebase.

Release branch auto-detection: All subcommands read VERSION from .env.version and construct release/v${VERSION} automatically.

Quick Reference

Subcommand Routing

Parse the argument passed to this skill:

• checkout [branch-name] → Read and follow checkout.md
• prepare → Read and follow prepare.md
• diff-check → Read and follow diff-check.md
• publish → Read and follow publish.md
• sync → Read and follow sync.md
• No argument → Show this quick reference and ask which subcommand to run

Typical Release Flow

/1k-bundle-release checkout feat/my-fix   ← Branch from release/* to start work
  ... develop, create PR targeting release/*, QA verifies, merge ...
/1k-bundle-release prepare                ← Set BUILD_NUMBER
/1k-bundle-release diff-check             ← Review changeset before publishing
/1k-bundle-release publish                ← Record release in RELEASES.json
/1k-bundle-release sync                   ← Rebase changes to x

These steps are designed to run in sequence, but each can also run independently.

Key Files

Related Skills

• /1k-git-workflow — Branch naming, commit conventions
• /commit — Create commits