// Release workflow for stella Go CLI project. Create releases with semantic versioned tags, update changelog, and trigger automated CI/CD builds. Use when the user asks to "release", "create a release", "tag a version", "update changelog", "prepare release", "cut a release", or discusses versioning and release artifacts.
Self-knowledge about stella, the self-hosted AI assistant. Use when the user asks about stella itself: configuration, setup, onboarding, providers, models, agents, channels (Telegram/QQ/Feishu/WeChat), memory system (LCM), scheduled jobs, heartbeat, skills, plugins, session compaction, notifications, self-update, multi-agent, multi-user, or general "how does stella work" / "help me get started" questions. Also triggers on "change my model", "set up telegram", "set up wechat", "configure provider", "update stella", "what can you do", "how do I install skills", "stella onboard", "switch agent".
Database schema design best practices. Use when creating tables, reviewing migrations, planning data models, or answering schema design questions.
Automate Stella web UI testing with tap-web browser automation. Use when the user asks to "test the UI", "check the web page", "verify the frontend", "run UI tests", "browser test", or wants to interact with stella.localhost in a browser.
Access websites, search the web, and extract clean content using the `tap` CLI. Supports structured site scripts, readable page extraction, and browser automation for tabs, screenshots, forms, cookies, JavaScript evaluation, and network capture. Use for web lookup, page reading, content extraction, browser interaction, authenticated sessions, request interception, or CDP-connected desktop apps.
Reading assistant for saving, organizing, and recalling web content. Use when the user says "save this article", "read this link", "summarize this", "check my feeds", "add to my library", or asks about previously saved content. Handles articles, tweets, YouTube videos, GitHub repos, PDFs, and RSS feeds. Articles are stored as markdown files with metadata and indexed for fast search.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
| name | release |
| description | Release workflow for stella Go CLI project. Create releases with semantic versioned tags, update changelog, and trigger automated CI/CD builds. Use when the user asks to "release", "create a release", "tag a version", "update changelog", "prepare release", "cut a release", or discusses versioning and release artifacts. |
Use semantic versioning with v prefix: v0.1.0, v1.0.0, v1.2.3-rc.1.
GoReleaser auto-detects pre-release suffixes (-rc.1, -beta.1).
vX.Y.Z; the web package version is X.Y.Z (without v).web/package.json so .version matches the API/server release version:
VERSION=X.Y.Z
tmp=$(mktemp)
jq --arg version "$VERSION" '.version = $version' web/package.json > "$tmp" && mv "$tmp" web/package.json
test "$(jq -r '.version' web/package.json)" = "$VERSION"
web/content/docs/changelog.mdx and web/content/docs/changelog.zh.mdx (see below).📝 docs: Update CHANGELOG for vX.Y.Z including both changelogs and web/package.json.git status --short
git log --oneline -1
HEAD; never tag before the commit exists.HEAD:
git tag vX.Y.Z
test "$(git rev-parse vX.Y.Z)" = "$(git rev-parse HEAD)"
git push origin main vX.Y.Z..github/workflows/release.yml → GoReleaser binaries + Docker images.The changelogs live at web/content/docs/changelog.mdx and web/content/docs/changelog.zh.mdx (rendered on the docs site).
They have YAML frontmatter — preserve it when editing. Only modify content below the --- block, and keep English and Chinese entries in sync.
Gather changes since last tag:
git log $(git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD)..HEAD --oneline
gh pr list --state merged --base main --search "merged:>=$(git log -1 --format=%aI $(git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD))"
Apply to both changelog files:
[Unreleased] to [X.Y.Z] - YYYY-MM-DD[Unreleased] section above✨ Features, 🐛 Bug Fixes, ♻️ Refactoring, 📝 Documentation, 📦 Dependencies([#123](https://github.com/CherryHQ/stella/pull/123))**Full Changelog**: [vPREV...vX.Y.Z](https://github.com/CherryHQ/stella/compare/vPREV...vX.Y.Z)VERSION=X.Y.Z
test "$(jq -r '.version' web/package.json)" = "$VERSION"
mise run release:check # Validate .goreleaser.yaml
mise run release:snapshot # Test release locally (no tag needed)
ghcr.io/cherryhq/stella — linux/amd64 + linux/arm64latest (stable), vX.Y.Z (release), SHA (every build)