菜单
Use when bumping the RAPS version for a new release — updates Cargo.toml workspace version, 9 internal crate dependencies, 6 npm package.json files, creates git tag, and triggers the release workflow.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when adding a new MCP tool to the RAPS MCP server — covers tool schema definition, handler implementation, dispatch registration, and the client accessor pattern.
Use when adding a new CLI command or subcommand to RAPS — covers the clap struct pattern, module wiring, output formatting, and test structure across the 10-crate workspace.
Use when new RAPS features ship and LinkedIn content is needed — adds posts to the raps-smm post bank following established tone, format, and hashtag conventions.
Use when adding or updating CI/CD integrations in the raps-actions repo — GitHub Actions composite actions, GitLab CI include templates, test workflows, and floating tag management.
Use before releases or after dependency updates to run security checks — cargo-audit, ASVS compliance matrix review, clippy security lints, redaction pattern verification.
Use when you need to create a shortened URL at go.rapscli.xyz — for long Cloudflare OAuth links, wrangler login URLs, or any URL that's unwieldy in the terminal.
| name | cutting-raps-release |
| version | 1.0 |
| description | Use when bumping the RAPS version for a new release — updates Cargo.toml workspace version, 9 internal crate dependencies, 6 npm package.json files, creates git tag, and triggers the release workflow. |
Bump version across all files, tag, and trigger the release workflow.
Repo: /root/github/raps/raps
| Location | Pattern |
|---|---|
Line ~18: [workspace.package] | version = "X.Y.Z" |
Lines ~29-37: [workspace.dependencies] | 9 crates with version = "X.Y.Z" |
Internal crates: raps-kernel, raps-oss, raps-derivative, raps-dm, raps-da, raps-acc, raps-webhooks, raps-reality, raps-admin.
| File | Field |
|---|---|
npm/package.json | "version" + 5 optionalDependencies values |
npm/platforms/win32-x64/package.json | "version" |
npm/platforms/darwin-x64/package.json | "version" |
npm/platforms/darwin-arm64/package.json | "version" |
npm/platforms/linux-x64/package.json | "version" |
npm/platforms/linux-arm64/package.json | "version" |
python-bindings/Cargo.toml — independent version (currently 4.3.0)python-bindings/pyproject.toml — sameOLD="4.16.0"
NEW="4.17.0"
# 1. Workspace version + internal deps (Cargo.toml)
sed -i "s/version = \"${OLD}\"/version = \"${NEW}\"/g" Cargo.toml
# 2. npm main package version
sed -i "s/\"version\": \"${OLD}\"/\"version\": \"${NEW}\"/" npm/package.json
# 3. npm optionalDependencies (5 entries in npm/package.json)
sed -i "s/\"${OLD}\"/\"${NEW}\"/g" npm/package.json
# 4. Platform packages
for p in win32-x64 darwin-x64 darwin-arm64 linux-x64 linux-arm64; do
sed -i "s/\"version\": \"${OLD}\"/\"version\": \"${NEW}\"/" npm/platforms/${p}/package.json
done
# 5. Verify
grep -r "$NEW" Cargo.toml npm/package.json npm/platforms/*/package.json
# 6. Commit
git add Cargo.toml npm/
git commit -m "chore: bump version to ${NEW}"
# 7. Tag and push (triggers release workflow)
git tag "v${NEW}"
git push origin main --tags
After tag push, .github/workflows/release.yml runs:
npm/package.json (5 version strings, not just the top-level version)