Something went wrong. Try again.
I'm going to build my own OpenClaw, with blackjack... and bun!
Something went wrong. Try again.
Markdown
Release process #
Publishing #
Pushing a version tag triggers .github/workflows/publish.yml and publishes multi-arch GHCR images:
ghcr.io/rcarmo/piclaw:<tag>ghcr.io/rcarmo/piclaw:latest
Cutting a release #
make bump-patch # or make bump-minor
make push
This bumps VERSION and package.json, commits, tags, and pushes. The CI workflow builds and publishes Docker images for AMD64 and ARM64.
For manual release-image verification outside GitHub Actions, the repo-owned smoke contract is:
IMAGE_REF=ghcr.io/rcarmo/piclaw:vX.Y.Z \
PLATFORM=linux/amd64 \
EXPECTED_BUN_VERSION=$(tr -d '[:space:]' < BUN_VERSION) \
EXPECTED_RESTIC_VERSION=$(tr -d '[:space:]' < RESTIC_VERSION) \
make publish-smoke
Boundary note:
- publish smoke is intentionally repo-owned (
make publish-smoke) - release/tag/workflow/package pruning remains GitHub-native in
.github/workflows/publish.ymlbecause it depends directly on Actions context and GitHub APIs
Release naming #
Each release gets a cult/classic movie name. See the cut-release skill for the full convention and workflow.
Container runtime compatibility #
PiClaw works with any OCI-compliant runtime.
- Preferred image source:
ghcr.io/rcarmo/piclaw - Primary target: Docker / Docker Desktop
- Also works with Apple Containers, Podman, nerdctl, and similar runtimes