菜单
End-to-end release process for hook: version bumps, local validation gate, binary release via tag push, and crates.io publish in dependency order. Use when cutting a new release or diagnosing a failed publish.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Build, maintain, and operate the contract-driven hook workspace with serve/relay/smash roles, Kafka core transport, and plug-and-play adapters. Use when editing runtime behavior, contract validation, adapter/plugin execution, or deployment documentation.
Maintain the kafka-openclaw-hook compatibility binary and its integration with hook-runtime smash execution. Use when changing startup wiring, runtime env expectations, deployment compatibility, or smash adapter/plugin behavior.
Maintain shared relay-core contracts, validation, envelope models, and security primitives used by serve, relay, smash, and hook-runtime. Use when changing contract schema, active-profile validation, model compatibility, or signature/sanitization/timestamp logic.
Add a new webhook source to hook serve. Covers implementing the SourceHandler trait, registering the handler, adding HMAC secret config, creating the Kafka topic, and writing tests. Use when integrating a new webhook provider (e.g. Stripe, PagerDuty, Bitbucket).
Provision and operate Apache Kafka in KRaft mode inside a Firecracker microVM without Docker, including host networking, guest bootstrap, systemd service, and security checks. Use when setting up a lightweight isolated Kafka broker for internal pipelines such as hook serve/relay/smash Kafka core transport.
Trace a webhook through the full hook pipeline (serve → relay → smash), inspect Kafka topic contents, check consumer group lag, and replay messages from the DLQ. Use when a webhook is lost, delayed, or failing delivery, or when diagnosing any serve/relay/smash runtime issue.
| name | release-workflow |
| description | End-to-end release process for hook: version bumps, local validation gate, binary release via tag push, and crates.io publish in dependency order. Use when cutting a new release or diagnosing a failed publish. |
| Artifact | Destination |
|---|---|
hook binary | GitHub Releases |
hook-serve binary | GitHub Releases |
kafka-openclaw-hook binary | GitHub Releases |
relay-core crate | crates.io |
hook-serve crate | crates.io |
kafka-openclaw-hook crate | crates.io |
hook-runtime is an internal workspace path dependency — not published to crates.io.
Update version in each Cargo.toml that is changing. All workspace members must stay aligned:
Cargo.toml (workspace root)crates/relay-core/Cargo.tomlsrc/Cargo.toml (hook-serve)apps/kafka-openclaw-hook/Cargo.tomltools/hook/Cargo.tomlcrates/hook-runtime/Cargo.tomlIf relay-core version changes, also update its version = "..." in any crate that depends on it.
Commit the bump:
git add -u
git commit -m "chore: bump version to v0.x.0"
All checks must pass before tagging. Do not skip any step.
cargo fmt --all -- --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace
cargo build --workspace --release
scripts/build-release-binaries.sh
scripts/publish-crates.sh --dry-run
Common dry-run failures:
relay-core version mismatch in downstream Cargo.toml filesgit tag v0.x.0
git push origin v0.x.0
This triggers .github/workflows/release-binaries.yml, which builds binaries for linux and macOS and attaches archives + checksums to a GitHub Release.
Expected release assets:
hook-serve-<target>.tar.gzkafka-openclaw-hook-<target>.tar.gzhook-<target>.tar.gzSHA256SUMS-<target>.txtMonitor CI:
gh run list --workflow release-binaries.yml
gh run view <run-id>
Publish order is fixed — relay-core must land on crates.io before dependents can be published.
gh workflow run publish-crates.yml -f dry_run=true # verify first
gh workflow run publish-crates.yml -f dry_run=false # then publish
scripts/publish-crates.sh
Enforced publish order:
relay-corehook-servekafka-openclaw-hookFor partial publishes, use skip flags:
scripts/publish-crates.sh --skip-relay-core
# Allow a few minutes for crates.io index propagation
cargo search relay-core
cargo search hook-serve
gh release view v0.x.0
crates.io versions are immutable — yank, then cut a patch:
cargo yank --version 0.x.0 relay-core
cargo yank --version 0.x.0 hook-serve
cargo yank --version 0.x.0 kafka-openclaw-hook
Bump to 0.x.1, fix the issue, republish. Document in changelog.
For binary releases: delete the GitHub Release and re-tag.
Check in order:
CARGO_REGISTRY_TOKEN secret configured in repo settingsrelay-core version mismatch in downstream Cargo.tomlscripts/publish-crates.sh --dry-run