一键导入
release-build
End-to-end checklist for building a signed macOS release — bump manifest min_app_version, verify sidecars, build, and inspect the .app
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
End-to-end checklist for building a signed macOS release — bump manifest min_app_version, verify sidecars, build, and inspect the .app
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Experimental protocol for Deep Cuts research, prototypes, model evaluations, threshold tuning, ablations, metric comparisons, and claims about accuracy or quality. Use before running or interpreting experiments so bots preserve train/validation/test boundaries, avoid leakage, compare against baselines, and report results honestly.
Guidelines for creating, updating, reorganizing, and reviewing Deep Cuts documentation in the project wiki, including page taxonomy, lifecycle status, protected pages, proposal handling, and link verification.
Pattern for multi-agent collaboration sessions in the deep-cuts fam — forge-first coordination over the botfam substrate (Gitea issues/PRs as the coordination plane, the unified `botfam wait` wake loop, bare-actor worktrees), with IRC opt-in for design sprints, plus session-log conventions
Draft, structure, and finalize a Deep Cuts blog-series post so it conforms to the post template, house voice, and cross-post link rules. Use when writing, drafting, assembling, or editing a "Deep Cuts" blog post (the rlupi.com series), preparing a post for publishing, or adding front matter to one. Covers the template, front matter schema, voice, agent crediting, and the link linter.
Checklist and guide for adding a new analysis pass to the trait-based modular pipeline
Safe pattern for adding SQLite schema migrations in the deep-cuts Rust/rusqlite_migration stack
| name | release-build |
| description | End-to-end checklist for building a signed macOS release — bump manifest min_app_version, verify sidecars, build, and inspect the .app |
The release process does not bump src-tauri/Cargo.toml — that version represents the current release and stays as-is. After shipping, bump it separately using the bump-dev-version skill to start the next dev cycle.
min_app_version in models/manifest.jsonSet min_app_version to the current version from src-tauri/Cargo.toml:
{
"manifest_version": 1,
"min_app_version": "X.Y.Z",
...
}
This tells older app installs that they must update before the new model manifest applies.
Update both:
CHANGELOG.md (root) — add bullet points for this release under the current version tagdocs/changelog.md — mirror the same entries (this is the public-facing website changelog)Use git log <prev-tag>..HEAD --oneline to enumerate commits since the last release.
These steps are fully automated by tools/release-build.sh. Run it from the repo root:
tools/release-build.sh
The script:
ACOUSTID_CLIENT_KEY automatically from src-tauri/.cargo/config.toml/opt/homebrew/ paths exist in the source binaries@loader_path/../Frameworks is in the rpathtauri.conf.json frameworks match src-tauri/binaries/cargo test and npm testnpm run tauri build.app bundle layout, paths, signatures, and Gatekeeper statusOutput lands in src-tauri/target/release/bundle/.
If you've run brew upgrade llama.cpp since the last release, re-run tools/bundle-llama-server.sh before running the build script.
To run the build manually instead:
ACOUSTID_CLIENT_KEY=$(grep ACOUSTID_CLIENT_KEY src-tauri/.cargo/config.toml | sed 's/.*= *"\(.*\)"/\1/') \
npm run tauri build
Replace X.Y.Z with the current version:
VERSION=$(grep '^version' src-tauri/Cargo.toml | head -1 | sed 's/.*= *"\(.*\)"/\1/')
git add models/manifest.json CHANGELOG.md docs/changelog.md tools/ skills/
git commit -m "chore: release v$VERSION"
git tag "v$VERSION"
git push origin main --tags
gh release create "v$VERSION" \
"src-tauri/target/release/bundle/dmg/Deep Cuts_${VERSION}_aarch64.dmg" \
--title "v$VERSION" \
--notes "$(sed -n "/^## \[${VERSION}\]/,/^---/p" CHANGELOG.md | head -n -1)"
min_app_version in models/manifest.json set to current versionCHANGELOG.md (root) and docs/changelog.md updatedtools/release-build.sh passes all checks (covers steps 3–5)gh release create