release

GitHub

自动化发布 Flowplan 服务器版本,触发 GitHub Actions 工作流以构建镜像、打标签并创建发行版。需确保 CI 绿灯,验证发布结果后通知相关方。

.claude/skills/release/SKILL.md yannicschuller/flowplan

Trigger Scenarios

用户输入 /release 用户请求发布新版本(如 'neues Release', 'Patch Release')

Install

npx skills add yannicschuller/flowplan --skill release -g -y
More Options

Non-standard path

npx skills add https://github.com/yannicschuller/flowplan/tree/main/.claude/skills/release -g -y

Use without installing

npx skills use yannicschuller/flowplan@release

指定 Agent (Claude Code)

npx skills add yannicschuller/flowplan --skill release -a claude-code -g -y

安装 repo 全部 skill

npx skills add yannicschuller/flowplan --all -g -y

预览 repo 内 skill

npx skills add yannicschuller/flowplan --list

SKILL.md

Frontmatter
{
    "name": "release",
    "description": "Publish a Flowplan server release (patch by default, minor or major on request) with the repository's standard Release workflow – only from a green main, then check the release notes and the published image, and tell the reporters of issues that waited for the release. Use when the user types \/release or asks for a \"neues Release\", \"Patch Release\", \"Minor Release\"."
}

/release – a Flowplan release, the standard way

The maintainer is Yannic Schuller (GitHub yannicschuller). Talk to him in German; write on GitHub in English. Argument: patch (default), minor or major. The user invoking /release is the OK to publish this one release – nothing more.

1. Preconditions

  1. cd /home/user/flowplan && git fetch -q origin main --tags – look at the remote tags, local ones may be stale. The next version is what release.yml computes: a version already raised in package.json but never tagged is released as it is; otherwise bump raises it.
  2. The head of main must be green: CI, Visual regression, Docker image (and CodeQL). Not green → /ship first (fix, push, wait), then come back. Uncommitted or unpushed work → ask whether it belongs in the release.
  3. Show Yannic nothing for approval unless something is odd (a red run, a huge or surprising change list) – then ask once.

2. Run the standard workflow

Dispatch release.yml on main with bump: <patch|minor|major> (mcp__github__actions_run_trigger, method run_workflow). Never tag by hand, never create the GitHub release by hand, never force-move a tag (pushes of tags with force are refused anyway).

The workflow raises package.json and the Helm chart's appVersion, commits with CHANGELOG.md, tags vX.Y.Z, creates the GitHub release (notes from scripts/release-notes.mjs) and publishes the image as :latest, :X.Y.Z, :X.Y, :X (it calls docker.yml).

Watch it with Monitor until it finishes. Red → read the job log, root-cause; re-dispatch only after the cause is fixed.

3. After the release

  1. mcp__github__get_latest_release – check tag, notes (no internal noise that shouldn't be public), and that the Docker part of the run is green including the Trivy scan job.
  2. git pull --ff-only origin main locally (the release commit), then force-push the session branch to it.
  3. Issues that are status: done and whose last comment said "will be in the next release": optional one-line note "Released in vX.Y.Z" only if Yannic asks for it – don't spam.

4. Report (German, short)

Version and link, the main changes in a few bullets (grouped: features, fixes, security), run results, and anything Yannic does by hand (e.g. watch Coolify pull :latest on stable instances).

Not this skill

  • App store versions → /app-release. Desktop app → its own release.yml in flowplan-desktop, only on explicit request.

Version History

  • 84c9b3c Current 2026-11-07 08:54

Same Skill Collection

.claude/skills/app-release/SKILL.md
.claude/skills/deps/SKILL.md
.claude/skills/issue/SKILL.md
.claude/skills/language/SKILL.md
.claude/skills/security-audit/SKILL.md
.claude/skills/security/SKILL.md
.claude/skills/ship/SKILL.md

Metadata

Files
0
Version
84c9b3c
Hash
06cf040a
Indexed
2026-11-07 08:54

trang chủ - Wiki
Copyright © 2011-2026 iteam. Current version is 2.156.0. UTC+08:00, 2026-11-07 20:59
浙ICP备14020137号-1