Agentbro Release

AgentBro Release

Use this repository-scoped skill for AgentBro release work. Keep unrelated local changes out of commits.

Safety Rules

• Start with git status --short --branch. If unrelated files are dirty, do not stage them.
• Never reuse or force-move an existing release tag. If a published release is wrong, make the next patch version.
• Do not edit signing keys, certificates, entitlements, or release secrets.
• Do not bump versions in feature PRs. Only bump for an actual release.
• Do not leave dev behind the latest stable release. Every stable release must be merged back through a PR to dev.
• If gh is not authenticated, use the public GitHub API with curl for read-only checks.

Version Selection

Use semantic versioning when choosing the next release number:

• Bug fixes and small reliability fixes bump the third number: X.Y.Z -> X.Y.(Z+1).
• Minor/user-facing feature releases bump the middle number and reset patch: X.Y.Z -> X.(Y+1).0.
• Major breaking releases bump the first number and reset the rest: X.Y.Z -> (X+1).0.0.

When the maintainer explicitly asks for a version, use that version after confirming the tag does not already exist locally or remotely.

Version Files

All four must match:

• package.json
• src-tauri/tauri.conf.json
• src-tauri/Cargo.toml
• src-tauri/Cargo.lock

After editing the first three, update the lockfile with:

cargo update --manifest-path src-tauri/Cargo.toml -p agentbro

Run:

pnpm release:check

Standard Release Flow

1. Fetch current remote state:

git fetch origin main dev --tags

2. If releasing from dev, merge it to main only after dev is pushed:

git checkout main
git pull --ff-only origin main
git merge --no-ff origin/dev -m "Merge branch 'dev' into main"

3. If main changed while working, pull it before creating the release commit. Stash only your own release edits if needed:

git stash push -u -m "release-work"
git pull --ff-only origin main
git stash pop

4. Update .github/release-notes.md for the actual release. The GitHub Release body and updater latest.json notes both come from this file.

   Before writing, derive the changelog from the actual diff — do not hand-wave a short summary. See "Drafting Release Notes From the Diff" below. The notes must reflect everything shipped since the previous release.

   Release notes must be bilingual:

   • English first, under ## English.
   • Chinese second, under ## 中文.
   • Keep the same facts in both sections. Do not ship an English-only or Chinese-only release body.
   • The app update dialog selects the Chinese section only when the user's language is Chinese; all other UI languages show the English section.
   • If this release includes first-time contributors, include a ### New Contributors block in English and a matching ### 新贡献者 block in Chinese. Mention GitHub usernames and PR numbers.

5. Bump to the next version using the "Version Selection" rules above and run validation:

pnpm release:check
pnpm test:run
pnpm lint
pnpm build
cargo check --manifest-path src-tauri/Cargo.toml

Known acceptable warnings today:

• Vitest/jsdom may print HTMLCanvasElement's getContext() not implemented while tests pass.
• ESLint may report existing React hook dependency warnings.
• Vite may warn about chunk size or ineffective dynamic imports.
• cargo check may warn about apps_claude_gemini dead code.

6. Commit release-related changes separately when useful:

git add <changed-files>
git commit -m "fix: <release fix>"
git add package.json src-tauri/Cargo.lock src-tauri/Cargo.toml src-tauri/tauri.conf.json
git commit -m "chore: release vX.Y.Z"

7. Confirm the tag does not exist:

git tag --list vX.Y.Z
git ls-remote --tags origin refs/tags/vX.Y.Z

8. Tag and push:

git tag vX.Y.Z
git push origin main vX.Y.Z

9. After the stable GitHub Release is published, verify that the Sync release back to dev workflow opens a PR from chore/sync-vX.Y.Z-to-dev into dev:

gh pr list \
  --base dev \
  --head chore/sync-vX.Y.Z-to-dev \
  --state open

Review and merge that PR before accepting more feature PRs into dev. The PR must carry the release commit and all four version files back together; do not manually change only package.json.

If the workflow is unavailable, create the equivalent sync PR manually:

git checkout dev
git pull --ff-only origin dev
git checkout -b chore/sync-vX.Y.Z-to-dev
git merge --no-ff vX.Y.Z -m "chore: sync vX.Y.Z back to dev"
git push -u origin chore/sync-vX.Y.Z-to-dev
gh pr create \
  --base dev \
  --head chore/sync-vX.Y.Z-to-dev \
  --title "chore: sync vX.Y.Z back to dev"

10. After the sync PR merges, confirm dev is not behind the latest stable tag:

git checkout dev
git pull --ff-only origin dev
pnpm release:check