version-release

Installation
SKILL.md

Version Release Workflow

Overview

The primary development branch is canary. All day-to-day development happens on canary. When releasing, canary is merged into main. After merge, auto-tag-release.yml automatically handles tagging, version bumping, creating a GitHub Release, and syncing back to the canary branch.

Only two release types are used in practice (major releases are extremely rare and can be ignored):

Type Use Case Frequency Source Branch PR Title Format Version
Minor Feature iteration release ~Every 4 weeks canary 🚀 release: v{x.y.0} Manually set
Patch Weekly release / hotfix / model / DB migration ~Weekly or as needed canary or main Custom (e.g. 🚀 release: 20260222) Auto patch +1

Minor Release Workflow

Used to publish a new minor version (e.g. v2.2.0), roughly every 4 weeks.

Steps

Related skills

More from lobehub/lobe-chat

Installs
1
GitHub Stars
77.0K
First Seen
Apr 8, 2026