9527CODE 技术博客
← 返回博客列表

release

由 reactive-resume 提供的 release Skill,包含安装方法、功能说明、完整指令和 GitHub 原文入口。


name: release description: Use when releasing a new version of Reactive Resume — bumping the version, writing the changelog entry, creating the GitHub release, or when asked to "cut a release" / "release vX.Y.Z".


功能说明

Use when releasing a new version of Reactive Resume — bumping the version, writing the changelog entry, creating the GitHub release, or when asked to "cut a release" / "release vX.Y.Z".

快速安装

npx skills add https://github.com/reactive-resume/reactive-resume --skill release

以上为基于原仓库和 Skill 名称整理的安装命令,未在本机执行;原文另有安装要求时以原文为准。


Release Reactive Resume

One pipeline: version bump → changelog entry → PR → squash-merge → tag → GitHub release. The changelog entry and the GitHub release body are the same text.

Steps

  1. Scope the release. Previous tag: git tag --sort=-creatordate | head -1. Changes: git log vPREV..HEAD --format='%h %s'. Confirm the new version with the user if not given (patch unless there's a headline feature).

  2. If this cycle added user-facing strings, run fill-translations first so catalogs ship complete.

  3. Bump the version in the root package.json: it is the release version for the web app, server and GitHub release. The native app's store version, version in apps/mobile/app.config.ts, is separate: change it only when this release also ships a new store build (see .agents/docs/runbooks/mobile-releases.md).

  4. Write the changelog entry at the TOP of docs/changelog/index.mdx (right after the frontmatter), in house style — use changelog-generator for the prose, then fit it to this exact shape:

    <Update label="vX.Y.Z" description="7th July 2026">
    ## Highlights
    
    - **Bold feature lead.** One or two sentences of user-facing benefit — what it does for the user, not how it's implemented. [abc123def](https://github.com/reactive-resume/reactive-resume/commit/abc123def)
    
    ## Thematic Section (e.g. Resume Builder, Import & Export, Self-Hosting & Maintenance)
    
    - Past-tense entry ("Added…", "Fixed…", "Improved…") with commit links. [abc123def](https://github.com/reactive-resume/reactive-resume/blob/main/.agents/skills/release/...)
    
    **Full Changelog**: [vPREV...vX.Y.Z](https://github.com/reactive-resume/reactive-resume/compare/vPREV...vX.Y.Z)
    
    </Update>
    

    Conventions: date is ordinal ("7th July 2026"); every bullet links its commit(s) as [shortsha](commit url); group by theme, Highlights first; write for users of the app and self-hosters, not for contributors. Thank external contributors by handle where relevant.

  5. Run checks: pnpm check, pnpm typecheck, pnpm test.

  6. PR: non-draft, against main. Before merging, tagging, publishing the release or pushing the Cloudron change, show the user exactly what will run (version, commit SHA, release notes) and wait for an explicit yes. Short summary + bullets of changes in the body. No mention of Claude/Codex/AI anywhere in title, body, or commits. Squash-merge once CI is green, then wait for the post-merge checks on main to pass (gh pr checks --watch, then watch the main run).

  7. Tag and release from updated main:

    git checkout main && git pull
    git tag vX.Y.Z && git push origin vX.Y.Z
    gh release create vX.Y.Z --title vX.Y.Z --notes-file release-notes.md
    

    Write the release body to release-notes.md first, and delete the file afterwards. The body is the new <Update> block's inner content (Highlights through Full Changelog line), without the <Update> wrapper.

  8. Update the Cloudron package once the release image is on GHCR: follow cloudron/README.md (manifest version, CHANGELOG, npx cloudron versions add --image ghcr.io/reactive-resume/reactive-resume:v<version>), then commit cloudron/ to main.

  9. Optional, on request: screenshots for the changelog/docs (via agent-browser against the running app) and a LinkedIn/Reddit announcement draft based on the Highlights.

Common Mistakes

Mistake Reality
Bumping versions in packages/*, apps/web or apps/server Only the root package.json carries the release version; apps/mobile/app.config.ts changes only for a store build.
Appending the entry at the bottom Newest <Update> goes first, directly after frontmatter.
Implementation-speak in the changelog Readers are end users and self-hosters; describe benefits.
Tagging before the squash-merge lands Tag the merged commit on main, never the branch.
ISO dates in the description House style is ordinal: "7th July 2026".

来源与许可

reactive-resume/reactive-resume 提供此 Skill,适用 MIT。本版本追加了安装和访问入口,并将相对文档链接解析为 GitHub 地址;原始文件可从下方原文入口获取。

MIT License

Copyright (c) 2026 Amruth Pillai

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

在 GitHub 查看原文

查看更多详情

原文作者:reactive-resume

来源网站:GitHub